EventBridge delivers events to Lambda.
Retry transient failures and retain events that continue to fail so they can be investigated.
Which design is most appropriate?
Configure an EventBridge target retry policy and a dead-letter queue to separate transient failures from persistent failures.
Detailed explanation
DNS TTL does not control EventBridge delivery retries.
DNS TTL does not control EventBridge delivery retries.
Discarding removes the event needed for investigation and reprocessing.
Discarding removes the event needed for investigation and reprocessing.
EventBridge can retry transient failures and store persistent failures in a DLQ.
EventBridge can retry transient failures and store persistent failures in a DLQ.
S3 storage alone does not configure retries for an EventBridge target.
S3 storage alone does not configure retries for an EventBridge target.
Check official documentation
Compare the following points with the official documentation.
Amazon EventBridge retry policyとdead-letter queueの公式説明を確認する。
What to confirm
イベント配信の再試行と失敗イベント保管を設計できる。
Key points
- EventBridge
- Retry policy
- Dead-letter queue
Notes
- Environment: AWS公式EventBridgeドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Retry and retention
Retries handle transient faults while the DLQ preserves evidence for persistent faults.
Reprocessing
A retained event can be analyzed and replayed after the target problem is fixed.