Design guide for managed fleets
The topics in this design guide cover some of the decisions you'll need to make when configuring an Amazon GameLift managed EC2 fleet. They provide guidance and best practices for creating and configuring a fleet to host your game.
Required decisions include:
Where should you deploy hosting resources? Latency is a major factor in selecting your fleet's locations, but cost also varies by location.
What EC2 instance type will best support your game? Choose from instance types that are available in all your fleet locations to use the best combination of compute architecture, memory, storage, and networking capacity.
What size of instance type do you need? Choose an instance type size based on the resource requirements (memory and CPU) of your game server software and other factors.
Should your fleet use On-Demand or Spot Instances? Consider whether you can take advantage of lower Spot pricing given how Amazon GameLift guards against the chance of game sessions interruptions.
How do you want your game server software to run on each fleet instance? The runtime configuration tells Amazon GameLift what server software to run and how.
