Real AWS labs. No exam dumps. No toy demos.

Build, break, troubleshoot, and fix realistic cloud environments using Terraform, AWS CLI, and real engineering workflows.

Example lab preview

realistic failure

The app cannot reach its RDS database.

Your job is to find whether the failure is networking, security groups, DNS, or database configuration, then submit proof that the connection works.

Symptom

API requests fail with database connection timeouts.

Clues

Inspect VPC routes, security groups, subnets, and the RDS endpoint.

Win condition

A validation command confirms the app can connect.

Example workflow

terraform apply
aws ec2 describe-route-tables
aws rds describe-db-instances
notforexam validate ec2-rds-connectivity

Deploy a lab environment

Investigate the issue

Fix the root cause

Validate your solution

Start with focused failures that map to real AWS work.

A backend EC2 instance cannot connect to a PostgreSQL RDS database. Find and fix the root cause.

published

60-90 minutesAround $0.50-$2 if destroyed after completion

A cross-region private HTTP path fails across VPC peering. Find the missing route, security group rule, and network ACL rule.

published

75-120 minutesAround $1-$3 if destroyed after completion

Connectivity, IAM, deployment, and runtime failures modeled after actual platform work.

Labs start from infrastructure code so debugging begins where engineering teams work.

You read signals, inspect resources, and form a root-cause hypothesis before fixing.

Cleanups, blast radius, permissions, and validation are first-class parts of each lab.

Run the platform locally, seed demo labs, and start debugging.