Skip to main content

Use Case for SQS Queue No Messages Received

  1. Configure SQS Queue No Messages Received
  2. Use Case for SQS Queue No Messages Received
  3. Triage Guides by Violation Type
    1. Triage SQS Queue No Messages Received QUEUE_NO_MESSAGES_RECEIVED

SQS Queue No Messages Received Policy

This policy helps identify SQS queues where messages are being sent but not received. Such queues may continue to accumulate messages, incurring costs without effective use.

Pros and Cons​

Pros:

  • Cost Optimization: Reduces costs by identifying and addressing queues that aren't being effectively utilized.
  • Reliability: Improves system reliability by alerting on queues that may be misconfigured or unintended.

Cons:

  • False Positives: If receivers process messages irregularly, the policy might flag valid queues.

Operation​

  • messagesSentThreshold: Number of messages sent to a queue to consider before checking, by default 100 messages per hour.
  • minimumAgeThreshold: The minimum age of the queue in days, before it's checked by the policy, by default 30 days.

The policy will generate a violation when the NumberOfMessagesReceived is zero, NumberOfMessagesSent is non-zero and above the threshold, and the queue is older than the minimum age threshold. DLQs are excluded.

violationTypeIds Distinction​

  • QUEUE_NO_MESSAGES_RECEIVED: Triggered when a queue meets all the above conditions.