Till now there is no official guide to import existing aws resources into CDK Stack. By searching AWS CDK docs you may find confusing messages about this fact. For example dynamodb docs has a title which says “Importing existing tables”, but deep-dive can reveal that it has limitations. As an example we can check out dynamodb related part. It says we can only create ITable kind of resources which is a bit different with original Table class. With ITable class we can do some operations over existing resource but they are limited. To my knowledge, CDK does not allow appropriate way of importing existing tables. I have discovered some walk-round by using CloudFormation feature.
CloudFormation Import Existing Resource
At some point CloudFormation released new feature which allows import of existing resources into a CloudFormation Stack. There is a good blog that walks through how to use that feature. It can be done from aws console by selecting an existing cloud formation stack and clicking Stack actions -> Import Resources into stack.
Then we can upload CloudFormation template json file which contains list of resources we are intended to bind with CloudFormation.
Way-round for CDK
After building CDK we get CloudFormation stack template file, we can perform the same operations on that file.
- create a basic CDK stack, with some dummy resource inside (Lets call the dummy resource as D-resource). It can be any kind of resource (ex: SNS Topics are could candidate, created really fast). Make sure you are working on the same region where you want to perform import of existing resource (Lets call existing resource as E-resource).
- build and deploy CDK stack with D-resource
- modify the code of CDK stack by adding a E-resource. It means just declare the same kind resource with the same name.
- build the CDK stack, but DO NOT DEPLOY!
- when build is done, open project folder and find the CloudFormation template file (should be under build/cdk.out/stack-name.template.json). Lets refer to this CloudFormation template as
- open aws-console and go to CloudFormation, to find the previously deployed stack. Previously means the stack we deployed at previous step, the one that contains our D-resource. Then choose Stack actions -> Import Resources into stack and upload the
N-cf-template.jsonfile. Further steps are similar to steps described in the CloudFormation blog
- when the import is done, we can perform deployment of CDK stack (which we built but not deployed previously)
- [optional] we can remove the D-resource from CDK Stack
Te be safe it is advised to set DeletionPolicy to Retain for all new resources. That way even if something goes wrong with our import, we can make sure our existing resource stays.
Philosophy of Walk-Round
- CDK -> CloudFormation -> Create Resources
- CloudFormation -> Import Existing Resource. Binds existing resources with CloudFormation stack resource references.
- CDK -> deploy-to -> CloudFormation. When we try to deploy CDK the CloudFormation syncs up, with already containing resources.
I guess this walk-round is temporary, until AWS comes up with full working solution that works right from CDK.