Integrating with AWS Cloud Development Kit (CDK)»
To use AWS Cloud Development Kit in an AWS CloudFormation stack you'll need to do two things: create a Docker image with AWS CDK and invoke it in
Preparing the image»
Since our base image doesn't support AWS CDK, you will have to build your image that includes it as well as any tooling needed to run whatever language your infrastructure declaration is written in.
The example below shows a Dockerfile with attached
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
You should build it, push it to a repository, and set it as the Runner Image of your Stack.
For the AWS CDK code to be properly interpreted by Spacelift, you have to customize the default stack workflow by enriching them with hooks.
To create a CloudFormation template that can be interpreted by Spacelift, you will have to add these hooks to the
cdk bootstrap- to bootstrap your AWS CDK project.
cdk synth- to create a CloudFormation template.
Multiple template AWS CDK definition»
The default CloudFormation integration in Spacelift uses a single CloudFormation template. That means that AWS CDK definitions that generate multiple templates will only have a single template picked up for further processing. To mitigate this, consider unifying the AWS CDK definition to generate a single template file.
Our integration doesn't use
cdk deploy, but rather uses template definitions created by
cdk deploy deploys Lambda assets to S3 which are used to deploy Lambdas by CloudFormation.
Our process won't upload assets, so deploying Lambdas via a Spacelift stack configured to handle AWS CDK will result in errors.