# atmos aws cloudformation logs

Show the combined CloudFormation event log across a stack and every nested
stack beneath it (up to 10 levels deep), merged into a single chronological
timeline — instead of having to check each nested stack's events separately.

> ⚠️ Experimental

## Usage

```shell
atmos aws cloudformation logs <component> --stack <stack> [options]
```

```shell
atmos aws cloudformation logs vpc -s plat-ue2-dev
```

Render a per-resource timeline instead of a flat chronological list:

```shell
atmos aws cloudformation logs vpc -s plat-ue2-dev --chart
```

Show logs for all or affected components in dependency order:

```shell
atmos aws cloudformation logs --all -s plat-ue2-dev
atmos aws cloudformation logs --affected --base origin/main
```

## Flags

- **`--stack`, `-s` (required)**
  Atmos stack.
- **`--chart` (optional)**
  Render a per-resource timeline (one line per logical resource ID, showing its status transitions in order) instead of a flat chronological event list.
- **`--all` (optional)**
  Show logs for all 
  `aws/cloudformation`
   components in dependency order.
- **`--affected` (optional)**
  Show logs 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.

## Output

By default, every event from the stack and its nested stacks is printed in
timestamp order, the same as a single stack's event stream. With `--chart`,
events are grouped by logical resource ID instead, one line per resource
showing its status transitions in order:

```
NatGateway                    CREATE_IN_PROGRESS -> CREATE_COMPLETE
SubnetsStack                  CREATE_IN_PROGRESS -> CREATE_COMPLETE
```

:::note
`logs` does not fire `before`/`after` hook events — only
[`apply`](/cli/commands/aws/cloudformation/apply),
[`diff`](/cli/commands/aws/cloudformation/diff), and
[`delete`](/cli/commands/aws/cloudformation/delete) do.
:::