Skip to main content

atmos aws cloudformation list

List deployed CloudFormation stacks in an AWS account and region. Each stack is marked as managed when its name matches a configured Atmos component.

Experimental
CloudFormation Configuration

Configure templates, parameters, and delivery targets for your component.

atmos aws cloudformation list --help

Usage​

atmos aws cloudformation list [--stack <stack>] [options]

Examples​

Annotate against the components configured in every Atmos stack:

atmos aws cloudformation list

Annotate against a single Atmos stack:

atmos aws cloudformation list --stack plat-ue2-dev

Only stacks currently in a *_COMPLETE status:

atmos aws cloudformation list --stack plat-ue2-dev --status CREATE_COMPLETE,UPDATE_COMPLETE

List stacks in a specific region:

atmos aws cloudformation list --stack plat-ue2-dev --region us-west-2

Arguments​

This command does not take positional arguments.

Flags​

--stack, -s (optional)
Atmos stack whose component names determine the managed annotation. Omit to compare against all Atmos stacks. An unknown stack is an error. Go templates in stack names are evaluated; YAML functions are not.
--identity, -i (optional)

Identity to use for authentication. Without it, list uses the single default: true identity declared in your auth configuration or stack manifests, the same way the component verbs do. If no identity can be resolved and the AWS SDK finds no credentials either, the error suggests passing --identity. --identity with no value selects interactively.

--status (optional)

Filter by stack status (comma-separated, e.g. CREATE_COMPLETE,UPDATE_COMPLETE). Values are matched case-insensitively against the CloudFormation stack statuses, so create_complete works. An unknown value is an error that names it and lists every valid status; it is rejected before any AWS call. By default every status except DELETE_COMPLETE is listed.

--region (optional)
AWS region to list stacks in. Defaults to the active identity's region, then the AWS SDK's standard resolution chain.

Behavior​

This command lists stacks in one AWS account and region. It does not take a component argument or support --all, --affected, --tags, or --labels. The --stack flag controls annotations; it does not restrict which AWS stacks are returned.

Output​

The table starts with a header row. Each following line shows whether the stack is managed (its name matches an aws/cloudformation component's configured stack_name in the queried stack, or in any stack when --stack is omitted) or unmanaged, its status, and its name:

MANAGED   STATUS                         STACK NAME
managed   CREATE_COMPLETE                vpc-plat-ue2-dev
unmanaged UPDATE_COMPLETE                some-other-stack

Try it out​

Copy the example into a new directory and make it your own:

atmos init examples/cloudformation
cd cloudformation

Requires Docker or Podman, Python 3, and network access. Deploy the demo into the local AWS emulator, inspect it, then clean up. No AWS account is needed.

atmos config set aliases.cft "aws cloudformation"
atmos emulator up aws -s local
atmos cft deploy demo -s local
atmos cft list -s local
atmos cft delete demo -s local --auto-approve
atmos emulator down aws -s local
Explore the example →Initialization and repository settings