Availability · Difficulty 3 of 5 · 20 min
Callers turned away at trivial traffic
Clients of the public interface get 429 responses almost immediately, even at trivial traffic. A browser app on another origin also shows cross-origin errors in its console. More than one version of the interface exists. Restore normal access on the one serving live traffic.
Where the symptom shows: API Gateway
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
- AvailabilityContainers lose connectivity mid-requestElastic Load Balancing · 45 min · level 4
- AvailabilityOutbound traffic reaches nothingLambda · 45 min · level 4
- AvailabilityConnections drop when the writer changesRDS · 45 min · level 4