Amazon GameLift FAQs

A fleet is a set of compute resources that runs your game build and hosts game sessions. It can provide hosting to multiple locations globally. There are two types of fleets: Amazon GameLift fleets and Amazon GameLift Anywhere fleets. The Amazon GameLift fleet represents hosting resources as a set of fully managed Amazon Elastic Compute Cloud (Amazon EC2) virtual computing machines, called instances. Amazon GameLift Anywhere fleets represent hosting resources in the form of a set of customer managed servers. You can accommodate changes in player demand by increasing or decreasing the number of instances or customer managed hardware in your fleet. A fleet is configured to use a certain instance type, to deploy a build, and to run one or more server processes on each instance.

A multi-location fleet is a fleet with hosting resources in multiple geographic locations. Multi-location fleets have a home region and one or more remote locations. By utilizing multi-location fleets you can upload a game binary and deploy your hosting resources across multiple geographic locations. Remote locations can be any of the AWS Regions or Local Zones that Amazon GameLift supports. Please visit the Amazon GameLift developer guide for more information.

Fleet creation time is dependent on the size of your game build, your installation script runtime, and the number of locations you are deploying. This time is measured from the time you submit a fleet creation request to when it is fully deployed and accessible to your players. To learn more about fleet creation times, please visit the developer guide.

Please see the Amazon GameLift Instance Pricing page for a full list of Amazon GameLift instances.

The right instance type depends on your game’s server performance and the number of server processes you plan to run concurrently on each instance. The computational complexity of your game, optimization of your game and network code, and maximum number of players are the main drivers for the size of the instance that you will need. One of the advantages of Amazon GameLift is that you only pay for what you use, which makes it convenient and inexpensive to test the performance of your game on different instance families and types.

Up to 50. The number of server processes depends on the performance requirements of your game servers and the instance type you choose for your fleet. When you set up a fleet, you will select an instance type and configure the fleet to concurrently run an optimum number of server processes. Running more processes on fewer instances can help you decrease costs. You can also configure your fleet to run multiple server builds or game configurations on each instance.

Amazon GameLift provides a truly elastic computing environment. Amazon GameLift instances enable you to increase or decrease capacity within minutes, not hours or days. You can provision one, hundreds, or even thousands of server instances simultaneously.

Seamlessly provide the capacity you need to meet changes in player demand with Amazon GameLift Target Tracking. Target Tracking is an autoscaling feature that allows you to simply set a percentage target for available game sessions, creating a buffer to accommodate fluctuations in player traffic. Amazon GameLift will add or remove capacity as required to keep this buffer of available game sessions at the target value you define and adjust to a fluctuating load pattern, minimizing rapid fluctuations in capacity. For more information, see the Autoscaling section of the Amazon GameLift Developer Guide.

Amazon GameLift retains activity metrics. When you terminate an instance, any data generated by your game server and stored on the instance is lost. However, you can instruct Amazon GameLift to retain and store these log files for up to seven days after the instance has been terminated.

Yes. You can remotely access an instance in a fleet that is in an activating, active, or error status. This is useful for debugging, inspecting player activity in real time, or connecting performance monitoring or benchmarking tools. You can modify your fleet’s port settings and protocols using either the AWS command line interface (CLI) or through the Amazon GameLift console.

Yes, Amazon GameLift makes updating production fleets simple with its alias feature. An alias enables you to direct traffic to fleets without having to change the client end-point descriptor. After creating a new production fleet, you can edit an alias to point from an older fleet to this newer fleet, routing all connecting players to the new fleet alias feature. Learn more about creating aliases in our Amazon GameLift Developer Guide.

To see a list of regions that Amazon GameLift is currently available in please visit the Amazon GameLift documentation.

AWS Local Zones allow you to use Amazon GameLift closer to more end-users, providing them very low latency access to the dedicated game servers running your session-based multiplayer games. AWS Local Zones are a new type of AWS infrastructure designed to run gaming-related workloads that require single-digit millisecond latency, like remote real-time gaming and augmented and virtual reality. Not every customer wants to operate their own on-premises data center, while others may be interested in getting rid of their local data center entirely. Local Zones allow customers to gain all the benefits of having compute resources closer to end-users, without the need to own and operate their own data center infrastructure.

