AWS solutions documentation change
Summary
Updated solution version from 1.1.7 to 1.2.0 and added 8 new steps describing live race orchestration components including DynamoDB streams, Lambda functions for broadcast handling and safety mechanisms, IoT Core for real-time messaging, and queue management operations.
Security assessment
Step 36 explicitly describes a Lambda function that resolves caller identity and attaches IoT messaging policies, documenting an authorization mechanism for real-time subscriptions. While not fixing a vulnerability, this adds security documentation about authenticated access control.
Diff
diff --git a/solutions/deepracer-on-aws/index.md b/solutions/deepracer-on-aws/index.md index aa1dfe351..96610ee48 100644 --- a//solutions/deepracer-on-aws/index.md +++ b//solutions/deepracer-on-aws/index.md @@ -8 +8 @@ Version - 1.1.7 + 1.2.0 @@ -163,0 +164,32 @@ A user data bucket stores all user data including trained models, evaluation res +Step 31 + +An Amazon DynamoDB stream captures table changes to trigger the live race orchestration and real-time broadcasting pipelines. + +Step 32 + +A broadcast handler (AWS Lambda function) processes stream records, detects relevant state changes, builds typed events, and publishes them to the real-time messaging channel. + +Step 33 + +AWS IoT Core provides a managed MQTT message broker that delivers real-time race state updates to spectator and participant browsers via authenticated WebSocket connections. + +Step 34 + +An Amazon EventBridge rule triggers the SafetyNet function whenever a live race workflow execution reaches a terminal state, ensuring the execution lock is cleared and pending evaluations are retriggered without manual intervention. + +Step 35 + +Queue API handlers (AWS Lambda functions) handle race facilitator operations including reorder, remove, reset, clear leaderboard, launch race, and declare winner. + +Step 36 + +An attach IoT policy function (AWS Lambda) resolves the caller's identity and attaches the messaging policy, authorizing real-time subscriptions for live race viewing. + +Step 37 + +A stream handler (AWS Lambda function) monitors the stream for new or pending queue items, verifies race preconditions, acquires the execution lock, and starts the evaluation workflow. + +Step 38 + +A SafetyNet function (AWS Lambda) serves as an execution recovery handler that clears the execution lock, applies backoff logic for repeated failures, and retriggers the stream handler if items remain in the queue. +