Skip to content

Course

Infrastructure as Code with Terraform

Declare infrastructure, don't click it — Terraform's resource model, state as the source of truth, plan/apply discipline, modules, and remote state that lets a team share one reality.

7 lessons

Course Q&A

Reviews

Enrolled members can rate this course.

No reviews yet.

IaC Thinking

Why clickops rots, what declarative means in practice, and where Terraform fits.

  1. 01Why Infrastructure as CodeClickops produces snowflake servers nobody can rebuild — IaC produces infrastructure that's reviewable, repeatable, and documented by definition.18mOpen

Terraform Mechanics

HCL, state, plan/apply, variables, and modules — the moving parts you'll use daily.

  1. 01HCL, Resources, and State: The Mental ModelResources are declared objects; state is Terraform's memory of what exists — understand that pairing and everything else follows.22mOpen
  2. 02Variables, Locals, and ModulesParameterizing configs, keeping secrets out of HCL, and modules as the unit of reuse — with the pitfalls that bite.22mMembers
  3. 03Plan, Apply, Destroy: The Lifecycleterraform plan as the contract — read the diff, understand -/+ symbols, and why 'apply without reading' is how databases get deleted.22mMembers

Real Infrastructure

Remote state, environments, and operating Terraform safely on infra that matters.

  1. 01Remote State and Locking: Terraform for TeamsS3+DynamoDB-style backends, state locking that prevents the two-apply disaster, and why local state ends at solo work.22mMembers
  2. 02Environments, Workspaces, and Repo LayoutHow real teams structure Terraform — per-env roots vs workspaces, and the monorepo layout that scales.20mMembers
  3. 03Operating Terraform SafelyThe rules that keep infrastructure code from becoming an incident: blast radius, state hygiene, drift detection, and the emergency exits.20mMembers