Observability · Difficulty 3 of 5 · 20 min
Two incidents that alerted nobody
On call missed two incidents last week: a spike of errors went unnoticed, and storage costs climbed because old log entries were kept. Everything looks in place at a glance. Find what is silently disconnected in each case and make the next incident reach someone.
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
- ObservabilityAn error spike no alarm noticedLambda · 20 min · level 3
- ObservabilityLog storage costs keep climbingAWS Config · 15 min · level 3
- ObservabilityEvery run fails and nothing explains whyStep Functions · 20 min · level 3
- ObservabilityNo trace of public API trafficAPI Gateway · 15 min · level 2
- ObservabilityAssistant activity is no longer recordedBedrock AgentCore · 10 min · level 1
- ObservabilityModel usage leaves no recordAmazon Bedrock · 10 min · level 1