Terraform: Manage Infrastructure as Code

Why it exists

Before Infrastructure as Code (IaC), managing servers and networks was a manual process of clicking through a cloud provider's web console. This was slow, error-prone, hard to reproduce consistently, and impossible to version control. Terraform was created to solve this by allowing you to manage infrastructure programmatically.

The mental model

Terraform is like a general contractor for your cloud infrastructure. You give it a blueprint (a configuration file) describing the final state you want: "I need two web servers, a database, and a load balancer." Terraform then figures out the exact steps to build, modify, or demolish resources to make reality match the blueprint. It uses specific plugins called "providers" to talk to each service's API, whether it's AWS, GCP, or even a DNS service.

How it works

You write your desired infrastructure in a human-readable language called HCL (HashiCorp Configuration Language). The workflow has three main steps. First, terraform init prepares your project and downloads the necessary providers. Second, terraform plan shows you a dry run of exactly what will be created, changed, or destroyed. Finally, terraform apply executes that plan. Terraform records what it built in a special "state file" to keep track of your infrastructure.

When to use it

Use Terraform to manage any resource that has an API. It's most common for provisioning low-level cloud components like compute instances, storage, and networking on AWS, Azure, and GCP. It's also great for higher-level components like DNS entries, SaaS features, or even creating GitHub repositories. Its main strength is creating identical, reproducible environments for development, staging, and production.

When not to use it

Terraform is not a configuration management tool like Ansible or Puppet. Terraform is excellent at provisioning a server, but it's not the right tool for installing software or managing files inside that server once it's running. While you can force it to run scripts on startup, dedicated tools are better suited for configuring the software layer.

One canonical example

A classic use case is deploying a web application. A Terraform configuration would define a VPC (a private network), subnets, security groups (firewall rules), a virtual server to run the application, a managed database for data storage, and a load balancer to distribute traffic. With a single terraform apply command, this entire stack is provisioned in the correct dependency order.