Immutable Infrastructure — Explained with Examples

Immutable infrastructure is an operational model where servers and infrastructure components are never modified after deployment. Instead of SSH-ing into a running server to apply a patch or update configuration, you replace it entirely with a new instance built from a golden image or machine definition.

This approach eliminates configuration drift — the gradual divergence of server configurations over time due to ad-hoc changes. By treating infrastructure as disposable, you gain reproducibility, fast rollbacks (just redeploy the previous image), and simplified debugging. Immutable infrastructure pairs naturally with Containerization and Infrastructure as Code: containers are inherently immutable, and IaC defines the golden image.

Real-world analogy. Instead of repairing a broken coffee machine by replacing its boiler (mutable), you swap the entire machine with a brand new one (immutable). The old machine is recycled. If the new machine has issues, you swap back to the previous model. Repairs are replaced by replacements.

Example (Packer golden image):

source "amazon-ebs" "web" {
  ami_name    = "web-server-{{timestamp}}"
  source_ami = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
}

build {
  sources = ["source.amazon-ebs.web"]
  provisioner "shell" {
    inline = [
      "sudo apt-get update",
      "sudo apt-get install -y nginx"
    ]
  }
}

Related terms: Infrastructure as Code, Containerization, GitOps, Blue-Green Deployment, Zero Downtime Deployment

Related tutorial: Packer for Immutable Infrastructure