Delivery · Difficulty 3 of 5 · 20 min
Order processor stalls after a change window
A processing function started timing out and complaining about settings it can no longer find right after last night's change window, with no code deployment. The table it writes to exists and is reachable. The team documented the expected operating values: find them and restore them.
Where the symptom shows: Lambda
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
- DeliveryDeployment that never landedElastic Load Balancing · 20 min · level 3
- DeliveryNightly reconciliation never completesEKS · 40 min · level 3
- DeliveryReleases never finish rolling outECS · 45 min · level 4
- DeliveryNew intake workers never startEKS · 12 min · level 2
- DeliveryA change handler fails every callLambda · 45 min · level 4
- DeliveryRequest handler fails every cold startLambda · 45 min · level 4