AWS gameliftservers documentation change
Summary
Updated fleet creation documentation with restructured workflow steps, clarified requirements for IAM roles/TLS certificates, removed script deployment options, and improved console navigation instructions
Security assessment
While the changes include security-adjacent elements like IAM roles and TLS certificates, these are existing security features being clarified rather than new security documentation. The TLS certificate punctuation fix and IAM role reference update don't indicate a security vulnerability being addressed. No evidence of patching vulnerabilities or responding to security incidents in the changes.
Diff
diff --git a/gameliftservers/latest/developerguide/fleets-creating.md b/gameliftservers/latest/developerguide/fleets-creating.md index 0ca4f89fd..faac55068 100644 --- a//gameliftservers/latest/developerguide/fleets-creating.md +++ b//gameliftservers/latest/developerguide/fleets-creating.md @@ -11,7 +10,0 @@ When you create a new managed EC2 fleet resource, you immediately initiate the f - * [How Amazon GameLift Servers fleet creation works](./fleets-intro.html#fleets-creation-workflow) - - * [Debug Amazon GameLift Servers fleet issues](./fleets-creating-debug.html) - - - - @@ -29,8 +22 @@ Console -In the [Amazon GameLift Servers console](https://console.aws.amazon.com/gamelift/), use the navigation pane to open the **Fleets** page. Choose **Create fleet** to start the fleet creation workflow. - -**Step 1 Choose compute type** - - -Select the **Managed EC2** option and choose **Next**. - -**Step 2 Define fleet details** +In the [Amazon GameLift Servers console](https://console.aws.amazon.com/gamelift/), use the navigation pane to open the **Managed EC2, Fleets** page. Choose **Create managed EC2 fleet** to start the fleet creation workflow. @@ -37,0 +24 @@ Select the **Managed EC2** option and choose **Next**. +**Step 1 Define managed EC2 fleet details** @@ -39 +25,0 @@ Select the **Managed EC2** option and choose **Next**. -In this step, specify some fleet-wide settings. @@ -45 +31 @@ In this step, specify some fleet-wide settings. - * Choose a binary type and specify an uploaded build or script. + * Choose **Binary type: Build**. Choose a build from the list of server builds that you've previously uploaded to Amazon GameLift Servers. @@ -47 +33 @@ In this step, specify some fleet-wide settings. - * Skip the sections on additional details and tags. + * Skip the Additional details and Tags sections to use default settings. @@ -54 +40 @@ In this step, specify some fleet-wide settings. - 1. Enter a fleet **Name**. We recommend using a fleet naming pattern that makes it easier to identify fleet types when viewing lists of fleets. + 1. Enter a fleet **Name**. Fleet names are descriptive only, useful for sorting or filtering a list of fleets. They don't need to be unique. @@ -56 +42 @@ In this step, specify some fleet-wide settings. - 2. Provide a short **Description** of the fleet. + 2. Provide a short fleet **Description** to include any custom information you want to capture about the fleet. @@ -58 +44 @@ In this step, specify some fleet-wide settings. - 3. For **Binary type** , select **Build** to indicate that you're deploying a custom game server build, or select or **Script** if you're deploying Amazon GameLift Servers Realtime to this fleet. Select an uploaded build or script from the dropdown list. + 3. Select **Binary type, Build** , and use the dropdown list to choose a game server build that you've previously uploaded to Amazon GameLift Servers. @@ -60 +46 @@ In this step, specify some fleet-wide settings. - 2. (Optional) Set **Additional details** as needed. + 2. Set **Additional details** as needed. @@ -62 +48 @@ In this step, specify some fleet-wide settings. - 1. If your game server executable needs to access other AWS resources in your account, specify an IAM **Instance role** with the necessary permissions. For more information, including how to authorize other server-side applications (such as CloudWatch agent), see [Communicate with other AWS resources from your fleets](./gamelift-sdk-server-resources.html). This setting can't be changed after you create the fleet. + 1. If your game server executable needs to access other AWS resources in your account, specify an IAM **Instance role** with the necessary permissions. For more information, including how to authorize other server-side applications (such as CloudWatch agent), see [Connect your Amazon GameLift Servers hosted game server to other AWS resources](./gamelift-sdk-server-resources.html). This setting can't be changed after you create the fleet. @@ -66 +52 @@ You must create the role before you create a fleet that uses it. In addition, to - 2. Turn on the **Generate a TLS certificate** option to set up authentication and encryption for your game, Game clients use this certificate to authenticate a game server when connecting and encrypt all client/server communication. For each instance in a TLS-enabled fleet, Amazon GameLift Servers also creates a new DNS entry with the certificate. This setting can't be changed after you create the fleet. + 2. Turn on the **Generate a TLS certificate** option to set up authentication and encryption for your game, Game clients use this certificate to authenticate a game server when connecting and encrypt all client/server communication. For each instance in a TLS-enabled fleet. Amazon GameLift Servers also creates a new DNS entry with the certificate. This setting can't be changed after you create the fleet. @@ -68 +54 @@ You must create the role before you create a fleet that uses it. In addition, to - 3. If you want to combine metric data for this fleet and others, specify a **Metric group** name. Use the same metric group name for all fleets that you want to combine together. View metrics for the metric group to see the aggregated data. + 3. Amazon GameLift Servers emits metric data for each individual fleet. If you want to combine metric data for multiple fleets, specify a **Metric group** name. Use the same metric group name for all fleets that you want to combine metrics for. Use CloudWatch to view the aggregated metric group data. @@ -70 +56 @@ You must create the role before you create a fleet that uses it. In addition, to - 3. (Optional) Add **Tags** to the fleet resource. Each tag consists of a key and an optional value, both of which you define. Assign tags to AWS resources that you want to categorize in useful ways, such as by purpose, owner, or environment. Choose **Add new tag** for each tag that you want to add. + 3. Add **Tags** to the fleet resource. Each tag consists of a key and an optional value, both of which you define. Assign tags to AWS resources that you want to categorize, such as by purpose, owner, or environment. Choose **Add new tag** for each tag that you want to add. @@ -77 +63 @@ You must create the role before you create a fleet that uses it. In addition, to -**Step 3 Define instance details** +**Step 2 Define instance details** @@ -80 +66 @@ You must create the role before you create a fleet that uses it. In addition, to -In this step, specify the type of hosting resources to use and where you want to deploy them. By choosing multiple locations, you can deploy your game server to a wider geographical location, which puts them closer to your players and minimizes latency. Not all EC2 instance types are available in all locations. +In this step, select the type of hardware resources to use for your game servers and specify where you want to deploy them. By choosing multiple locations, you can deploy your game server to a wider geographical location, which puts them closer to your players and minimizes latency. All EC2 instances in a fleet must be the same type. Not all instance types are available in all locations. @@ -84 +70 @@ In this step, specify the type of hosting resources to use and where you want to - * Don't add remote locations. + * Start with deploying to the home location only. You don't need to add remote locations for initial development and testing. @@ -88 +74 @@ In this step, specify the type of hosting resources to use and where you want to - * Set instance type to "c5.large". This commonly used instance type is available in all AWS Regions. + * Set instance type to "c5.large". This commonly used instance type is available in all AWS Regions. You can optimize your hardware usage later. @@ -97 +83 @@ In this step, specify the type of hosting resources to use and where you want to -To learn more about supported locations, including how to use an AWS Region that isn't enabled by default, see [Amazon GameLift Servers service locations](./gamelift-regions.html) for managed hosting. Also review Amazon GameLift Servers [quotas](https://aws.amazon.com/general/latest/gr/gamelift.html#limits_gamelift) on locations per fleet. +To learn more about supported locations, including how to use an AWS Region that isn't enabled by default, see [Amazon GameLift Servers service locations](./gamelift-regions.html) for managed hosting. Also review Amazon GameLift Servers [quotas](https://docs.aws.amazon.com/general/latest/gr/gamelift.html#limits_gamelift) on locations per fleet. @@ -109 +95 @@ For more information about choosing an instance type, see [Instance types](./gam -Graviton Arm instances require an Amazon GameLift Servers server build on Linux OS. Server SDK 5.1.1 or newer is required for C++ and C#. Server SDK 5.0 or newer is required for Go. These instances provide no out-of-the-box support for Mono installation on Amazon Linux 2023 (AL2023) or Amazon Linux 2 (AL2). +Graviton Arm instances require a server build for a Linux AMI. Server SDK 5.1.1 or newer is required for C++ and C#. Server SDK 5.0 or newer is required for Go. These instances do not provide out-of-the-box support for Mono installation on Amazon Linux 2023 (AL2023) or Amazon Linux 2 (AL2). @@ -138 +124 @@ In this step, describe how you want each instance in the fleet to run your game - 1. Enter the **Launch path** to an executable file in your build. On Windows instances, game server executables are built to the path `C:\game`. On Linux instances, game servers are built to `/local/game`. Examples: `C:\game\MyGame\server.exe`, `/local/game/MyGame/server.exe`, or `MyRealtimeLaunchScript.js`. + 1. Enter the **Launch path** to an executable file in your build. On Windows instances, game server executables are built to the path `C:\game`. On Linux instances, game servers are built to `/local/game`. Examples: `C:\game\MyGame\server.exe` or `/local/game/MyGame/server.exe`. @@ -176 +162 @@ Review your settings before creating the fleet. Although some settings can be up - * Build or script: To deploy an update to your game server build or script, you must create a new fleet. + * Game server binary: To deploy an update to your game server build, you must create a new fleet. @@ -317 +303 @@ Managed EC2 fleets -Customize your EC2 managed fleets +Managed container fleets