AWS Local Zones allow you to use Amazon GameLift closer to more end-users, providing them very low latency access to the dedicated game servers running your session-based multiplayer games. AWS Local Zones are a new type of AWS infrastructure designed to run gaming-related workloads that require single-digit millisecond latency, like remote real-time gaming and augmented and virtual reality. Not every customer wants to operate their own on-premises data center, while others may be interested in getting rid of their local data center entirely. Local Zones allow customers to gain all the benefits of having compute resources closer to end-users, without the need to own and operate their own data center infrastructure.

To see a list of Local Zones that Amazon GameLift is currently available in please visit the Amazon GameLift documentation.

We support the following instance types in Local Zones for Amazon GameLift: C5d 2xlarge and R5d 2xlarge. 

Amazon GameLift Spot instances offer access to spare AWS computing capacity at savings of between 50% and 85% compared to On-Demand prices. However, Spot instances can be interrupted by AWS with two minutes of notification when AWS needs the capacity back. You can use this notification period to migrate or shut down games running on those instances. Using the Amazon GameLift built in game session placement algorithm, you can optimize for cost savings while maintaining high game server availability. The algorithm places new sessions on game servers based on player latencies, instance prices, and Spot interruption rates. You can customize how the algorithm balances these priorities.

You get the same high-performance hardware as Amazon GameLift On-Demand instances, but save between 50% and 85%. By accepting a small decrease in server availability as compared to using only On-Demand instances, you can save a lot of money. For more information on Spot pricing and to see pricing examples please see the Amazon GameLift Service pricing page.

You can find the best practices for using Spot instances in our developer guide You can also find a tutorial on how to best set up a game session queue for Spot Instances in our developer guide.

When AWS occasionally needs more capacity, some Amazon GameLift Spot instances could receive a warning that the game servers must shut down within two minutes. When that happens, you can use the warning period to gracefully migrate or shut down active game sessions. To maintain an equal amount of available capacity for your game, the game session placement algorithm will automatically start new servers in the same region by using alternate Spot instances types or by using On-Demand instances.

No. The Amazon GameLift game session placement algorithm minimizes the chances of termination.

The Amazon GameLift game session placement algorithm tracks Spot interruption rates and uses this data to automatically place games on instances with low interruption frequencies.

While a Spot instance remains running, you will be charged the price set at the beginning of each hour.

The AWS Management Console makes a detailed billing report available which shows Spot instance start and termination/stop times for all instances.

Amazon GameLift Spot prices fluctuate based on the current supply and demand for each instance type in each region. Spot instance prices are set by Amazon and adjust gradually based on long-term trends in supply and demand for Spot instance capacity. However, Amazon GameLift Spot prices never exceed Amazon GameLift On-Demand prices. In the Amazon GameLift console, you can view three months of historical pricing and savings data for GameLift Spot for every instance type and region.

Amazon GameLift FlexMatch is available to anyone using Amazon GameLift’s managed game servers. FlexMatch can also be used as a standalone feature and is available to anyone, regardless of whether they host their games peer-to-peer, on-premises, or on cloud compute primitives. Please see our documentation for more information on Amazon GameLift FlexMatch.

To see a list of regions that Amazon GameLift FlexMatch is currently available in please visit the Amazon GameLift documentation.

To see a list of regions that you can place an Amazon GameLift FlexMatch matchmaker in please visit the Amazon GameLift documentation.

No. Once you create a FlexMatch rule set, that rule set can’t be changed. To change a rule set, you must clone the rule set, give it a new name, and then create your changes. To change the rule set for a live matchmaker, you then update the matchmaker’s configuration to use the new rule set instead of the old one. Because a rules set may be used by one or more live matchmakers, this limitation guards against causing unintended consequences to live production systems.

Yes. If you would like to use your own matchmaking system, you can feed match results into any game session queues that you define.

Using Amazon GameLift FlexMatch in standalone mode will incur charges based on player packages and matchmaking hours consumed. See the Amazon GameLift FlexMatch pricing page for more details. Successful matches with FlexMatch automatically result in the creation of new game sessions. Depending on how you’re managing game server capacity, creating new game sessions may trigger additional server instances, for which you’ll be charged standard Amazon GameLift instance prices.

