AWS gamelift documentation change
Summary
Updated documentation to reflect service name change from 'Amazon GameLift' to 'Amazon GameLift Servers' throughout the document, including resource references and section headers.
Security assessment
The changes primarily involve rebranding/renaming of service references without introducing new security content or addressing specific security vulnerabilities. The IAM role mention remains unchanged as a standard security practice, but no new security features or vulnerability mitigations are added.
Diff
diff --git a/gamelift/latest/developerguide/resources-cloudformation.md index 64ac12626..008906843 100644 --- a/gamelift/latest/developerguide/resources-cloudformation.md +++ b/gamelift/latest/developerguide/resources-cloudformation.md @@ -3 +3 @@ -[Documentation](/index.html)[Amazon GameLift](/gamelift/index.html)[Developer Guide](gamelift-intro.html) +[Documentation](/index.html)[Amazon GameLift](/gamelift/index.html)[Hosting Guide](gamelift-intro.html) @@ -7 +7 @@ Best practicesUsing AWS CloudFormation stacksUpdating builds -# Managing Amazon GameLift hosting resources using AWS CloudFormation +# Managing Amazon GameLift Servers hosting resources using AWS CloudFormation @@ -9 +9 @@ Best practicesUsing AWS CloudFormation stacksUpdating builds -You can use AWS CloudFormation to manage your Amazon GameLift resources. In AWS CloudFormation, you create a template that models each resource and then use the template to create your resources. To update resources, you make the changes to your template and use AWS CloudFormation to implement the updates. You can organize your resources into logical groups, called stacks and stack sets. +You can use AWS CloudFormation to manage your Amazon GameLift Servers resources. In AWS CloudFormation, you create a template that models each resource and then use the template to create your resources. To update resources, you make the changes to your template and use AWS CloudFormation to implement the updates. You can organize your resources into logical groups, called stacks and stack sets. @@ -11 +11 @@ You can use AWS CloudFormation to manage your Amazon GameLift resources. In AWS -Using AWS CloudFormation to maintain your Amazon GameLift hosting resources offers a more efficient way to manage sets of AWS resources. You can use version control to track template changes over time and coordinate updates made by multiple team members. You can also reuse templates. For example, when deploying a game across multiple Regions, you might use the same template to create identical resources in each Region. You can also use these templates to deploy the same sets of resources in another partition. +Using AWS CloudFormation to maintain your Amazon GameLift Servers hosting resources offers a more efficient way to manage sets of AWS resources. You can use version control to track template changes over time and coordinate updates made by multiple team members. You can also reuse templates. For example, when deploying a game across multiple Regions, you might use the same template to create identical resources in each Region. You can also use these templates to deploy the same sets of resources in another partition. @@ -13 +13 @@ Using AWS CloudFormation to maintain your Amazon GameLift hosting resources offe -For more information about AWS CloudFormation, see the [AWS CloudFormation User Guide](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/). To view template information for Amazon GameLift resources, see the [ Amazon GameLift resource type reference](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_GameLift.html). +For more information about AWS CloudFormation, see the [AWS CloudFormation User Guide](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/). To view template information for Amazon GameLift Servers resources, see the [Amazon GameLift Servers resource type reference](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_GameLift.html). @@ -17 +17 @@ For more information about AWS CloudFormation, see the [AWS CloudFormation User -For detailed guidance on using AWS CloudFormation, see the [AWS CloudFormation best practices](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/best-practices.html) in the _AWS CloudFormation User Guide_. In addition, these best practices have special relevance with Amazon GameLift. +For detailed guidance on using AWS CloudFormation, see the [AWS CloudFormation best practices](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/best-practices.html) in the _AWS CloudFormation User Guide_. In addition, these best practices have special relevance with Amazon GameLift Servers. @@ -42 +42 @@ For detailed guidance on using AWS CloudFormation, see the [AWS CloudFormation b -We recommend the following structures to use when setting up AWS CloudFormation stacks for Amazon GameLift resources. Your optimal stack structure varies depending on if you are deploying your game in one location or multiple locations. +We recommend the following structures to use when setting up AWS CloudFormation stacks for Amazon GameLift Servers resources. Your optimal stack structure varies depending on if you are deploying your game in one location or multiple locations. @@ -46 +46 @@ We recommend the following structures to use when setting up AWS CloudFormation -To manage Amazon GameLift resources in a single location, we recommend a two-stack structure: +To manage Amazon GameLift Servers resources in a single location, we recommend a two-stack structure: @@ -48 +48 @@ To manage Amazon GameLift resources in a single location, we recommend a two-sta - * **Support stack** – This stack contains resources that your Amazon GameLift resources depend on. At a minimum, this stack should include the S3 bucket where you store your custom game server or Realtime script files. The stack should also include an IAM role that gives Amazon GameLift permission to retrieve your files from the S3 bucket when creating a Amazon GameLift build or script resource. This stack might also contain other AWS resources that are used with your game, such as DynamoDB tables, Amazon Redshift clusters, and Lambda functions. + * **Support stack** – This stack contains resources that your Amazon GameLift Servers resources depend on. At a minimum, this stack should include the S3 bucket where you store your custom game server or Realtime script files. The stack should also include an IAM role that gives Amazon GameLift Servers permission to retrieve your files from the S3 bucket when creating a Amazon GameLift Servers build or script resource. This stack might also contain other AWS resources that are used with your game, such as DynamoDB tables, Amazon Redshift clusters, and Lambda functions. @@ -50 +50 @@ To manage Amazon GameLift resources in a single location, we recommend a two-sta - * **Amazon GameLift stack** – This stack contains all of your Amazon GameLift resources, including the build or script, a set of fleets, aliases, and game session queue. AWS CloudFormation creates a build or script resource with files stored in the S3 bucket location and deploys the build or script to one or more fleet resources. Each fleet should have a corresponding alias. The game session queue references some or all of the fleet aliases. If you are using FlexMatch for matchmaking, this stack also contains a matchmaking configuration and rule set. + * **Amazon GameLift Servers stack** – This stack contains all of your Amazon GameLift Servers resources, including the build or script, a set of fleets, aliases, and game session queue. AWS CloudFormation creates a build or script resource with files stored in the S3 bucket location and deploys the build or script to one or more fleet resources. Each fleet should have a corresponding alias. The game session queue references some or all of the fleet aliases. If you are using FlexMatch for matchmaking, this stack also contains a matchmaking configuration and rule set. @@ -57 +57 @@ The diagram below illustrates a two-stack structure for deploying resources in a - + @@ -61 +61 @@ The diagram below illustrates a two-stack structure for deploying resources in a -When deploying your game in more than one Region, keep in mind how resources can interact across Regions. Some resources, such as Amazon GameLift fleets, can only reference other resources in the same Region. Other resources, such as a Amazon GameLift queue, are Region agnostic. To manage Amazon GameLift resources in multiple Regions, we recommend the following structure. +When deploying your game in more than one Region, keep in mind how resources can interact across Regions. Some resources, such as Amazon GameLift Servers fleets, can only reference other resources in the same Region. Other resources, such as a Amazon GameLift Servers queue, are Region agnostic. To manage Amazon GameLift Servers resources in multiple Regions, we recommend the following structure. @@ -63 +63 @@ When deploying your game in more than one Region, keep in mind how resources can - * **Regional support stacks** – These stacks contain resources that your Amazon GameLift resources depend on. This stack must include the S3 bucket where you store your custom game server or Realtime script files. It might also contain other AWS resources for your game, such as DynamoDB tables, Amazon Redshift clusters, and Lambda functions. Many of these resources are Region specific, so you must create them in every Region. Amazon GameLift also needs an IAM role that allows access to these support resources. Because an IAM role is Region agnostic, you only need one role resource, placed in any Region and referenced in all of the other support stacks. + * **Regional support stacks** – These stacks contain resources that your Amazon GameLift Servers resources depend on. This stack must include the S3 bucket where you store your custom game server or Realtime script files. It might also contain other AWS resources for your game, such as DynamoDB tables, Amazon Redshift clusters, and Lambda functions. Many of these resources are Region specific, so you must create them in every Region. Amazon GameLift Servers also needs an IAM role that allows access to these support resources. Because an IAM role is Region agnostic, you only need one role resource, placed in any Region and referenced in all of the other support stacks. @@ -65 +65 @@ When deploying your game in more than one Region, keep in mind how resources can - * **Regional Amazon GameLift stacks** –This stack contains the Amazon GameLift resources that must exist in each region where your game is being deployed, including the build or script, a set of fleets, and aliases. AWS CloudFormation creates a build or script resource with files in an S3 bucket location, and deploys the build or script to one or more fleet resources. Each fleet should have a corresponding alias. The game session queue references some or all of the fleet aliases. You can maintain one template to describe this type of stack and use it to create identical sets of resources in every Region. + * **Regional Amazon GameLift Servers stacks** –This stack contains the Amazon GameLift Servers resources that must exist in each region where your game is being deployed, including the build or script, a set of fleets, and aliases. AWS CloudFormation creates a build or script resource with files in an S3 bucket location, and deploys the build or script to one or more fleet resources. Each fleet should have a corresponding alias. The game session queue references some or all of the fleet aliases. You can maintain one template to describe this type of stack and use it to create identical sets of resources in every Region. @@ -67 +67 @@ When deploying your game in more than one Region, keep in mind how resources can - * **Global Amazon GameLift stack** – This stack contains your game session queue and matchmaking resources. These resources can be located in any Region and are usually placed in the same Region. The queue can reference fleets or aliases that are located in any Region. To place additional queues in different Regions, create additional global stacks. + * **Global Amazon GameLift Servers stack** – This stack contains your game session queue and matchmaking resources. These resources can be located in any Region and are usually placed in the same Region. The queue can reference fleets or aliases that are located in any Region. To place additional queues in different Regions, create additional global stacks. @@ -80 +80 @@ The diagrams below illustrates a multistack structure for deploying resources in -Amazon GameLift builds are immutable, as is the relationship between a build and a fleet. As a result, when you update your hosting resources to use a new set of game build files, the following need to happen: +Amazon GameLift Servers builds are immutable, as is the relationship between a build and a fleet. As a result, when you update your hosting resources to use a new set of game build files, the following need to happen: @@ -97 +97 @@ When updating a stack containing related build, fleet and alias resources, the d - 1. Retrieves the new files from S3, validates the files, and creates a new Amazon GameLift build. + 1. Retrieves the new files from S3, validates the files, and creates a new Amazon GameLift Servers build. @@ -116 +116 @@ You can also have AWS CloudFormation retain resources instead of deleting them. -If you want to have more control over when new fleets go live for players, you have some options. You can choose to manage aliases manually using the Amazon GameLift console or the CLI. Alternatively, instead of updating your build template to replace the build and fleets, you can add a second set of build and fleet definitions to your template. When you update the template, AWS CloudFormation creates a second build resource and corresponding fleets. Since the existing resources are not replaced, they are not deleted, and the aliases remain pointing at original fleets. +If you want to have more control over when new fleets go live for players, you have some options. You can choose to manage aliases manually using the Amazon GameLift Servers console or the CLI. Alternatively, instead of updating your build template to replace the build and fleets, you can add a second set of build and fleet definitions to your template. When you update the template, AWS CloudFormation creates a second build resource and corresponding fleets. Since the existing resources are not replaced, they are not deleted, and the aliases remain pointing at original fleets. @@ -128 +128 @@ When executing a resource update, if any step is not completed successfully, AWS -If you need to manually trigger a rollback, change the build template's S3 location key back to the original location and update your stack. A new Amazon GameLift build and fleet are created, and the alias switches over to the new fleet after the fleet is active. If you are managing aliases separately, you need to switch them to point to the new fleets. +If you need to manually trigger a rollback, change the build template's S3 location key back to the original location and update your stack. A new Amazon GameLift Servers build and fleet are created, and the alias switches over to the new fleet after the fleet is active. If you are managing aliases separately, you need to switch them to point to the new fleets. @@ -140 +140 @@ Preparing for game launch -Monitoring Amazon GameLift +Monitoring Amazon GameLift Servers