atmos aws cloudformation backend list

List every kind: aws/s3 provision target declared on the component, and whether each one's bucket currently exists.

Experimental

atmos aws cloudformation backend list --help

Usage

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

atmos aws cloudformation backend list vpc -s plat-ue2-dev
atmos aws cloudformation backend list vpc -s plat-ue2-dev --format json

Flags

--stack, -s (required)

Atmos stack.

--format, -f (optional)

Output format: table (default), yaml, or json.

--identity, -i (optional)

Atmos identity to authenticate with.

The component argument is required. Running backend list with only a stack fails with a hint that shows the full form, atmos aws cloudformation backend list <component> -s <stack>. There is no stack-wide form (see Behavior below).

Behavior

Unlike atmos terraform backend's own list verb (which lists every backend across a whole stack, with no component argument), backend list is scoped to one component: CloudFormation's provision-target model declares kind: aws/s3 targets per-component under provision.targets, not once per stack, so there is no component-independent, stack-wide backend inventory to list. backend list never needs --target — it always shows every declared target at once.

The table format prints a header row (TARGET, BUCKET, REGION, STATUS). The json and yaml formats use snake_case keys; see backend describe for the shape.