Delivery · Difficulty 4 of 5 · 45 min
A change handler fails every call
A handler for data changes logs configuration errors at startup and fails every request, though nothing was redeployed. The tables named in its logs exist and look healthy, and a second one sits alongside them. Get it working again, and make sure its failures no longer disappear silently.
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
- DeliveryReleases never finish rolling outECS · 45 min · level 4
- DeliveryRequest handler fails every cold startLambda · 45 min · level 4
- DeliveryDeployment that never landedElastic Load Balancing · 20 min · level 3
- DeliveryService never settles behind the entry pointElastic Load Balancing · 90 min · level 5
- DeliveryNightly reconciliation never completesEKS · 40 min · level 3
- DeliveryOrder processor stalls after a change windowLambda · 20 min · level 3