Delivery · Difficulty 5 of 5 · 90 min
Service never settles behind the entry point
The service behind the public entry point returns server errors, and discovery lookups fail now and then. Deployments keep happening but new copies cycle unhealthy. An older revision and a second discovery namespace also exist. Restore stable discovery and healthy targets.
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
- DeliveryReleases never finish rolling outECS · 45 min · level 4
- DeliveryA change handler fails every callLambda · 45 min · level 4
- DeliveryRequest handler fails every cold startLambda · 45 min · level 4
- DeliveryDeployment that never landedElastic Load Balancing · 20 min · level 3
- DeliveryNightly reconciliation never completesEKS · 40 min · level 3
- DeliveryOrder processor stalls after a change windowLambda · 20 min · level 3