Interactive AWS incident scenarios

The Cloud Toolkit

Build Real AWSEngineeringJudgment

Investigate realistic AWS failures, follow the evidence, and choose what to check next.

Explore scenarios How it works

No Signup RequiredAlways Free

Real failure pathsEvidence-first decisionsInstant feedback

INC-ALB-001us-east-1

AWS infrastructure investigation

Tracing request

UserRequest

Route 53Resolved

ALBHealthy

Target GroupRouting

EC2-AHealthy

EC2-BTarget

RDSAvailable

Playable incidents

STEP

Decision-led practice

WHY

Root-cause debriefs

ZERO

Live AWS resources

How it works

From alert toroot cause.

One focused AWS incident. Four clear stages. No live cloud environment required.

10-15 min

per incident

Step-by-step

investigation

View all scenarios

Incident journey

A complete investigation in four stages

Get the incident

Start with symptoms and affected AWS services.

Inspect the evidence

Review logs, metrics, health and configuration clues.

Choose what comes next

Make the next engineering decision.

Understand the root cause

Review your path and learn a better approach.

Featured scenarios

Pick an incident.Find the root cause.

Practice realistic AWS failures through evidence and engineering decisions.

Explore all scenarios

High

Elastic Load Balancing

Application Load Balancer returning 502

Users are receiving HTTP 502 responses immediately after a production application deployment.

Identity and Access Management

IAM AccessDenied during an S3 deployment

A deployment pipeline suddenly loses permission to upload application assets to an S3 bucket.

Incident signal

Detected

12–15 minIntermediate

Medium

Amazon EC2

EC2 application cannot reach the database

An application instance is healthy but cannot establish a connection with its private RDS database.

Incident signal

Detected

15–20 minIntermediate

Browse the complete scenario library

Loading The Cloud Toolkit...

Interactive AWS incident scenarios

The Cloud Toolkit

Build Real AWSEngineeringJudgment

Investigate realistic AWS failures, follow the evidence, and choose what to check next.

Explore scenarios How it works

No Signup RequiredAlways Free

Real failure pathsEvidence-first decisionsInstant feedback

INC-ALB-001us-east-1

AWS infrastructure investigation

Tracing request

UserRequest

Route 53Resolved

ALBHealthy

Target GroupRouting

EC2-AHealthy

EC2-BTarget

RDSAvailable

Playable incidents

STEP

Decision-led practice

WHY

Root-cause debriefs

ZERO

Live AWS resources

How it works

From alert toroot cause.

One focused AWS incident. Four clear stages. No live cloud environment required.

10-15 min

per incident

Step-by-step

investigation

View all scenarios

Incident journey

A complete investigation in four stages

Get the incident

Start with symptoms and affected AWS services.

Inspect the evidence

Review logs, metrics, health and configuration clues.

Choose what comes next

Make the next engineering decision.

Understand the root cause

Review your path and learn a better approach.

Featured scenarios

Pick an incident.Find the root cause.

Practice realistic AWS failures through evidence and engineering decisions.

Explore all scenarios

High

Elastic Load Balancing

Application Load Balancer returning 502

Users are receiving HTTP 502 responses immediately after a production application deployment.

Identity and Access Management

IAM AccessDenied during an S3 deployment

A deployment pipeline suddenly loses permission to upload application assets to an S3 bucket.

Incident signal

Detected

12–15 minIntermediate

Medium

Amazon EC2

EC2 application cannot reach the database

An application instance is healthy but cannot establish a connection with its private RDS database.

Incident signal

Detected

15–20 minIntermediate

Browse the complete scenario library