S3 and DynamoDB produce differently shaped events.
Before Step Functions, create a common JSON containing source, object ID, and event time.
Which configuration is most appropriate?
Use an EventBridge Input Transformer to map event fields into a common target payload.
Detailed explanation
Metric conditions do not standardize an event payload.
Metric conditions do not standardize an event payload.
Storage class changes storage characteristics, not event JSON.
Storage class changes storage characteristics, not event JSON.
It extracts event fields and formats a target payload with a consistent structure.
It extracts event fields and formats a target payload with a consistent structure.
Authorization scope changes, but the event payload is not transformed.
Authorization scope changes, but the event payload is not transformed.
Check official documentation
Compare the following points with the official documentation.
EventBridge Input Transformer、InputPathMap、InputTemplateの公式説明を確認する。
What to confirm
イベント変換と保存・権限・監視設定を区別できる。
Key points
- Input Transformer
- EventBridge
- InputPathMap
- InputTemplate
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Contract transformation
A common event schema reduces source-specific logic in the downstream workflow.
Missing fields
Optional values, types, nulls, and payload size need explicit template behavior.