Skip to main content

atmos aws cloudformation changeset execute

Execute a previously-created, named changeset (ExecuteChangeSet) and stream stack events until the operation reaches a terminal state — unlike apply, which creates (or reuses) and executes a changeset in one step, changeset execute acts on an existing changeset by name, created earlier with changeset create.

Experimental
atmos aws cloudformation changeset execute --help
 

Usage

atmos aws cloudformation changeset execute <component> --stack <stack> --changeset-name <name> [options]
atmos aws cloudformation changeset execute vpc -s plat-ue2-dev --changeset-name vpc-2026-08-25

Skip the interactive confirmation prompt:

atmos aws cloudformation changeset execute vpc -s plat-ue2-dev --changeset-name vpc-2026-08-25 --auto-approve

Flags

--stack, -s (required for a single component)
Atmos stack. Required when operating on a single component; optional (and used only to narrow the selected set) with --all/--affected.
--changeset-name (required)
Name of the changeset to execute.
--auto-approve (optional)
Skip the interactive confirmation prompt. Without it, changeset execute prompts for confirmation on a TTY before executing the changeset.
--all (optional)
Execute the named changeset for all aws/cloudformation components in dependency order.
--affected (optional)
Execute the named changeset for affected aws/cloudformation components and their dependencies.
--include-dependents (optional)
With --affected, include dependent aws/cloudformation components.
--tags (optional)
Filter by tags (comma-separated, matches any): --tags=production,tier-1. Composes with --all/--affected to narrow the selected set further; cannot be combined with a single component argument.
--labels (optional)
Filter by labels (comma-separated key=value or key:value pairs, matches all): --labels=cost-center=platform,compliance=sox. Composes with --all/--affected/--tags; cannot be combined with a single component argument.

Behavior

If the stack ends in a failed status after executing the changeset (e.g. UPDATE_ROLLBACK_COMPLETE), changeset execute exits non-zero.

note

changeset execute does not fire before/after hook events — only apply, diff, and delete do.