Amazon GameLift service locations - Amazon GameLift
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon GameLift service locations

Amazon GameLift features are available across multiple Amazon Web Services Regions and Local Zones. You can design a hosting solution that places your game servers globally to meet your players where they're located.

Supported Amazon locations

The following table describes provides the list of supported Amazon Web Services Regions and Local Zones and indicates which Amazon GameLift resources you can create in each location.

Geographic location Location code Home region for EC2 managed fleet (single location) Home region for managed container fleet or EC2 fleet (multi-location) Remote location for managed container fleet or EC2 fleet (multi-location) Anywhere fleet Game session queue FlexMatch matchmaker and rule set
US East (N. Virginia) us-east-1 Yes Yes Yes Yes Yes Yes
US East (Ohio) us-east-2 Yes Yes Yes Yes
US West (N. California) us-west-1 Yes Yes Yes Yes
US West (Oregon) us-west-2 Yes Yes Yes Yes Yes Yes
Africa (Cape Town) af-south-1 Yes
Asia Pacific (Hong Kong) ap-east-1 Yes
Asia Pacific (Tokyo) ap-northeast-1 Yes Yes Yes Yes Yes Yes
Asia Pacific (Seoul) ap-northeast-2 Yes Yes Yes Yes Yes Yes
Asia Pacific (Osaka) ap-northeast-3 Yes
Asia Pacific (Mumbai) ap-south-1 Yes Yes Yes Yes
Asia Pacific (Singapore) ap-southeast-1 Yes Yes Yes Yes
Asia Pacific (Sydney) ap-southeast-2 Yes Yes Yes Yes Yes Yes
Canada (Central) ca-central-1 Yes Yes Yes Yes
Europe (Frankfurt) eu-central-1 Yes Yes Yes Yes Yes Yes
Europe (Stockholm) eu-north-1 Yes
Europe (Milan) eu-south-1 Yes
Europe (Ireland) eu-west-1 Yes Yes Yes Yes Yes Yes
Europe (London) eu-west-2 Yes Yes Yes Yes
Europe (Paris) eu-west-3 Yes
Middle East (Bahrain) me-south-1 Yes
South America (São Paulo) sa-east-1 Yes Yes Yes Yes
Atlanta local zone us-east-1-atl-1 Yes
Chicago local zone us-east-1-chi-1 Yes
Dallas local zone us-east-1-dfw-1 Yes
Houston local zone us-east-1-iah-1 Yes
Kansas City local zone us-east-1-mci-1 Yes
Denver local zone us-west-2-den-1 Yes
Los Angeles local zone us-west-2-lax-1 Yes
Phoenix local zone us-west-2-phx-1 Yes
Lagos, Nigeria local zone af-south-1-los-1 Yes
Note

Not all Amazon Web Services Regions are enabled by default for an Amazon Web Services account. If you want a multi-location fleet with instances in these Regions, you must enable them. For more information about Regions that aren't enabled by default and how to enable them, see Managing Amazon Web Services Regions in the Amazon Web Services General Reference. Fleets that you created before February 28, 2022 are unaffected.

In addition, you must update your Amazon GameLift administrator policy to allow the ec2:DescribeRegions action. For a policy example with Regions that aren't enabled by default, see Administration permission examples.

Locations for managed hosting

Amazon GameLift managed hosting deploys fleets of game server resources. Each fleet is created in an Amazon Web Services Region, which is the fleet's home region. A fleet's home region is referenced in the fleet's Amazon Resource Number (ARN).

You can deploy a single-region fleet, with hosting resources in the home region only. Alternatively, you can deploy a multi-location fleet, with hosting resources in multiple geographic locations. A multi-location fleet has a home region and one or more remote locations. When managing hosting capacity for a fleet, you can set capacity for each location individually. 

Remote locations for a multi-location fleet can be other Amazon Web Services Regions or Local Zones. A Local Zone is an extension of an Amazon Web Services Region, designed to place compute resources closer to users and provide low-latency gameplay. For more information, see Amazon Local Zones. The location code for a Local Zone is its parent Region code followed by a physical location identifier. For example, the code for the Los Angeles Local Zone is us-west-2-lax-1.

The following diagram illustrates a multi-location fleet with resources in two Amazon Web Services Regions and one Local Zone. The fleet's home region is us-west-2, and it has two remote locations: us-east-2 Region and us-west-2-lax-1 Local Zone.

An Amazon GameLift fleet with 2 Amazon Web Services Regions and one Local Zone. Each location hosts their own game server resources.

In addition to fleet resources, managed hosting with Amazon GameLift also uses the following resources. You create each resource in a specific Amazon Web Services Region.

  • Build – This is a game server build to be hosted with a managed EC2 fleet. Create a build resource in the same region as the fleet that it will be deployed to.

  • Script – This is a configuration script for hosting a game with Realtime Servers. Create a script resource in the same region as the fleet that it will be deployed to.

  • Container group definition and container image – This is a configuration for running containers on a managed container fleet. It identifies one or more container images with software to deploy to the container fleet. Create a container group definition and all container images (which are stored in an Amazon Elastic Container Registry repository) in the same region as the fleet they will be deployed to.

  • Game session queue – This resource processes requests for game sessions and initiates new game sessions. Processing takes place in the Amazon Web Services Region where the queue is located. To reduce latency in the game session placement process, create a queue geographically near the players that will use it.

Locations for Amazon GameLift FlexMatch

FlexMatch resources are used to process player requests for matchmaking. The include a matchmaking configuration resource and a rule set resource. Processing takes place in the Amazon Web Services Region where the FlexMatch resources are located. To reduce latency in the matchmaking process, create a the resources geographically near the players that will use it. A matchmaking configuration and the rule set it uses must be located in the same Amazon Web Services Region. You can create FlexMatch resources in any of the Amazon Web Services Regions that support them.

For more information about setting up FlexMatch for your hosting solution, see the Amazon GameLift FlexMatch developer guide.