Infrastructure as Code Fundamentals

Infrastructure as code (IaC) means defining your servers, networks, databases, and cloud services in text files that a tool reads and executes. Instead of clicking through a console or running ad-hoc commands, you write a definition of what you want and let the tool make it real.

Why IaC exists

Manual infrastructure fails at scale and under pressure:

• Two environments that should be identical are not, because someone forgot a step.
• A change made in production cannot be reproduced in staging.
• No one knows what configuration a server has — it accumulated changes over years.
• Recovery from failure requires someone to remember the exact sequence of setup steps.

IaC solves these by making infrastructure a code artifact: versionable, reviewable, testable, and repeatable.

Core principles

Declarative over imperative. Most IaC tools are declarative: you describe the desired end state, and the tool figures out what changes to make. You say "I want three servers with these properties" — not "create a server, then another, then another."

Idempotency. Running the same definition twice produces the same result. If the infrastructure already matches the desired state, nothing happens. This makes IaC safe to re-apply.