Pulumi CDK Importer Tool Plugin

Assists migrating CDK-managed infrastructure to pulumi-cdk.

Caution

This is currently an experimental tool. It may not be able to migrate all CDK stacks and may have undocumented behaviors and/or bugs. Users should carefully test the behavior before using on production stacks.

Installation

pulumi plugin install tool cdk-importer

Usage

❯ pulumi plugin run cdk-importer -- --help
Usage of /Users/mjeffryes/.pulumi/plugins/tool-cdk-importer-v0.0.1-alpha.3/pulumi-tool-cdk-importer:
  -stack string
    	CloudFormation stack name to import

To migrate your existing CDK infrastructure to pulumi-cdk:

1. Follow instructions in the pulumi/pulumi-cdk repo to embed your CDK stacks in a Pulumi program

2. Instead of running pulumi up, run pulumi plugin run cdk-importer -- -stack $CFStackName. This will import the state of the infrastructure defined by your CDK stack into Pulumi state. This operation is read-only (with the below exceptions) and should not modify any resources.

3. To verify that everything worked as expected, run pulumi preview. It should show no changes.

Unsupported Resources

There are some resources that the tool is unable to import. Some of these resources are related to assets and will be created by the tool.

Resources that will be created

• Resources required by CDK File Assets
  • aws:s3/bucketObjectv2:BucketObjectv2
  • aws:s3/bucketV2:BucketV2
  • aws:s3/bucketLifecycleConfigurationV2:BucketLifecycleConfigurationV2
  • aws:s3/bucketServerSideEncryptionConfigurationV2:BucketServerSideEncryptionConfigurationV2
  • aws:s3/bucketPolicy:BucketPolicy
  • aws:s3/bucketVersioningV2:BucketVersioningV2
• Resources required by CDK Image Assets
  • aws:ecr/repository:Repository
  • aws:ecr/lifecyclePolicy:LifecyclePolicy

Due to pulumi/pulumi-cdk#293

• aws:iam/policy:Policy
• aws:iam/rolePolicyAttachment:RolePolicyAttachment

Resources that will not be imported

• CFN Custom Resources (aws-native:cloudformation:CustomResourceEmulator).
  • Upvote #6 if this affects you