Loading content
Infrastructure as Code (IaC) is an approach that allows infrastructure to be defined and provisioned through code. This improves efficiency, reduces the likelihood of errors, and facilitates tracking changes.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Infrastructure as code describes infrastructure in versioned, executable files so environments can be created, changed, and checked repeatedly.
The approach grew from configuration management and automation in large data-center environments. Tools such as Ansible, AWS CloudFormation, and Terraform extended it into declarative descriptions and reproducible cloud infrastructure.
Treat servers and networks like source code: a file describes the desired state, a tool applies it, and changes pass through review and version control.
Files describe how the infrastructure should look.
The same description can create a comparable environment.
Differences between the description and the real environment become visible.
IaC makes infrastructure changes traceable, reviewable, and automatable. It supports safe rollbacks but requires careful handling of secrets and state files.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.