AWS solutions documentation change
Summary
Enhanced architecture diagram description, added detailed components 31-38 for live race workflow, and expanded real-time communication section with IoT Core implementation details.
Security assessment
Item 33 and 36 document IAM-authorized pub/sub channels and IoT policy attachment for spectator connections, adding security documentation about authentication and authorization mechanisms for real-time messaging. The conditional write operations for execution locks (item 37-38) also demonstrate safety controls.
Diff
diff --git a/solutions/latest/deepracer-on-aws/architecture-overview.md b/solutions/latest/deepracer-on-aws/architecture-overview.md index 60aac1e1f..d76b0e0ac 100644 --- a//solutions/latest/deepracer-on-aws/architecture-overview.md +++ b//solutions/latest/deepracer-on-aws/architecture-overview.md @@ -30 +30 @@ Deploying this solution with the default parameters deploys the following compon - + @@ -92 +92,17 @@ Deploying this solution with the default parameters deploys the following compon - 30. A user data bucket stores all user data including trained models, evaluation results, and other assets generated during the DeepRacer workflow. + 30. A user data bucket (Amazon S3) stores all user data including trained models, evaluation results, and other assets generated during the DeepRacer workflow. + + 31. [Amazon DynamoDB Streams](https://aws.amazon.com/dynamodb/) captures item-level changes from the main table and delivers them to downstream Lambda consumers, enabling event-driven orchestration of live race evaluations and real-time broadcast of race state to spectators. + + 32. A live broadcast handler (AWS Lambda function) is triggered by the DynamoDB stream and detects relevant state changes — such as evaluation started/completed, leaderboard updates, and winner declarations — and publishes corresponding events to the IoT Core MQTT topic for the active race, delivering real-time updates to connected spectator browsers. + + 33. [AWS IoT Core](https://aws.amazon.com/iot/) provides a managed WebSocket pub/sub channel for delivering live race state updates to spectator and participant browsers. Each live race uses a dedicated MQTT topic scoped by leaderboard ID. Spectators subscribe via WebSocket; the broadcast handler publishes via IAM-authorized HTTPS. IoT Core handles connection management, fan-out, and scaling without requiring a connections table or custom connect/disconnect handlers. + + 34. [Amazon EventBridge (Rules)](https://aws.amazon.com/eventbridge/) triggers the SafetyNet Lambda whenever a live race Step Functions execution reaches a terminal state (succeeded, failed, aborted, or timed out), ensuring the execution lock is cleared and pending evaluations are retriggered without manual intervention. + + 35. Live race queue API handlers (AWS Lambda functions) back the live race queue management endpoints, handling facilitator operations including listing the queue, reordering submissions via fractional indexing, removing submissions, resetting in-progress or failed models, clearing the leaderboard, launching the live race, and declaring a winner. + + 36. An attach IoT policy handler (AWS Lambda function) grants newly authenticated users the IoT Core policy required to subscribe to live race MQTT topics over WebSocket, enabling real-time race state delivery to their browser sessions. + + 37. A stream handler (AWS Lambda function) is triggered by the DynamoDB stream and auto-starts a new Step Functions execution for a live race when one or more submissions with pending status exist in the queue, the race is in progress, autolaunch is enabled, and no execution is currently running. It acquires the execution lock via a conditional write before starting the execution. + + 38. A SafetyNet (AWS Lambda function) is invoked by EventBridge when a live race Step Functions execution reaches any terminal state. It clears the execution lock with a conditional write, applies a backoff check if the execution has failed repeatedly, and touches a pending queue item to generate a DynamoDB stream event — retriggering the stream handler to start a new execution if items remain in the queue. @@ -122,0 +139,2 @@ During model training and evaluation, Amazon Kinesis Video Streams captures vide +During live race events, AWS IoT Core supplements the video stream by delivering real-time race state updates to spectator and participant browsers via a managed WebSocket connection. As each model evaluation completes, a Lambda function publishes leaderboard changes, queue status updates, and participant notifications to an IoT Core topic, which fans the events out to all connected clients instantly. This two-channel architecture keeps the high-bandwidth video traffic on Kinesis Video Streams while routing lightweight event data through IoT Core, ensuring both streams remain responsive under concurrent viewer load. + @@ -141,0 +160 @@ AWS service | Function | Description +[AWS IoT Core](https://aws.amazon.com/iot/) | Core | Provides a managed WebSocket pub/sub channel for delivering real-time race state updates (leaderboard changes, evaluation progress, and participant notifications) to spectator browsers during live race events.