AWS cli documentation change
Summary
Updated CLI version reference and expanded StatusReason error codes with specific failure scenarios (internalError, invalidSignalRequest, placementTimeout, applicationLogS3DestinationError). Added guidance about S3 bucket configuration for logs.
Security assessment
While the applicationLogS3DestinationError mentions S3 bucket configuration, this relates to operational reliability rather than security controls. Other errors describe capacity issues and request validation without security implications. No authentication, authorization, or encryption aspects are addressed.
Diff
diff --git a/cli/latest/reference/gameliftstreams/get-stream-session.md b/cli/latest/reference/gameliftstreams/get-stream-session.md index c094815d1..65088795d 100644 --- a//cli/latest/reference/gameliftstreams/get-stream-session.md +++ b//cli/latest/reference/gameliftstreams/get-stream-session.md @@ -15 +15 @@ - * [AWS CLI 2.31.16 Command Reference](../../index.html) » + * [AWS CLI 2.31.18 Command Reference](../../index.html) » @@ -273 +273 @@ Status -> (string) -> * `ERROR` : The stream session failed to activate. +> * `ERROR` : The stream session failed to activate. See `StatusReason` (returned by `GetStreamSession` and `StartStreamSession` ) for more information. @@ -296,0 +297,7 @@ StatusReason -> (string) +> +> * `internalError` : An internal service error occurred. Start a new stream session to continue streaming. +> * `invalidSignalRequest` : The WebRTC signal request that was sent is not valid. When starting or reconnecting to a stream session, use `generateSignalRequest` in the Amazon GameLift Streams Web SDK to generate a new signal request. +> * `placementTimeout` : Amazon GameLift Streams could not find available stream capacity to start a stream session. Increase the stream capacity in the stream group or wait until capacity becomes available. +> * `applicationLogS3DestinationError` : Could not write the application log to the Amazon S3 bucket that is configured for the streaming application. Make sure the bucket still exists. +> + @@ -499 +506 @@ ExportFilesMetadata -> (structure) - * [AWS CLI 2.31.16 Command Reference](../../index.html) » + * [AWS CLI 2.31.18 Command Reference](../../index.html) »