Skip to main content
Examples/AWS CDK with CloudFormation
EXAMPLE

AWS CDK with CloudFormation

Deploy an AWS CDK application through the native aws/cloudformation component. A before-hook synthesizes the template, Atmos previews and deploys it, and a local Floci AWS emulator stands in for an…

ComponentsHooksEmulators
Try it out View on GitHub
cloudposse / atmos

Try it out

Copy the example into a new directory and make it your own:

atmos init examples/cdk-cloudformation
cd cdk-cloudformation

Follow the README for prerequisites and next steps.

Initialization and repository settings

See it in action

RECORDED DEMO
cdk-cloudformation
Recorded from this example
Real commands. Real output.
README.md2.3 KB
View on GitHub

Notes

This example is the native CloudFormation track of the Deploy AWS CDK with lifecycle hooks tutorial. A TypeScript AWS CDK app in components/cloudformation/greeting/ creates one AWS::SSM::Parameter. The component's synth hook installs dependencies when package-lock.json changed or the CLI is missing, then runs npm run synth before diff, apply, and changeset create, so Atmos always reads a freshly synthesized cdk.out/Demo.template.json. Deployment state stays in CloudFormation.

The local stack declares a Floci AWS emulator and an aws/emulator identity in atmos.yaml points the component at it, so no AWS account is needed. Remove that identity and the emulator import to deploy to a real account.

Requirements: Node.js 22 or later, npm, and Docker or Podman for the emulator.

Usage

atmos validate stacks
atmos emulator up aws -s local
atmos aws cloudformation diff greeting -s local
atmos aws cloudformation deploy greeting -s local
atmos aws cloudformation output greeting -s local
atmos aws cloudformation delete greeting -s local --auto-approve
atmos emulator down aws -s local

Change parameters.Message in stacks/deploy/local.yaml and run diff again to see the synthesized template re-read. render and validate do not fire the hook; run npm --prefix components/cloudformation/greeting run synth (after an initial npm ci) before those commands.

Run the whole lifecycle with atmos test.