Use Amazon GameLift to integrate hardware anywhere in your environment (on-premises or cloud) into your Amazon GameLift game hosting. Amazon GameLift Anywhere introduces a compute type, Anywhere, used to register your on-premises or cloud hardware with Amazon GameLift in a Amazon GameLift Anywhere fleet. You can integrate Anywhere and Amazon EC2 fleets in matchmaker and game session queues to manage matchmaking and game placement across your hardware in one location.

You’ll need to download the latest version of the Amazon GameLift Server SDK. You can download the SDK in the Amazon GameLift documentation.

You’ll need to perform a migration in order to enable Amazon GameLift Anywhere. Learn more about how to migrate your current Amazon GameLift project to use the updated SDK by clicking this link here.

Yes. Amazon GameLift Anywhere includes a total of 3K game sessions places and 500K server connection minutes per month for a duration of one year per account in all control plane regions. See the Amazon GameLift Anywhere Pricing for more details.

Please visit the developer guide to get started with Amazon GameLift Anywhere.

Amazon GameLift includes 50GB EBS General Purpose (SSD) Volume for each instance. However, this limit is adjustable. For more information please see the Amazon GameLift Service Quotas page.

The build catalog is a record of all of your server builds that have been uploaded to Amazon GameLift. Builds in ready state are available for fleet creation at any time.

The build catalog can store the maximum of 1,000 builds or 100GB of storage.

Yes, by default, you are limited to 10 fleets per region. However, this limit is adjustable. For more information please see the Amazon GameLift Service Quotas page.

No, you are only limited by your AWS account limits.

Yes, Amazon GameLift is limited by the number of instances available to your AWS account. If you need to raise this limit, you can do so via the service limits page in the Amazon GameLift console.

If you are using Amazon GameLift to manage your game sessions or use Amazon GameLift FlexMatch to create new game sessions after matching players then the maximum number of players per game session is 200. If you do not use Amazon GameLift to manage your game sessions then your player count is only limited by hardware and networking constraints that are being utilized.

No, the maximum number of players per instance is primarily dictated by your game design and game code.

No.

You pay for the compute resources and bandwidth your games actually use, without monthly or annual contracts. Please see the Amazon GameLift pricing page for more information.

FlexMatch in standalone mode will cost $20 per million player packages, and $1 per matchmaking hour. FlexMatch counts a Player Package each time you submit a player’s request to play a game session. This package also includes player attributes used to evaluate a match. Matchmaking Hours is calculated as the duration FlexMatch is executing a matchmaking evaluation, rounded up to the nearest 1 microsecond.

See Amazon GameLift FlexMatch pricing page for details.

No. Please note that your Amazon GameLift Realtime Servers are run within the context of game sessions. Depending on how you’re managing game server capacity, creating new game sessions may trigger additional server instances, for which you’ll be charged standard Amazon GameLift instance prices.

No, we do not bill based on how you upload your game build. You pay for the compute resources and bandwidth your games actually use, without monthly or annual contracts.

Billing begins when you allocate Amazon GameLift capacity and Amazon GameLift launches your game’s server binary for the first time on each instance. Billing concludes when you stop instances. Both Windows and Linux instances are billed at per instance-second and have a 1 minute minimum charge per-instance.

Our SLA guarantees a Monthly Uptime Percentage of at least 99.5% for Amazon GameLift within a Region.

You are eligible for a SLA credit for Amazon GameLift if the region that you are operating in has an Monthly Uptime Percentage of less than 99.5% during any monthly billing cycle. For full details on all of the terms and conditions of the SLA, as well as details on how to submit a claim, please see https://aws.amazon.com/gamelift/sla/.

No. Only your authorized users with the necessary AWS credentials can access the Amazon GameLift console. You can use AWS Identity and Access Management (IAM) to securely share AWS credentials across a team. Please see Creating IAM Policies for Amazon GameLift for more details.

Yes. To receive a history of Amazon GameLift API calls made on your account, you simply turn on CloudTrail in the AWS Management Console.

For more information about securing AWS resources, see the AWS Security Center.

Security is a shared responsibility between AWS and you. The shared responsibility model describes this as security of the cloud and security in the cloud. You can read more about how this applies to the Amazon GameLift service in our developer guide here.