When an object is created under the incoming/ prefix in S3, a Systems Manager Automation runbook must validate its metadata.
Avoid polling the whole bucket or requiring an operator to start the runbook; process only matching events.
Which automation is most appropriate?
Create an EventBridge rule matching S3 Object Created events for the prefix and use a Systems Manager Automation runbook as the target.
Detailed explanation
Lifecycle manages storage-class transitions and deletion timing; it does not use Systems Manager Automation as an event target.
Lifecycle manages storage-class transitions and deletion timing; it does not use Systems Manager Automation as an event target.
EventBridge evaluates the event pattern, including a prefix, and starts the runbook only for matching events.
EventBridge evaluates the event pattern, including a prefix, and starts the runbook only for matching events.
DNS health checks measure endpoint reachability and do not deliver S3 object-created events.
DNS health checks measure endpoint reachability and do not deliver S3 object-created events.
Bucket size does not identify an individual creation event or prefix, and periodic scanning adds delay and unnecessary work.
Bucket size does not identify an individual creation event or prefix, and periodic scanning adds delay and unnecessary work.
Check official documentation
Compare the following points with the official documentation.
Amazon EventBridge event patterns、S3 events、Systems Manager Automation targetsの公式説明を確認する。
Official references
What to confirm
イベントパターン、ターゲット、実行権限の役割を区別できる。
Key points
- S3 ObjectCreated
- Event-driven automation
- EventBridge rule
- Idempotency
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current behavior in the official SOA-C03 guide and AWS service documentation.
Foundation review
Filtering
A prefix or other event-pattern condition prevents unrelated objects from starting the runbook.
Execution role
The target role grants EventBridge permission to start the Systems Manager automation.