Declarative, provider-agnostic infrastructure as code with a planned, reviewable change workflow. This walkthrough covers the mental model and the configuration you will actually touch.
Terraform describes infrastructure as declarative HCL, builds a dependency graph, and shows a plan of exactly what will change before it applies - across AWS, Azure, GCP and hundreds of providers.
The configuration that matters
A minimal AWS example with remote state and a variable.
terraform {
required_providers { aws = { source = "hashicorp/aws", version = "~> 5.0" } }
backend "s3" {
bucket = "acme-tfstate"
key = "prod/network.tfstate"
region = "eu-west-1"
}
}
variable "env" { type = string, default = "prod" }
resource "aws_s3_bucket" "assets" {
bucket = "acme-${var.env}-assets"
tags = { Environment = var.env }
}Principles to hold onto
- Remote, locked state; separate state per environment/component
- Pin provider and module versions; commit .terraform.lock.hcl
- Keep modules small and composable; review plans in the PR
- Use workspaces or directories, never edit prod state by hand
Everyday commands
terraform init
terraform fmt -recursive && terraform validate
terraform plan -out tfplan
terraform apply tfplanWant senior help putting Terraform to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.