05 ANSWER-SAFE INCIDENT BRIEFS
AWS EC2 and Auto Scaling incident practice
Work through EC2, Auto Scaling, launch-template, cloud-init, IMDSv2, burst-credit, and EBS attachment failures.
WHY THIS TRACK MATTERS
Debug the system, not the first plausible theory.
Compute incidents are rarely solved by rebooting first. The useful skill is distinguishing launch, bootstrap, capacity, identity, and storage faults from one another.
- Read EC2 lifecycle and bootstrap evidence
- Diagnose scaling and instance replacement failures
- Choose a narrow, reversible recovery
INCIDENT QUEUE
Choose the failure you want to face.
Each preview shows the symptom and baseline while keeping the diagnosis and recovery protected.
INC-013Intermediate
The launch template references a ghost
EC2 · Auto Scaling
an Auto Scaling group cannot replace unhealthy instancesINC-014Foundational
Bootstrap never finishes
EC2 · cloud-init
new instances launch but never join the serviceINC-015Intermediate
Burst credits hit zero
EC2 · CloudWatch
latency climbs while CPU appears pinned at a low ceilingINC-016Intermediate
Metadata hardening breaks startup
EC2 · IMDSv2
new instances cannot retrieve startup credentialsINC-017Intermediate
The volume changes its name
EC2 · EBS
an application starts with an empty data directory after instance replacementFULL SIMULATION LIBRARY
Train the decision, not just the vocabulary.
Three incidents are free. Core includes 100 incidents; Complete includes all 500 for lifetime access.
Start a free incident →