Skip to main content

Using CloudFormation

CloudFormation components let you deploy AWS CloudFormation templates with the same stack configuration, inheritance, authentication, and dependencies used by other Atmos components. Atmos calls the AWS SDK directly; the aws CLI is not required.

Experimental

Use a CloudFormation component when you already have a template or need AWS resources that fit CloudFormation. A component can refer to a template file or define the template inline in its stack manifest. Each stack can supply its own parameters, region, account identity, and delivery target.

components:
  "aws/cloudformation":
    vpc:
      stack_name: vpc
      path: vpc.yaml
      parameters:
        Environment: dev

The vpc key is the component name in this stack. The template file is resolved from the configured CloudFormation component directory. See the CloudFormation stack configuration for the full schema, inline templates, changesets, drift detection, and StackSets.

Next steps​