Observability · Difficulty 2 of 5 · 15 min
No trace of public API traffic
After an incident, the security team finds no access records for the public interface despite steady traffic, and an alarm tied to that traffic has never recovered. Two similarly named destinations exist and both feed monitoring. Restore the records where the rest of the monitoring expects them.
Where the symptom shows: API Gateway
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
- ObservabilityAlarm fires, nobody gets pagedCloudWatch · 10 min · level 1
- ObservabilityAn error spike no alarm noticedLambda · 20 min · level 3
- ObservabilityLog storage costs keep climbingAWS Config · 15 min · level 3