Availability · Difficulty 1 of 5 · 5 min
Failover reacts far too slowly
During recent trouble on the primary side, automated failover left customers on a failing site for minutes. The failover records are in place and the monitoring reports. Make failover react promptly to real trouble.
Where the symptom shows: Route 53
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
- AvailabilityCallers turned away at trivial trafficAPI Gateway · 20 min · level 3
- 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
- AvailabilityContainers lose connectivity mid-requestElastic Load Balancing · 45 min · level 4
- AvailabilityOutbound traffic reaches nothingLambda · 45 min · level 4