Infrastructure as Code

The arc of Infrastructure as Code: declare one real resource and apply it, see why click-ops cannot be reproduced, separate the application from the infrastructure it runs on, and learn the state-and-drift dangers that make IaC its own skill — the principle, not Terraform syntax.

Write a tiny declarative config for one real resource, preview the change, apply it, and watch the tool create exactly what the file says: the principle of infrastructure-as-code, not Terraform syntax.

A clicked-together environment works on one account, in one region, and cannot be reproduced anywhere else: the same disease Docker cured for the app, moved up one layer.

Separate deploying the application from provisioning the infrastructure, and learn why a staff engineer keeps the two jobs apart.

The dangers that make IaC its own skill: state as a fallible source of truth, drift between state and reality, and the one apply that enforces the entire config and can delete a live database.

A recap of Infrastructure as Code: infrastructure declared in a versioned file instead of clicked together, the application kept separate from the infrastructure it runs on, and the discipline of reading the plan for the destroy that a one-line edit can trigger — and where the system goes next.