Resilience · Difficulty 3 of 5 · 25 min
Bad messages with nowhere to go
Malformed orders disappear after a few retries instead of landing somewhere a human can review, and nobody was alerted when processing stalled. A second worker with a very short time limit also exists. Restore both containment and visibility for messages that cannot be processed.
Where the symptom shows: SQS
Take this challenge on a live account
A live AWS account, already broken, and a clock. You fix it with the provider's own console and command line, then read a report of how you worked. We host the cloud account. Nothing lands on your bill.
More challenges
- ResiliencePoison records vanish after retriesKinesis · 15 min · level 2
- ResilienceFailed background requests vanishLambda · 15 min · level 2
- ResiliencePrivate workloads reach nothing they depend onEC2 · 90 min · level 5
- ResilienceFailed deliveries leave no traceEventBridge · 10 min · level 1
- ResilienceThe same order is processed twiceLambda · 5 min · level 1
- DeliveryDeployment that never landedElastic Load Balancing · 20 min · level 3