Cloud & DevOps
Lab Curriculum.

BUG FOUND: learners who know cloud terms, but cannot recover a failed deployment.

$ step-01 brushup // weeks 1–2 — Topics taught:

1. Linux basics: files, processes, logs, permissions, and SSH.
2. Docker: images, containers, volumes, and networking basics.
3. Cloud basics: compute, storage, networking, and IAM concepts.
4. CI/CD basics: build, test, deploy stages, and environment variables.
5. Git for infra: versioning config, reviewing config changes.
6. Monitoring basics: metrics, logs, alerts, and health checks.

$ step-02 debug // weeks 3–4 — Production Debugging. Tools: Docker, a cloud console / CLI, CI logs, shell, monitoring dashboards.

• BUG #1: Deployment fails in CI — read the build log, find the dependency / config error, fix it, get a green build.
• BUG #2: App is up but returns errors after deploy — roll back safely, then find the bad config / migration, fix forward.
• BUG #3: Service outage from a misconfigured environment variable / port / secret — diagnose from logs, fix, verify health checks pass.
• BUG #4: Disk / resource exhaustion slows a service — find the cause (logs, cache, runaway process), remediate, add an alert.

$ step-03 navigate // weeks 5–7 — Codebase / System Navigation:

• Trace an outage through infrastructure-as-code, service configs, and logs; write a timeline.
• Fix a config change safely across dev/staging/prod with a rollback plan.
• Add monitoring and alerting to an unmonitored service (health, error rate, latency).
• Review a peer's infra change for security, cost, and blast-radius risks.

$ step-04 ship // weeks 8–9 — Shipping Features: capstone — a stable deployment pipeline with rollback, monitoring, and an incident runbook; run a failure drill and document recovery time.

$ ship → PROOF — exact output: deployment pipeline config, monitoring/alert setup, incident runbook, and a failure-drill post-mortem with recovery steps.

$ run --lab cloud-devops → ✓ SHIPPED, job-ready