AWS AWSCloudFormation documentation change
Summary
Added PlayerGatewayMode property documentation detailing DDoS protection features, updated location deployment documentation, and clarified scaling policy/tagging descriptions.
Security assessment
The PlayerGatewayMode documentation explicitly describes security features like DDoS protection, traffic validation, and IP hiding. This adds security-related documentation but does not indicate resolution of a specific security flaw.
Diff
diff --git a/AWSCloudFormation/latest/TemplateReference/aws-resource-gamelift-containerfleet.md b/AWSCloudFormation/latest/TemplateReference/aws-resource-gamelift-containerfleet.md index 850cf0ba9..a30946c4b 100644 --- a//AWSCloudFormation/latest/TemplateReference/aws-resource-gamelift-containerfleet.md +++ b//AWSCloudFormation/latest/TemplateReference/aws-resource-gamelift-containerfleet.md @@ -35,0 +36 @@ To declare this entity in your CloudFormation template, use the following syntax + "PlayerGatewayMode" : String, @@ -68,0 +70 @@ To declare this entity in your CloudFormation template, use the following syntax + PlayerGatewayMode: String @@ -220 +222 @@ _Required_ : No -Property description not available. +A set of locations to deploy container fleet instances to. You can add any AWS Region or Local Zone that's supported by Amazon GameLift Servers. Provide a list of one or more AWS Region codes, such as `us-west-2`, or Local Zone names. Also include the fleet's home Region, which is the AWS Region where the fleet is created. For a list of supported Regions and Local Zones, see [ Amazon GameLift Servers service locations](https://docs.aws.amazon.com/gamelift/latest/developerguide/gamelift-regions.html) for managed hosting. @@ -299,0 +302,26 @@ _Minimum_ : `1` +`PlayerGatewayMode` + + +Configures player gateway for your fleet. Player gateway provides benefits such as DDoS protection by rate limiting and validating traffic before it reaches game servers, hiding game server IP addresses from players, and providing updated endpoints when relay endpoints become unhealthy. + +**How it works:** When enabled, game clients connect to relay endpoints instead of to your game servers. Player gateway validates player gateway tokens and routes traffic to the appropriate game server. Your game backend calls [GetPlayerConnectionDetails](https://docs.aws.amazon.com/gamelift/latest/apireference/API_GetPlayerConnectionDetails.html) to retrieve relay endpoints and player gateway tokens for your game clients. To learn more about this topic, see [DDoS protection with Amazon GameLift Servers player gateway](https://docs.aws.amazon.com/gameliftservers/latest/developerguide/ddos-protection-intro.html). + +Possible values include: + + * `DISABLED` (default) -- Game clients connect to the game server endpoint. Use this when you do not intend to integrate your game with player gateway. + + * `ENABLED` \-- Player gateway is available in fleet locations where it is supported. Your game backend can call [GetPlayerConnectionDetails](https://docs.aws.amazon.com/gamelift/latest/apireference/API_GetPlayerConnectionDetails.html) to obtain a player gateway token and endpoints for game clients. + + * `REQUIRED` \-- Player gateway is available in fleet locations where it is supported, and the fleet can only use locations that support this feature. Attempting to add a remote location to your fleet which does not support player gateway will result in an `InvalidRequestException`. + + + + +_Required_ : No + + _Type_ : String + + _Allowed values_ : `DISABLED | ENABLED | REQUIRED` + + _Update requires_ : [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement) + @@ -303 +331 @@ _Minimum_ : `1` -Property description not available. +Rule that controls how a fleet is scaled. Scaling policies are uniquely identified by the combination of name and fleet ID. @@ -316 +344 @@ _Required_ : No -Property description not available. +A list of labels to assign to the new fleet resource. Tags are developer-defined key-value pairs. Tagging AWS resources are useful for resource management, access management and cost allocation. For more information, see [ Tagging AWS Resources](https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html) in the _AWS General Reference_.