Loading content
AWS CloudFormation is an infrastructure-as-code service for modeling, provisioning and managing AWS resources through declarative JSON or YAML templates. It automates creation, updates and deletion of stacks, handling dependencies, rollbacks and change sets. Teams use it to codify environments, enable repeatable deployments, integrate with CI/CD and enforce…
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
AWS CloudFormation is an infrastructure-as-code service that describes AWS resources in declarative JSON or YAML templates, deploys them as stacks, and manages them through their lifecycle.
AWS CloudFormation was developed by Amazon Web Services and released on February 25, 2011. It grew out of the practical problem of managing AWS infrastructure without manual console work: teams needed a reproducible text form for describing, versioning, sharing, and operating resources as a single unit. YAML support and features such as drift detection came later.
Think of CloudFormation as a blueprint with execution logic. A template defines the desired state, parameters supply environment-specific values, and a stack is the concrete instance in AWS. When a stack is created or updated, CloudFormation reads the template, orders dependencies, applies changes in the correct sequence, and can roll back if something fails. Change sets let you review planned changes before execution.
The JSON or YAML file describes desired resources, properties, and optional conditions.
A stack groups the AWS resources created from a template into one managed unit.
Input values make templates flexible across environments and easier to reuse.
CloudFormation determines the order in which resources are created, updated, or deleted.
A change set shows planned adjustments before they are applied; if something fails, rollback can restore the prior state.
Reconciliation reveals when live resources diverge from the expected template configuration.
CloudFormation is useful when environments must be built reproducibly, deployed through CI/CD, or enforced against standards. It reduces manual console work and makes coordinated changes across many accounts or environments easier. Its value depends on well-maintained templates; complex dependencies, AWS lock-in, and drift caused by manual edits remain important trade-offs.
Where this building block is located in the topic model.
No structure path available.
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.