Observability · Difficulty 1 of 5 · 10 min
Alarm fires, nobody gets paged
On call confirms an alarm entered its triggered state overnight, yet nobody was notified. The threshold looks right and the alarm history shows the state changes. A notification channel with no subscribers sits in the account. Get the alerts to the team.
Where the symptom shows: CloudWatch
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
- ObservabilityAssistant activity is no longer recordedBedrock AgentCore · 10 min · level 1
- ObservabilityModel usage leaves no recordAmazon Bedrock · 10 min · level 1
- ObservabilityThe activity record went quietCloudTrail · 5 min · level 1
- ObservabilityFailed runs leave no historyStep Functions · 5 min · level 1
- ObservabilityNo trace of public API trafficAPI Gateway · 15 min · level 2
- ObservabilityAn error spike no alarm noticedLambda · 20 min · level 3