liveBook · Manning

Infrastructure as code

As explained in Automating API Delivery

Infrastructure as code is the declarative definition and management of infrastructure resources and topologies in version-controlled files.

Manual provisioning can leave deployment environments inconsistent. Infrastructure as code (IaC) defines system resources and their topology in a descriptive model, so teams can manage infrastructure definitions in version control rather than relying on manual setup. section 1.2

Definitions can describe networks, virtual machines, and load balancers. Tools such as Terraform, Ansible, and AWS CloudFormation automate provisioning from those definitions. Reapplying them helps teams recreate the same environment, reduce drift, and make deployments more repeatable. section 1.2

IaC concerns infrastructure; configuration as code applies a similar version-controlled approach to deployed applications. Both fit alongside CI/CD practices that build and deploy tested artifacts. section 1.2

How Automating API Delivery covers it

How deep it goes
Defines the practice and names tools and benefits, but provides no provisioning commands or configuration walkthrough.
Examples
Names networks, virtual machines, and load balancers as resources, and Terraform, Ansible, and AWS CloudFormation as tools.
What you can do after
Apply it via Terraform, Ansible, or AWS CloudFormation to automate provisioning and recreate environments.
How it connects
Connects infrastructure as code to version control, configuration as code, and CI/CD.

Also explained in

Compare how 14 books explain infrastructure as code →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Automating API Delivery. The section links point to the parts of the book it draws on.