AWS cli documentation change
Summary
Added managed capacity configuration with zero-scaling strategy. Introduced --managed-capacity-configuration option, updated min-size parameter constraints, and added documentation for automatic scaling between 0-1 instances based on game activity.
Security assessment
The changes focus on cost optimization through automatic scaling. While reducing instances to zero minimizes attack surface, there's no evidence of addressing a specific vulnerability. The documentation describes operational efficiency rather than security controls.
Diff
diff --git a/cli/latest/reference/gamelift/update-fleet-capacity.md b/cli/latest/reference/gamelift/update-fleet-capacity.md index 254f3be3d..43688aa5b 100644 --- a//cli/latest/reference/gamelift/update-fleet-capacity.md +++ b//cli/latest/reference/gamelift/update-fleet-capacity.md @@ -15 +15 @@ - * [AWS CLI 2.33.8 Command Reference](../../index.html) » + * [AWS CLI 2.33.12 Command Reference](../../index.html) » @@ -63,2 +62,0 @@ Updates capacity settings for a managed EC2 fleet or managed container fleet. Fo -Use this operation to set these fleet capacity properties: - @@ -77,0 +76,2 @@ Updates often prompt an immediate change in fleet capacity, such as when current +Use ManagedCapacityConfiguration with the “SCALE_TO_AND_FROM_ZERO” ZeroCapacityStrategy to enable Amazon GameLift Servers to fully manage the MinSize value, switching between 0 and 1 based on game session activity. This is ideal for eliminating compute costs during periods of no game activity. It is particularly beneficial during development when you’re away from your desk, iterating on builds for extended periods, in production environments serving low-traffic locations, or for games with long, predictable downtime windows. By automatically managing capacity between 0 and 1 instances, you avoid paying for idle instances while maintaining the ability to serve game sessions when demand arrives. Note that while scale-out is triggered immediately upon receiving a game session request, actual game session availability depends on your server process startup time, so this approach works best with multi-location Fleets where cold-start latency is tolerable. With a “MANUAL” ZeroCapacityStrategy Amazon GameLift Servers will not modify Fleet MinSize values automatically and will not scale out from zero instances in response to game sessions. This is configurable per-location. + @@ -92,0 +93 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/gameli + [--managed-capacity-configuration <value>] @@ -141 +142 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/gameli -> The minimum number of instances that are allowed in the specified fleet location. If this parameter is not set, the default is 0. +> The minimum number of instances that are allowed in the specified fleet location. If this parameter is not set, the default is 0. This parameter cannot be set when using a ManagedCapacityConfiguration where ZeroCapacityStrategy has a value of SCALE_TO_AND_FROM_ZERO. @@ -170,0 +172,48 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/gameli +`--managed-capacity-configuration` (structure) + +> Configuration for Amazon GameLift Servers-managed capacity scaling options. +> +> ZeroCapacityStrategy -> (string) +> +>> The strategy Amazon GameLift Servers will use to automatically scale your capacity to and from zero instances in response to game session activity. Game session activity refers to any active running sessions or game session requests. +>> +>> Possible ZeroCapacityStrategy types include: +>> +>> * **MANUAL** – (default value) Amazon GameLift Servers will not update capacity to and from zero on your behalf. +>> * **SCALE_TO_AND_FROM_ZERO** – Amazon GameLift Servers will automatically scale out MinSize and DesiredInstances from 0 to 1 in response to a game session request, and will scale in MinSize and DesiredInstances to 0 after a period with no game session activity. The duration of this scale in period can be configured using ScaleInAfterInactivityMinutes. +>> + +>> +>> Possible values: +>> +>> * `MANUAL` +>> * `SCALE_TO_AND_FROM_ZERO` +>> + +> +> ScaleInAfterInactivityMinutes -> (integer) +> +>> Length of time, in minutes, that Amazon GameLift Servers will wait before scaling in your MinSize and DesiredInstances to 0 after a period with no game session activity. Default: 30 minutes. +>> +>> Constraints: +>> +>> * min: `5` +>> * max: `1440` +>> + + +Shorthand Syntax: + + + ZeroCapacityStrategy=string,ScaleInAfterInactivityMinutes=integer + + +JSON Syntax: + + + { + "ZeroCapacityStrategy": "MANUAL"|"SCALE_TO_AND_FROM_ZERO", + "ScaleInAfterInactivityMinutes": integer + } + + @@ -305,0 +355,33 @@ Location -> (string) +ManagedCapacityConfiguration -> (structure) + +> Configuration for Amazon GameLift Servers-managed capacity scaling options. +> +> ZeroCapacityStrategy -> (string) +> +>> The strategy Amazon GameLift Servers will use to automatically scale your capacity to and from zero instances in response to game session activity. Game session activity refers to any active running sessions or game session requests. +>> +>> Possible ZeroCapacityStrategy types include: +>> +>> * **MANUAL** – (default value) Amazon GameLift Servers will not update capacity to and from zero on your behalf. +>> * **SCALE_TO_AND_FROM_ZERO** – Amazon GameLift Servers will automatically scale out MinSize and DesiredInstances from 0 to 1 in response to a game session request, and will scale in MinSize and DesiredInstances to 0 after a period with no game session activity. The duration of this scale in period can be configured using ScaleInAfterInactivityMinutes. +>> + +>> +>> Possible values: +>> +>> * `MANUAL` +>> * `SCALE_TO_AND_FROM_ZERO` +>> + +> +> ScaleInAfterInactivityMinutes -> (integer) +> +>> Length of time, in minutes, that Amazon GameLift Servers will wait before scaling in your MinSize and DesiredInstances to 0 after a period with no game session activity. Default: 30 minutes. +>> +>> Constraints: +>> +>> * min: `5` +>> * max: `1440` +>> + + @@ -316 +398 @@ Location -> (string) - * [AWS CLI 2.33.8 Command Reference](../../index.html) » + * [AWS CLI 2.33.12 Command Reference](../../index.html) »