AWS gameliftservers documentation change
Summary
Updated regional availability table with new regions (Asia Pacific Thailand), reordered entries, corrected terminology (e.g., 'EC2 managed fleet' to 'managed fleets'), fixed FlexMatch documentation link formatting, and added Denver local zone.
Security assessment
Changes focus on updating regional service availability and documentation accuracy. No security vulnerabilities, configurations, or features are mentioned. Terminology changes (e.g., 'managed fleets') appear to be branding/consistency updates rather than security-related.
Diff
diff --git a/gameliftservers/latest/developerguide/gamelift-regions.md b/gameliftservers/latest/developerguide/gamelift-regions.md index 6b1fbdcfe..20a607b82 100644 --- a//gameliftservers/latest/developerguide/gamelift-regions.md +++ b//gameliftservers/latest/developerguide/gamelift-regions.md @@ -13 +13 @@ Amazon GameLift Servers features are available across multiple AWS Regions and L -The following table is a list of AWS Regions and Local Zones that support Amazon GameLift Servers resources. It indicates which resources you can create in each location. +The following table is a list of AWS Regions and Local Zones that support Amazon GameLift Servers resources. It indicates the types of resources that you can create in each location. @@ -15 +15 @@ The following table is a list of AWS Regions and Local Zones that support Amazon -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 +Geographic location | Location code | Home Region for managed fleets (single location) | Home Region for managed fleets (multi-location) | Remote location for managed fleets (multi-location) | Anywhere fleet | Game session queue | FlexMatch matchmaker and rule set @@ -21,0 +22 @@ Africa (Cape Town) | af-south-1 | | | Yes | | | +Asia Pacific (Thailand) | ap-southeast-7 | | | Yes | | | @@ -23,3 +24 @@ 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 (Malaysia) | ap-southeast-5 | | | Yes | | | @@ -26,0 +26,2 @@ Asia Pacific (Mumbai) | ap-south-1 | Yes | | Yes | Yes | Yes | +Asia Pacific (Osaka) | ap-northeast-3 | | | Yes | | | +Asia Pacific (Seoul) | ap-northeast-2 | Yes | Yes | Yes | Yes | Yes | Yes @@ -28,0 +30 @@ Asia Pacific (Sydney) | ap-southeast-2 | Yes | Yes | Yes | Yes | Yes | Yes +Asia Pacific (Tokyo) | ap-northeast-1 | Yes | Yes | Yes | Yes | Yes | Yes @@ -31,2 +32,0 @@ Europe (Frankfurt) | eu-central-1 | Yes | Yes | Yes | Yes | Yes | Yes -Europe (Stockholm) | eu-north-1 | | | Yes | | | -Europe (Milan) | eu-south-1 | | | Yes | | | @@ -34,0 +35 @@ Europe (London) | eu-west-2 | Yes | | Yes | Yes | Yes | +Europe (Milan) | eu-south-1 | | | Yes | | | @@ -35,0 +37 @@ Europe (Paris) | eu-west-3 | | | Yes | | | +Europe (Stockholm) | eu-north-1 | | | Yes | | | @@ -40,0 +43 @@ Dallas local zone | us-east-1-dfw-1 | | | Yes | | | +Denver local zone | us-west-2-den-1 | | | Yes | | | @@ -43 +45,0 @@ Kansas City local zone | us-east-1-mci-1 | | | Yes | | | -Denver local zone | us-west-2-den-1 | | | Yes | | | @@ -89 +91 @@ For more information about creating an Anywhere fleet and testing your game serv -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 AWS 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 AWS Region. You can create FlexMatch resources in any of the AWS Regions that support them. +FlexMatch resources are used to process player requests for matchmaking. They include a matchmaking configuration resource and a rule set resource. Processing takes place in the AWS Region where the FlexMatch resources are located. To reduce latency in the matchmaking process, create 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 AWS Region. You can create FlexMatch resources in any of the AWS Regions that support them. @@ -91 +93 @@ FlexMatch resources are used to process player requests for matchmaking. The inc -For more information about setting up FlexMatch for your hosting solution, see the [Amazon GameLift ServersFlexMatch developer guide](https://docs.aws.amazon.com/gamelift/latest/flexmatchguide/match-intro.html). +For more information about setting up FlexMatch for your hosting solution, see the [Amazon GameLift Servers FlexMatch developer guide](https://docs.aws.amazon.com/gameliftservers/latest/flexmatchguide/match-intro.html).