Fix deliberately broken cloud network infrastructure. Learn by troubleshooting real incidents.
| Provider | Status | Guide |
|---|---|---|
| Azure | ✅ Available | azure/README.md |
| AWS | ✅ Available | aws/README.md |
| GCP | ✅ Available | gcp/README.md |
- Routing & Gateways — NAT gateways, route tables, internet egress
- DNS Resolution — Private DNS zones, service discovery
- Network Security — Security groups, firewall rules, subnet isolation
- Troubleshooting — Real-world diagnostic techniques
- Deploy — Run the setup script. Infrastructure deploys with intentional misconfigurations.
- Read the incidents — Ticket descriptions tell you the symptoms. Your job is to find the root cause.
- Diagnose — SSH through the bastion host into VMs to test connectivity, check DNS, inspect services, etc.
- Fix — From your local terminal, use the cloud provider CLI (
az,aws,gcloud) to fix the misconfigured cloud resources (routes, firewall rules, DNS records, etc.). You are not editing Terraform or fixing things from inside the VMs. - Validate — Run the validation script from your local machine. It SSHes into the VMs and runs real connectivity checks.
- Clean up — Run the provider's destroy script when finished.
Report bugs, broken instructions, or unclear steps through GitHub Issues.
Read CONTRIBUTING.md for contribution guidelines and the manual testing required before opening a pull request.