An EC2 state-change event must be sent to another system with tags and an owning team added.
Avoid a separate Lambda for every destination and handle retry behavior in the event flow.
Which design is most appropriate?
Use EventBridge Pipes enrichment with a Lambda function or API, then route the enriched event to its target.
Detailed explanation
Event history is an audit record, not a transformable and retryable delivery pipeline.
Event history is an audit record, not a transformable and retryable delivery pipeline.
DNS routing records do not transform or deliver event payloads.
DNS routing records do not transform or deliver event payloads.
Pipes can filter an event, add information through an enrichment step, and deliver it to a target.
Pipes can filter an event, add information through an enrichment step, and deliver it to a target.
Lifecycle manages object transitions and deletion; it does not route events.
Lifecycle manages object transitions and deletion; it does not route events.
Check official documentation
Compare the following points with the official documentation.
Amazon EventBridge Pipes filtering enrichment target retryの公式説明を確認する。
What to confirm
イベントルール、Pipesのenrichment、ターゲットの責務を区別できる。
Key points
- EventBridge Pipes
- Enrichment
- Retry
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current behavior in the official SOA-C03 guide and AWS service documentation.
Foundation review
Flow stages
Filtering, enrichment, and delivery are separate stages with different failure behavior.
Operational reuse
A shared pipe can reduce duplicated integration code when targets have the same event context.