Observability · Difficulty 3 of 5 · 15 min
Log storage costs keep climbing
Finance flags runaway storage costs from the account's logs, while compliance asks why no violation was ever reported. Log groups exist with a range of settings, one of them suspiciously short. Find what is driving the cost and bring it in line with the compliance rule.
Where the symptom shows: AWS Config
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
- ObservabilityTwo incidents that alerted nobodyLambda · 20 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