Availability · Difficulty 4 of 5 · 40 min
The fleet never replaces a dead node
Capacity has sat below target since one node stopped answering. Health checks and replacement rules both exist and read as active, yet the silent node stays and the fleet stays short, all in one availability zone. The operations team wrote down what normal looks like. Make the fleet replace a node that stops serving.
Where the symptom shows: EC2
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
- 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
- AvailabilityCallers turned away at trivial trafficAPI Gateway · 20 min · level 3