Skip to main content
Definition Website Computer and Technology

Immutable Infrastructure

Subject: Computer and Technology noun /ɪˈmjuː.tə.bəl ˈɪn.frəˌstrʌk.tʃər/ 1 definition

  1. Definition (noun)

    Entry #144 · Updated

    Immutable Infrastructure is a cloud and systems-engineering paradigm in which servers, containers, and runtime environments are never modified, patched, or reconfigured in place after they are provisioned. Instead, every application release, configuration change, or security update is compiled into a new, versioned artifact—such as a machine image or container image—verified through automated testing, and deployed by launching replacement instances while draining and terminating the old ones. By forbidding live in-place edits and requiring stateful data to reside outside compute nodes in external storage or managed databases, immutable infrastructure eliminates configuration drift, enforces reproducible environments, and enables fast, reliable rollbacks to prior builds.

    Common Forms

    • Golden Virtual Machine Images: Pre-baked, versioned VM snapshots (such as Amazon Machine Images) generated by tools like HashiCorp Packer with operating-system packages, security hardening, and application binaries sealed prior to boot.

    • Container Images: Read-only, layered OCI or Docker artifacts packaging an application with its dependencies so orchestrators like Kubernetes replace entire pods rather than updating running containers in place.

    • Atomic Host Operating Systems: Minimal Linux distributions—such as Talos Linux, Fedora CoreOS, or Flatcar Container Linux—that mount core system paths read-only and apply upgrades via signed, atomic image switches across dual partitions.

    • Serverless Function Revisions: Versioned deployment archives or container artifacts published to serverless platforms (such as AWS Lambda), where each code or runtime change creates a separate immutable revision rather than altering running workers.

    Example

    When a critical OpenSSL vulnerability is disclosed, a platform team bumps the package version in their Packer template, triggering a CI pipeline that builds and verifies a new hardened Amazon Machine Image (app-v2.14.1). Instead of applying patches over SSH on live production servers, their deployment workflow updates the autoscaling launch template to app-v2.14.1, spins up healthy replacement instances behind the load balancer, and gracefully drains and terminates the older app-v2.14.0 fleet.