Starting Step Functions from EventBridge temporarily fails.
After automatic retries, retain undelivered events for investigation and later replay.
Which configuration is most appropriate?
Configure the target RetryPolicy and a dead-letter queue for events that remain undeliverable.
Detailed explanation
Discarding prevents later replay and creates a pipeline trigger gap.
Discarding prevents later replay and creates a pipeline trigger gap.
Broader authorization does not manage timeouts or failed delivery and violates least privilege.
Broader authorization does not manage timeouts or failed delivery and violates least privilege.
Retry limits handle temporary faults and the DLQ preserves final failures for replay.
Retry limits handle temporary faults and the DLQ preserves final failures for replay.
Object versions do not retain EventBridge delivery events.
Object versions do not retain EventBridge delivery events.
Check official documentation
Compare the following points with the official documentation.
EventBridge target RetryPolicy、MaximumEventAgeInSeconds、MaximumRetryAttempts、SQS DLQを確認する。
What to confirm
再試行とDLQ、イベント破棄・権限拡大の違いを説明できる。
Key points
- RetryPolicy
- Dead-letter queue
- EventBridge
- Replay
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Delivery guarantee
Retry limits prevent unbounded delay while a DLQ avoids silent loss.
Failure analysis
The event, error reason, replay procedure, and idempotency behavior should be recorded.