05 ANSWER-SAFE INCIDENT BRIEFS
AWS networking incident practice
Practice isolating failures across VPC routes, NACLs, security groups, load balancers, DNS, NAT gateways, and private endpoints.
WHY THIS TRACK MATTERS
Debug the system, not the first plausible theory.
Networking failures often leave every individual component looking healthy. Strong responders compare the client path, control-plane configuration, and known-good traffic before changing production.
- Trace traffic across layered AWS controls
- Separate DNS, routing, and target failures
- Recover connectivity without creating drift
INCIDENT QUEUE
Choose the failure you want to face.
Each preview shows the symptom and baseline while keeping the diagnosis and recovery protected.
INC-008Intermediate
Return traffic disappears
VPC · NACL
intermittent HTTPS timeouts from public clientsINC-009Intermediate
DNS points to yesterday
Route 53 · ALB
some clients reach a retired load balancerINC-010Intermediate
The one-way load balancer
ALB · Security Groups
load-balancer requests time out although instances answer locallyINC-011Advanced
The NAT runs out of sockets
NAT Gateway · VPC
private workloads intermittently fail outbound dependency callsINC-012Advanced
The endpoint black hole
VPC Endpoint · S3
private subnets lose access to S3 while other AWS APIs still workFULL 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 →