AWS gameliftservers documentation change
Summary
Major rewrite of remote access documentation: simplified title and introduction, updated CLI command syntax (removed unnecessary quotes), added references to container fleet access, clarified file system locations for containers vs EC2 fleets, and updated navigation links.
Security assessment
The changes are primarily editorial improvements and documentation restructuring. No security vulnerabilities, incidents, or weaknesses are mentioned. The updates clarify existing functionality (remote access via SSM) and add references to container-specific documentation. The warning about administrative access causing potential disruptions remains but is reworded without introducing new security considerations.
Diff
diff --git a/gameliftservers/latest/developerguide/fleets-remote-access.md b/gameliftservers/latest/developerguide/fleets-remote-access.md index a162e5bd2..dbc7964a6 100644 --- a//gameliftservers/latest/developerguide/fleets-remote-access.md +++ b//gameliftservers/latest/developerguide/fleets-remote-access.md @@ -7,26 +7 @@ Remote access through the consoleRemote access with the AWS CLIConnect to an ins -# Remotely connect to Amazon GameLift Servers fleet instances - -You can connect to any instance in your active Amazon GameLift Servers managed EC2 or container fleets. Common reasons to remotely access an instance include: - - * Troubleshoot issues with your game server integration. - - * Fine-tune your runtime configuration and other fleet-specific settings. - - * Get real-time game server activity, such as log tracking. - - * Run benchmarking tools using actual player traffic. - - * Investigate specific issues with a game session or server process. - - - - -When connecting to an instance, consider these potential issues: - - * You can connect to any instance in an active fleet. Generally, you can't connect to non-active fleets, such as fleets that are in the process of activating or are in an error state. (These fleets might have limited availability for a short period of time.) For help with fleet activation issues, see [Debug Amazon GameLift Servers fleet issues](./fleets-creating-debug.html). - - * Connecting to an active instance doesn't affect the instance's hosting activity. The instance continues to start and stop server processes based on the runtime configuration. It activates and runs game sessions. The instance might shut down in response to a scale down event or other event. - - * Any changes you make to files or settings on the instance might impact the instance's active game sessions and connected players. - - +# Connect to fleet instances @@ -33,0 +9 @@ When connecting to an instance, consider these potential issues: +You can remotely connect to any active Amazon GameLift Servers managed EC2 or managed container fleet instance to troubleshoot game server issues, inspect logs, and debug runtime behavior. Connect using the Amazon GameLift Servers console or the AWS CLI. @@ -37 +13 @@ When connecting to an instance, consider these potential issues: -You can connect to fleet instances directly from the Amazon GameLift Servers console using Amazon EC2 Systems Manager (SSM). This method provides secure access without requiring additional setup or credential management. +You can connect to fleet instances directly from the Amazon GameLift Servers console using Amazon EC2 Systems Manager (SSM). This method provides secure access without requiring additional setup or credential management. For container fleets, after connecting to the instance, you can access individual containers running on it. For more information, see [Connect to containers](./containers-remote-access.html). @@ -78,2 +54,2 @@ The following instructions describe how complete these tasks using the AWS CLI. - --fleet-id "fleet-2222bbbb-33cc-44dd-55ee-6666ffff77aa" \ - --location ""sa-east-1" + --fleet-id fleet-2222bbbb-33cc-44dd-55ee-6666ffff77aa \ + --location sa-east-1 @@ -110,2 +86,2 @@ For example: - aws gamelift describe-fleet-attributes / - --fleet-ids "fleet-2222bbbb-33cc-44dd-55ee-6666ffff77aa" + aws gamelift describe-fleet-attributes \ + --fleet-ids fleet-2222bbbb-33cc-44dd-55ee-6666ffff77aa @@ -128,2 +104,2 @@ For example: - aws gamelift describe-build / - --build-id "build-3333cccc-44dd-55ee-66ff-00001111aa22" + aws gamelift describe-build \ + --build-id build-3333cccc-44dd-55ee-66ff-00001111aa22 @@ -146 +122 @@ For example: -If the instance you want to connect to is running a game build with server SDK version 5.x, connect to the instance using Amazon EC2 Systems Manager (SSM). You can access remote instances that are running either Windows or Linux. +If the instance you want to connect to is running a game build with server SDK version 5.x, connect to the instance using Amazon EC2 Systems Manager (SSM). You can access remote instances that are running either Windows or Linux. For container fleets, after connecting to the instance, you can access individual containers running on it. For more information, see [Connect to containers](./containers-remote-access.html). @@ -248 +224,3 @@ SSH example: -Regardless of whether you have connected to an instance remotely through the console or the AWS CLI, you have full user and administrative access to it. This means you also have the ability to cause errors or failures with game hosting. If the instance is hosting games with active players, you may run the risk of crashing game sessions and dropping players, or disrupting game shutdown processes which could cause errors in saved game data and logs. +Once connected to a fleet instance, you have full user and administrative access. This means you also have the ability to cause errors or failures with game hosting. If the instance is hosting games with active players, you might run the risk of crashing game sessions and dropping players, or disrupting game shutdown processes which could cause errors in saved game data and logs. + +For container fleets, after accessing the container (see [Connect to containers](./containers-remote-access.html)), the following file locations apply within the container filesystem. For EC2 fleets, these file locations apply directly on the instance. @@ -285 +263 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Debug fleet issues +Remotely access fleet resources @@ -287 +265 @@ Debug fleet issues -Scaling +Connect to containers