Terraform — Infrastructure as Code for Any Cloud

What it is

Terraform is an open-source infrastructure-as-code tool by HashiCorp. You write declarative configuration files (HCL) that describe your desired infrastructure state, and Terraform figures out what API calls to make to reach that state. It supports 3000+ providers including AWS, Azure, GCP, Kubernetes, Cloudflare, and Datadog.

Terraform targets DevOps engineers, platform teams, and any developer who provisions cloud resources. Whether you manage a single VPS or a multi-cloud enterprise environment, Terraform provides a consistent workflow: write, plan, apply.

How it saves time or tokens

Without Terraform, provisioning infrastructure means clicking through cloud consoles or writing imperative scripts that break when APIs change. Terraform replaces that with a declarative approach: you describe what you want, not how to get there. The plan step shows exactly what will change before you apply, eliminating surprise modifications. State tracking means Terraform knows what already exists and only modifies the delta.

How to use

1. Install Terraform:

brew install terraform            # macOS
apt install terraform             # Debian/Ubuntu

1. Write a configuration file defining your resources.

1. Run the standard workflow:

terraform init       # Download providers
terraform plan       # Preview changes
terraform apply      # Apply changes
terraform destroy    # Tear down when done

Example

# main.tf -- Create an AWS S3 bucket
terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.0"
    }
  }
}

provider "aws" {
  region = "us-east-1"
}

resource "aws_s3_bucket" "data" {
  bucket = "my-app-data-bucket"

  tags = {
    Environment = "production"
    ManagedBy   = "terraform"
  }
}

Run terraform apply and Terraform creates the S3 bucket. Run it again and nothing changes because the state already matches.

Related on TokRepo

• DevOps Tools -- Infrastructure automation and deployment tools
• Automation Tools -- Tools for automating repetitive infrastructure tasks

Common pitfalls

• Storing Terraform state locally works for learning but breaks in teams. Use remote state backends (S3 + DynamoDB, Terraform Cloud, or GCS) for shared environments.
• Importing existing resources into Terraform state requires terraform import and manually writing the matching HCL. It is tedious but necessary to avoid duplicates.
• Provider version pinning is important. An unpinned provider can upgrade and introduce breaking changes on your next terraform init.