Infrastructure as Code Explained

Setting up a server by clicking through a cloud console feels productive — until you need to do it again, or explain what you did, or find out why last month's setup broke. There's no record, no repeatability, just a configuration living in one person's memory. Infrastructure as Code (IaC) is the fix: instead of clicking, you write down your infrastructure as files.

The problem with clicking

Manual setup has three quiet failures. It's not repeatable — rebuilding means retracing every click from memory. It's not reviewable — no one can diff or sign off on a change you made in a web UI. And it drifts — reality slowly diverges from what anyone thinks is deployed. Every one of those is a future outage waiting to happen.

What IaC actually is

You describe the servers, networks, databases, and rules you want in text files, and a tool reads those files and makes the real infrastructure match. The files live in Git alongside your app, so your infrastructure gets the same superpowers your code already has: version history, code review, and a rerun button.

# a taste: describe a server, don't click to create it
resource "server" "web" {
  image = "ubuntu-24.04"
  size  = "small"
  count = 3          # want three? change the number, re-apply.
}

Declarative beats step-by-step

Good IaC tools are declarative: you state the end result you want, not the clicks to get there. The tool compares your description to what exists and makes only the changes needed to close the gap. Want three servers instead of two? Change 2 to 3, re-run, and it adds one — no manual steps, no guesswork about current state.

IaC turns "I set this up somehow last spring" into "here's the file that defines it, in Git, reviewed, and rebuildable in minutes." Your infrastructure stops being a mystery and becomes a document.

Why it matters

Because the definition is code, you can rebuild an entire environment from scratch, spin up an identical staging copy, review infra changes in a pull request, and recover from disaster by re-applying files instead of frantically remembering. Terraform, Pulumi, and Ansible are common tools, but the principle outlives any one of them.

The mental model to keep

Stop thinking of infrastructure as something you do and start thinking of it as something you describe. The description is the source of truth; the tool's job is to make the world match the file. Written down, versioned, reviewable, repeatable — that's the whole win.