Migrating from AWS CDK to Pulumi

If your team has already provisioned infrastructure using AWS CDK, and you’d like to adopt Pulumi, you have two primary strategies you can take:

• Coexist with resources provisioned by CDK by referencing stack outputs
• Convert your CDK application to Pulumi, either by using the Pulumi CDK adapter or by migrating to a Pulumi program that imports existing resources

Choosing a CDK migration path

Decide whether you want to keep writing CDK constructs or move fully to Pulumi. Pick the adapter path if you want minimal code change and to keep using CDK libraries and patterns while gaining Pulumi’s engine, state, and policy features. Pick the migration path if you want a pure Pulumi program, direct access to the Pulumi Registry packages, and the ability to refactor away from CloudFormation over time.

To keep using AWS CDK constructs while adopting Pulumi as the engine, see Using Pulumi with AWS CDK.

To migrate an existing AWS CDK application to a Pulumi program that manages your current infrastructure, see Migrating existing AWS CDK applications to Pulumi.