What is the purpose of the _defaults.yaml pattern?

It is a convention used to store shared configurations at various directory levels (org, tenant, stage) which are then imported by top-level stacks to ensure consistency.

Can I use Atmos with tools other than Terraform?

Yes, Atmos provides native support for both Terraform and Helmfile, and can be extended to other tools like Packer or OpenTofu via command overrides.

What is an Atmos stack manifest?

A stack manifest is a YAML file that declares components and their configurations for a specific combination of organization, account, region, and stage, utilizing imports to stay DRY.

How does Atmos handle configuration merging?

Atmos uses a deep-merge algorithm where maps are recursively merged and lists are replaced, following a precedence order from global scope down to specific component overrides.

Atmos Stack Configuration

Name: Atmos Stack Configuration
Author: cloudposse

bycloudposse

•

1,293

•

Deployment & DevOps

Orchestrates hierarchical YAML configurations for Atmos to maintain DRY, scalable infrastructure deployments across environments.

The atmos-stacks skill empowers Claude with expert knowledge of the Atmos orchestration framework, specifically focusing on stack manifest management. It enables the creation and maintenance of complex infrastructure hierarchies using imports, deep merging, and inheritance. By separating configuration from code, this skill helps users manage Terraform and Helmfile components across multiple accounts, regions, and stages while minimizing repetition and ensuring configuration consistency.

Key Features

01Dynamic value resolution via YAML functions and outputs

02Component-level metadata and lifecycle hook management

03Hierarchical YAML imports and multi-level inheritance

04Stack manifest discovery and precedence resolution

05Deep-merging of variables, environment variables, and settings

061,293 GitHub stars

Use Cases

01Troubleshooting complex configuration merges across nested stack manifests

02Refactoring flat Terraform variables into DRY, hierarchical Atmos stacks

03Designing multi-tenant cloud architectures with shared organizational defaults

Key Features

01Dynamic value resolution via YAML functions and outputs

02Component-level metadata and lifecycle hook management

03Hierarchical YAML imports and multi-level inheritance

04Stack manifest discovery and precedence resolution

05Deep-merging of variables, environment variables, and settings

061,293 GitHub stars

Use Cases

01Troubleshooting complex configuration merges across nested stack manifests

02Refactoring flat Terraform variables into DRY, hierarchical Atmos stacks

03Designing multi-tenant cloud architectures with shared organizational defaults