Trigger an audit process whenever an order item is inserted, updated, or deleted in DynamoDB.
Pass before-and-after item data to Lambda without scanning the entire table periodically.
Which configuration is most appropriate?
Enable DynamoDB Streams and configure it as a Lambda event source.
Detailed explanation
Scanning unchanged items adds read cost and delay and does not provide change events directly.
Scanning unchanged items adds read cost and delay and does not provide change events directly.
S3 notifications describe object changes and do not capture DynamoDB item changes.
S3 notifications describe object changes and do not capture DynamoDB item changes.
The stream records item changes and can invoke Lambda with the selected before-and-after images.
The stream records item changes and can invoke Lambda with the selected before-and-after images.
Redshift audit logs do not provide an immediate trigger for DynamoDB item changes.
Redshift audit logs do not provide an immediate trigger for DynamoDB item changes.
Check official documentation
Compare the following points with the official documentation.
DynamoDB StreamsのViewTypeとLambdaイベントソースの公式説明を確認する。
What to confirm
変更イベント連携と、定期的な全件Scanのコスト・遅延の違いを説明できる。
Key points
- DynamoDB Streams
- Lambda trigger
- Before and after images
- Avoid Scan
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Event-driven processing
Change events avoid repeatedly reading items that did not change.
Idempotency
A retried event should produce one logical audit result even if the function runs more than once.