# atmos aws cloudformation logs

Show events from a stack and its nested stacks in a single chronological log.
Nested stacks are included up to 10 levels deep.

> ⚠️ Experimental

**CloudFormation Configuration**

Configure templates, parameters, and delivery targets for your component.
Configuration Reference[Read more](/stacks/components/aws-cloudformation)

## Usage

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

## Examples

```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
```

## Arguments

- **`component` (required unless selecting multiple components)**
  CloudFormation component name in the Atmos stack.

## Flags

- **`--stack`, `-s` (required for a single component)**
  Atmos stack. With 
  `--all`
  , 
  `--affected`
  , 
  `--tags`
  , or 
  `--labels`
  , this is an optional stack filter; omit it to select components across stacks.
- **`--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.
- **`--follow`, `-f` (optional)**
  Continuously stream new events until interrupted (
  `tail -f`
   style) instead of returning after one pass. Press Ctrl+C to stop; the command exits 130. Cannot be combined with 
  `--chart`
  .

## 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:

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

With nested stacks, each row is prefixed with its stack name (`<stack-name>/<LogicalId>`). A stack ARN
appears only when two different stacks share a name, for example a stack that was deleted and re-created,
where the name alone would merge their rows.

This command does not fire [lifecycle hooks](/stacks/components/aws-cloudformation#lifecycle-hooks).

## Try it out

Requires Docker or Podman, Python 3, and network access for the emulator image. Run against the local AWS emulator; the final commands clean up. No AWS account is needed.

```shell
atmos config set aliases.cft "aws cloudformation"
atmos emulator up aws -s local
atmos cft deploy demo -s local
atmos cft logs demo -s local
atmos cft delete demo -s local --auto-approve
atmos emulator down aws -s local
```