Design patterns: stack organization, component catalogs, inheritance, configuration composition, version management, layered configuration
Design patterns are proven solutions for structuring infrastructure configuration in Atmos. They address organizational complexity by providing reusable approaches for multi-account, multi-region, enterprise-grade environments.
Most teams follow this growth path:
Inline Configuration (learning/prototyping)
|
Basic Stack Organization (dev/staging/prod)
|
Multi-Region Configuration (add regions)
|
Organizational Hierarchy (add teams/accounts/OUs)
Start with the simplest pattern that meets your needs. You do not need to start with the most complex pattern -- start simple and evolve.
One file per environment. Simplest setup for single-region, single-account-per-stage deployments.
stacks/
catalog/
vpc/
defaults.yaml # Shared component defaults
deploy/
dev.yaml # Imports catalog, sets stage: dev
staging.yaml
prod.yaml
Each environment file imports shared defaults and adds environment-specific overrides:
# stacks/deploy/dev.yaml