AWS appsync documentation change
Summary
Added important notice about WebSocket PubSub API availability and clarified header support methods
Security assessment
Changes focus on feature announcement and grammatical improvements. No security vulnerabilities or security features mentioned.
Diff
diff --git a/appsync/latest/devguide/real-time-websocket-client.md b/appsync/latest/devguide/real-time-websocket-client.md index e7196be14..a864bd9ae 100644 --- a//appsync/latest/devguide/real-time-websocket-client.md +++ b//appsync/latest/devguide/real-time-websocket-client.md @@ -10,0 +11,4 @@ Building a real-time WebSocket client in AWS AppSync +###### Important + +As of Mar 13, 2025, you can build a real-time PubSub API powered by WebSockets using AWS AppSync Events. For more information, see [Publish events via WebSocket](https://docs.aws.amazon.com/appsync/latest/eventapi/publish-websocket.html) in the _AWS AppSync Events Developer Guide_. + @@ -46 +50 @@ To connect and initiate a successful handshake with AWS AppSync, a WebSocket cli - * Headers – Contain information relevant to the AWS AppSync endpoint and authorization. supports the following three methods for providing headers: + * Headers – Contain information relevant to the AWS AppSync endpoint and authorization. AWS AppSync supports the following three methods for providing headers: @@ -50 +54 @@ To connect and initiate a successful handshake with AWS AppSync, a WebSocket cli - * The header information is encoded as a base64 string, derived from a stringified JSON object. This JSON object contains details relevant to the endpoint and authorization. The content of the JSON object varies depending on the authorization mode. + * The header information is encoded as a base64 string, derived from a stringified JSON object. This JSON object contains details relevant to the AWS AppSync endpoint and authorization. The content of the JSON object varies depending on the authorization mode.