Start processing when a data file arrives in S3 rather than at a fixed time.
Ignore events from other buckets and key prefixes.
Which automation approach is most appropriate?
Filter S3 events with an EventBridge event pattern and target a workflow or function; make processing idempotent for duplicate events.
Detailed explanation
Polling increases API calls, latency, and cost and can miss a clean event boundary.
Polling increases API calls, latency, and cost and can miss a clean event boundary.
Bucket and object-key conditions can route only matching events to a target.
Bucket and object-key conditions can route only matching events to a target.
Post-processing audit logs is not a low-latency arrival trigger.
Post-processing audit logs is not a low-latency arrival trigger.
A storage-class transition is not general event routing for newly arrived objects.
A storage-class transition is not general event routing for newly arrived objects.
Check official documentation
Compare the following points with the official documentation.
Amazon EventBridge S3 event patterns、targets、S3 event notificationsの公式説明を確認する。
What to confirm
ポーリングとイベントパターンによる起動の違いを説明できる。
Key points
- EventBridge
- Event pattern
- S3 object key
- Idempotency
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
At-least-once delivery
Event consumers should expect duplicates and use a stable object or event identifier.
Narrow routing
Prefix, suffix, bucket, account, and region filters reduce accidental invocations.