Infrastructure as Code (IaC) is the practice of managing and provisioning infrastructure through machine-readable configuration files rather than manual processes.
Before IaC, infrastructure was provisioned manually through web consoles or ad-hoc scripts. This led to configuration drift, undocumented changes, and environments that were impossible to reproduce consistently.
IaC treats infrastructure definitions as software artifacts—they can be version controlled, reviewed, tested, and deployed through automated pipelines.
Successful IaC adoption requires treating infrastructure code with the same rigor as application code: use pull requests for reviews, run automated tests, enforce linting and formatting, and maintain modular, reusable components.
Teams should store state remotely with locking enabled, use separate state files per environment, and implement drift detection to catch out-of-band changes.
The companion to 'Terraform the Hard Way.' Same twenty-one crossroads, framed against what each one looks like under a framework that's already made the decisions. With concrete Atmos snippets at every step.
A guided checklist of every decision you'll make on the road from `terraform apply` to production. Not a recommendation — an education. Borrowed in spirit from Kelsey Hightower's 'Kubernetes the Hard Way.'
An internal developer platform is the icing on the cake — the reward for getting the foundation underneath into shape. Here's what I've learned about when the icing actually delivers, and why a framework matters more than the portal.
Teams keep telling themselves infrastructure is simple. 'It's just Terraform.' 'A contractor can clean it up.' Here's what those assumptions actually cost.
Open source Terraform module libraries are infrastructure's equivalent of npm and PyPI—battle-tested foundations that become even more critical when AI enters the picture.