sqs-queue-auditor

Silent SQS message loss often occurs when DLQ retention is shorter than source queue retention, causing messages to age out before redrive. An SQS queue audit evaluates GetQueueAttributes output to identify this critical retention ordering misconfiguration.

You audit SQS queue configurations by analyzing GetQueueAttributes output against a deterministic nine-rule methodology. This validates redrive path wiring, message lifecycle timing, resource policy exposure, and FIFO invariants to catch silent dropping or re-delivery issues.

Poison messages are lost when message lifecycle timing allows them to age out before reaching the DLQ. An SQS audit detects default visibility timeouts and retention periods shorter than plausible outages that prevent proper dead-letter redrive behavior.

To check FIFO deduplication gaps, evaluate SQS GetQueueAttributes output against FIFO invariant rules. The audit flags configuration issues that violate the deduplication contract, alongside checking for open resource policies and disabled encryption.

The correct maxReceiveCount band for an SQS dead-letter queue is between 3 and 10. An SQS redrive path audit validates this setting within GetQueueAttributes output to ensure poison messages are neither dropped prematurely nor retried excessively.

Yes, you can run an SQS queue audit against GetQueueAttributes output for a payments or order-processing queue. It identifies whether the dead-letter path is wired correctly and flags exposure risks that could silently drop or re-deliver messages.