Availability · Difficulty 4 of 5 · 45 min
Containers lose connectivity mid-request
Containers lost connectivity mid-request and health checks flapped across the service. Network metrics show heavy packet loss and added latency with no code change, and a processor alarm paged nobody. Find what is disrupting the service and bring it back to full health.
Where the symptom shows: Elastic Load Balancing
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
- AvailabilityFailover that never fails overRoute 53 · 45 min · level 4
- AvailabilityThe fleet never replaces a dead nodeEC2 · 40 min · level 4
- AvailabilityPower loss in one availability zoneEC2 · 45 min · level 4
- AvailabilityOutbound traffic reaches nothingLambda · 45 min · level 4
- AvailabilityConnections drop when the writer changesRDS · 45 min · level 4
- AvailabilityCallers turned away at trivial trafficAPI Gateway · 20 min · level 3