An SQS consumer repeatedly fails to process one message.
Do not block later messages, and investigate the cause before processing the failed message again.
Which architecture is most appropriate?
Configure an SQS dead-letter queue and a maximum receive count to isolate messages that repeatedly fail.
Detailed explanation
The failed message can consume processing capacity and repeatedly delay other messages.
The failed message can consume processing capacity and repeatedly delay other messages.
A DNS health check does not control queue message processing.
A DNS health check does not control queue message processing.
Discarding loses the data needed for investigation or reprocessing.
Discarding loses the data needed for investigation or reprocessing.
After a defined number of attempts, the message is isolated for investigation and controlled reprocessing.
After a defined number of attempts, the message is isolated for investigation and controlled reprocessing.
Check official documentation
Compare the following points with the official documentation.
Amazon SQS dead-letter queueの公式説明を確認する。
What to confirm
最大受信回数とDLQによる失敗隔離を説明できる。
Key points
- SQS
- Dead-letter queue
- Maximum receive count
Notes
- Environment: AWS公式SQSドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Isolation
A DLQ prevents one poison message from consuming the main queue indefinitely.
Controlled reprocessing
After investigation and remediation, an isolated message can be replayed deliberately.