Terraform & Infrastructure as Code Engineering Bootcamp Certificate

Checkpoint 1: Provision a small cloud environment with version-pinned providers, variables, outputs and explicit dependency structure; capture init/plan/apply/destroy evidence.
Checkpoint 2: Refactor into reusable modules for network, compute/service and data layers; enforce naming/tagging conventions and validate plans before apply.
Checkpoint 3: Move state to a remote backend with locking and protected access; demonstrate state inspection, backup/recovery and a safe workspace/environment strategy.
Checkpoint 4: Create a controlled drift scenario, detect it with plan/refresh-only evidence and reconcile it; import one pre-existing resource without accidental replacement.
Checkpoint 5: Add policy/guardrails and automated validation/testing for formatting, syntax, security or cost-sensitive rules; document what blocks a deployment and why.
Checkpoint 6: Build a GitHub Actions pipeline that runs fmt/validate/plan, requires approval for apply, protects secrets and produces auditable infrastructure-change evidence.

Day 1: Choose a cloud scenario and define architecture, environments, naming/tags, security constraints, state strategy, budget assumptions and acceptance
Day 2: Build base Terraform using pinned providers, variables, locals, data sources and outputs; run reproducible plan/apply/destroy against a sandbox
Day 3: Refactor into modules and multiple environments; document module interfaces, dependency graph, versioning strategy and one design tradeoff.
Day 4: Configure remote state and locking; simulate drift and import an unmanaged resource, then reconcile without destructive surprise and capture evidence.
Day 5: Add policy/validation and infrastructure tests; create negative cases that intentionally fail and document the guardrail or policy rationale.
Day 6: Build GitHub Actions CI/CD with fmt/validate/plan, plan artifact, approval gate and protected apply; inject a failed run and show safe recovery.
Day 7: Publish repo, architecture, module docs, state/governance design, plan artifacts, test/policy results, pipeline evidence, cost/security notes and runbook.