AWS gamelift documentation change
Summary
Updated service name references from 'Amazon GameLift' to 'Amazon GameLift Servers' throughout the document, including API/console references and FleetIQ mentions. Adjusted section headers and service-specific data handling descriptions to match rebranded service name.
Security assessment
Changes are primarily nomenclature updates (adding 'Servers' to service names) without altering security guidance. No new vulnerabilities or security features are introduced. Existing security practices (encryption, IAM, TLS) remain unchanged in substance.
Diff
diff --git a/gamelift/latest/developerguide/data-protection.md index 4d0558596..b8d48573f 100644 --- a/gamelift/latest/developerguide/data-protection.md +++ b/gamelift/latest/developerguide/data-protection.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 @@ Encryption at restEncryption in transitInternetwork traffic privacy -# Data protection in Amazon GameLift +# Data protection in Amazon GameLift Servers @@ -9 +9 @@ Encryption at restEncryption in transitInternetwork traffic privacy -If you're using Amazon GameLift FleetIQ as a standalone feature with Amazon EC2, see [Security in Amazon EC2](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-security.html) in the _Amazon EC2 User Guide_. +If you're using Amazon GameLift Servers FleetIQ as a standalone feature with Amazon EC2, see [Security in Amazon EC2](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-security.html) in the _Amazon EC2 User Guide_. @@ -11 +11 @@ If you're using Amazon GameLift FleetIQ as a standalone feature with Amazon EC2, -The AWS [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) applies to data protection in Amazon GameLift. As described in this model, AWS is responsible for protecting the global infrastructure that runs all of the AWS Cloud. You are responsible for maintaining control over your content that is hosted on this infrastructure. You are also responsible for the security configuration and management tasks for the AWS services that you use. For more information about data privacy, see the [Data Privacy FAQ](https://aws.amazon.com/compliance/data-privacy-faq/). For information about data protection in Europe, see the [AWS Shared Responsibility Model and GDPR](https://aws.amazon.com/blogs/security/the-aws-shared-responsibility-model-and-gdpr/) blog post on the _AWS Security Blog_. +The AWS [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) applies to data protection in Amazon GameLift Servers. As described in this model, AWS is responsible for protecting the global infrastructure that runs all of the AWS Cloud. You are responsible for maintaining control over your content that is hosted on this infrastructure. You are also responsible for the security configuration and management tasks for the AWS services that you use. For more information about data privacy, see the [Data Privacy FAQ](https://aws.amazon.com/compliance/data-privacy-faq/). For information about data protection in Europe, see the [AWS Shared Responsibility Model and GDPR](https://aws.amazon.com/blogs/security/the-aws-shared-responsibility-model-and-gdpr/) blog post on the _AWS Security Blog_. @@ -30 +30 @@ For data protection purposes, we recommend that you protect AWS account credenti -We strongly recommend that you never put confidential or sensitive information, such as your customers' email addresses, into tags or free-form text fields such as a **Name** field. This includes when you work with Amazon GameLift or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into tags or free-form text fields used for names may be used for billing or diagnostic logs. If you provide a URL to an external server, we strongly recommend that you do not include credentials information in the URL to validate your request to that server. +We strongly recommend that you never put confidential or sensitive information, such as your customers' email addresses, into tags or free-form text fields such as a **Name** field. This includes when you work with Amazon GameLift Servers or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into tags or free-form text fields used for names may be used for billing or diagnostic logs. If you provide a URL to an external server, we strongly recommend that you do not include credentials information in the URL to validate your request to that server. @@ -32 +32 @@ We strongly recommend that you never put confidential or sensitive information, -Amazon GameLift-specific data is handled as follows: +Amazon GameLift Servers-specific data is handled as follows: @@ -34 +34 @@ Amazon GameLift-specific data is handled as follows: - * Game server builds and scripts that you upload to Amazon GameLift are stored in Amazon S3. There is no direct customer access to this data once it is uploaded. An authorized user can get temporary access to upload files, but can't view or update the files in Amazon S3 directly. To delete scripts and builds, use the Amazon GameLift console or the service API. + * Game server builds and scripts that you upload to Amazon GameLift Servers are stored in Amazon S3. There is no direct customer access to this data once it is uploaded. An authorized user can get temporary access to upload files, but can't view or update the files in Amazon S3 directly. To delete scripts and builds, use the Amazon GameLift Servers console or the service API. @@ -36 +36 @@ Amazon GameLift-specific data is handled as follows: - * Game session log data is stored in Amazon S3 for a limited period of time after the game session is completed. Authorized users can access the log data by downloading it via a link in the Amazon GameLift console or by calls to the service API. + * Game session log data is stored in Amazon S3 for a limited period of time after the game session is completed. Authorized users can access the log data by downloading it via a link in the Amazon GameLift Servers console or by calls to the service API. @@ -38 +38 @@ Amazon GameLift-specific data is handled as follows: - * Metric and event data is stored in Amazon GameLift and can be accessed through the Amazon GameLift console or by calls to the service API. Data can be retrieved on fleets, instances, game session placements, matchmaking tickets, game sessions, and player sessions. Data can also be accessed through Amazon CloudWatch and CloudWatch Events. + * Metric and event data is stored in Amazon GameLift Servers and can be accessed through the Amazon GameLift Servers console or by calls to the service API. Data can be retrieved on fleets, instances, game session placements, matchmaking tickets, game sessions, and player sessions. Data can also be accessed through Amazon CloudWatch and CloudWatch Events. @@ -40 +40 @@ Amazon GameLift-specific data is handled as follows: - * Customer-supplied data is stored in Amazon GameLift . Authorized users can access it by calls to the service API. Potentially sensitive data might include player data, player session and game session data (including connection info), matchmaker data, and so on. + * Customer-supplied data is stored in Amazon GameLift Servers . Authorized users can access it by calls to the service API. Potentially sensitive data might include player data, player session and game session data (including connection info), matchmaker data, and so on. @@ -53 +53 @@ For more information about data protection, see the [AWS shared responsibility m -At-rest encryption of Amazon GameLift-specific data is handled as follows: +At-rest encryption of Amazon GameLift Servers-specific data is handled as follows: @@ -57 +57 @@ At-rest encryption of Amazon GameLift-specific data is handled as follows: - * Customer-supplied data is stored in Amazon GameLift in an encrypted format. + * Customer-supplied data is stored in Amazon GameLift Servers in an encrypted format. @@ -64 +64 @@ At-rest encryption of Amazon GameLift-specific data is handled as follows: -Connections to the Amazon GameLift APIs are made over a secure (SSL) connection and authenticated using [AWS Signature Version 4](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html) (when connecting through the AWS CLI or AWS SDK, signing is handled automatically). Authentication is managed using the IAM-defined access policies for the security credentials that are used to make the connection. +Connections to the Amazon GameLift Servers APIs are made over a secure (SSL) connection and authenticated using [AWS Signature Version 4](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html) (when connecting through the AWS CLI or AWS SDK, signing is handled automatically). Authentication is managed using the IAM-defined access policies for the security credentials that are used to make the connection. @@ -68 +68 @@ Direct communication between game clients and game servers is as follows: - * For custom game servers being hosted on Amazon GameLift resources, communication does not involve the Amazon GameLift service. Encryption of this communication is the responsibility of the customer. You can use TLS-enabled fleets to have your game clients authenticate the game server on connection and to encrypt all communication between your game client and game server. + * For custom game servers being hosted on Amazon GameLift Servers resources, communication does not involve the Amazon GameLift Servers service. Encryption of this communication is the responsibility of the customer. You can use TLS-enabled fleets to have your game clients authenticate the game server on connection and to encrypt all communication between your game client and game server. @@ -70 +70 @@ Direct communication between game clients and game servers is as follows: - * For Realtime Servers with TLS certificate generation enabled, traffic between game client and Realtime servers using the Realtime Client SDK is encrypted in flight. TCP traffic is encrypted using TLS 1.2, and UDP traffic is encrypted using DTLS 1.2. + * For Amazon GameLift Servers Realtime with TLS certificate generation enabled, traffic between game client and Realtime servers using the client SDK for Realtime is encrypted in flight. TCP traffic is encrypted using TLS 1.2, and UDP traffic is encrypted using DTLS 1.2. @@ -77 +77 @@ Direct communication between game clients and game servers is as follows: -You can remotely access your Amazon GameLift instances securely. For instances that use Linux, SSH provides a secure communications channel for remote access. For instances that are running Windows, use a remote desktop protocol (RDP) client. With Amazon GameLift FleetIQ, remote access to your instances using AWS Systems Manager Session Manager and Run Command is encrypted using TLS 1.2, and requests to create a connection are signed using SigV4. For help with connecting to a managed Amazon GameLift instance, see [Remotely connect to Amazon GameLift fleet instances](./fleets-remote-access.html). +You can remotely access your Amazon GameLift Servers instances securely. For instances that use Linux, SSH provides a secure communications channel for remote access. For instances that are running Windows, use a remote desktop protocol (RDP) client. With Amazon GameLift Servers FleetIQ, remote access to your instances using AWS Systems Manager Session Manager and Run Command is encrypted using TLS 1.2, and requests to create a connection are signed using SigV4. For help with connecting to a managed Amazon GameLift Servers instance, see [Remotely connect to Amazon GameLift Servers fleet instances](./fleets-remote-access.html).