Q: SQS queue is growing (consumer can't keep up).
Scale out consumer EC2/ECS instances. Use ASG scaled on ApproximateNumberOfMessagesVisible CloudWatch metric. Or move to Lambda consumer (auto-scales with queue depth).
Want to master this scenario in a live sandbox? Stephane Maarek's AWS Certified DevOps Engineer Professional Masterclass on Udemy covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "When an interviewer asks how I troubleshoot this in AWS, I frame it through my hands-on production experience. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Production Solution & Architecture
Scale out consumer EC2/ECS instances. Use ASG scaled on ApproximateNumberOfMessagesVisible CloudWatch metric. Or move to Lambda consumer (auto-scales with queue depth).
- Immediate Triage: Scale out consumer EC2/ECS instances. Use ASG scaled on ApproximateNumberOfMessagesVisible Clou
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Setting SQS visibility timeout shorter than consumer task processing duration If processing exceeds the visibility timeout, SQS returns the message to the queue, causing concurrent duplicate execution by other workers.
- Omitting a Dead Letter Queue (DLQ) redrive policy for poison pill messages Unparseable poison pill messages fail repeatedly, consuming worker capacity and cycling through retry loops indefinitely without a DLQ.
- Using SNS directly to an HTTP endpoint for mission-critical events requiring guaranteed persistence SNS is an ephemeral push notification service without persistent storage; decoupling via SQS buffers messages during consumer downtime.
- Assuming FIFO SQS queues support unlimited throughput without high-throughput mode enabled Standard FIFO queues cap throughput at 300 messages/sec (3,000 with batching) unless partition-key high-throughput mode is activated.