# atmos aws cloudformation render

Print the component’s CloudFormation template without deploying it. Inline
templates are evaluated as stack configuration; template files are used as written.

> ⚠️ 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 render <component> --stack <stack> [options]
```

## Examples

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

Render all or affected components in dependency order:

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

Render components selected by tags or labels:

```shell
atmos aws cloudformation render --all --tags production,tier-1
atmos aws cloudformation render --affected --labels cost-center=platform
```

## 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 bulk selection flags, limits the selected components to this stack.

## Source and Authentication

Local templates and cached sources can render offline when their configuration
does not require remote lookups. An uncached source must be downloaded first;
private S3 downloads use the component's resolved AWS identity.

Secret and output lookups can also require authentication and network access.
Use `--dry-run` for static validation without downloads or lookups. Use
[`diff`](/cli/commands/aws/cloudformation/diff) to preview changes against AWS.

## Try it out

Configure the short alias, then inspect the local example without deploying infrastructure.

```shell
atmos config set aliases.cft "aws cloudformation"
atmos cft render demo -s local
```