What Is Terraform? Infrastructure as Code Explained

Terraform is a tool developed by HashiCorp that allows engineering teams to manage infrastructure using code. A Terraform project defines resources such as servers, databases, networks, storage, permissions, Kubernetes clusters, and third-party platform settings in configuration files.

In simple terms, you describe the infrastructure you want, and Terraform builds and manages it automatically. If the configuration changes later, Terraform detects the difference and prepares the infrastructure changes needed to match the new desired state.

Terraform became foundational because it turns infrastructure from a fragile manual process into a structured engineering system. Teams can review changes, reuse patterns, automate environments, and reduce undocumented cloud dashboard work.

Infrastructure as Code, often shortened to IaC, is the practice of managing infrastructure through version-controlled configuration files instead of manual setup steps. Infrastructure becomes part of the engineering workflow, not a separate set of undocumented clicks.

Historically, an engineer might manually configure networking, provision virtual machines, create firewall rules, attach storage, and assign permissions through AWS, Azure, or Google Cloud dashboards. That approach creates drift over time because different environments slowly diverge.

Infrastructure as Code solves this by making the desired architecture explicit. The configuration can be reviewed, tested, reused, and automated the same way application code can be reviewed, tested, reused, and automated.

Terraform configurations are written in HCL, or HashiCorp Configuration Language. HCL is human-readable, structured, declarative, and designed for automation workflows.

Declarative is the key word. With an imperative workflow, engineers define every step. With Terraform, engineers define the desired final state, and Terraform determines execution order, dependencies, provisioning logic, and reconciliation.

provider "aws" {
  region = "us-west-2"
}

resource "aws_instance" "web_server" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t3.micro"

  tags = {
    Name        = "Production-Web-Server"
    Environment = "Production"
  }
}

This configuration tells Terraform to provision an AWS EC2 instance using a specific image, machine type, and set of tags. If the configuration changes, Terraform can detect the difference and plan an update.

You cannot truly understand Terraform without understanding state. When Terraform provisions infrastructure, it records mappings between your configuration and real resources in a state file, commonly named terraform.tfstate.

State acts as Terraform's infrastructure ledger. It helps Terraform understand what already exists, what changed, and what needs to happen next. Without state, Terraform would need to rediscover every resource from provider APIs during each operation.

In team environments, state is usually stored remotely in systems such as Terraform Cloud, AWS S3, Azure Storage, or Google Cloud Storage. Remote state supports collaboration, locking, shared visibility, and safer infrastructure changes.