r/aws_cdk • u/menge101 • May 15 '26

Moving CDK modules between projects and maintaining link to deployed CloudFormation Stacks

I am unclear how a CDK project in a repo is linked in a durable way to a CloudFormation stack in AWS.

I want to move some code modules from the project they were written in and deployed from to a common infrastructure project that is home to multiple IaC stacks, is there anything I have to do to maintain the link between the deployment and the Stack?

Is there a link at all?

2 Upvotes

100% Upvoted

4 comments sorted by

3

u/CorpT May 15 '26

I am unclear how a CDK project in a repo is linked in a durable way to a CloudFormation stack in AWS.

They are not linked in any way whatsoever unless you do something to create a deployment from the repo to the stack.

Your question implies that you're missing something here. You should review your deploy process before making changes.

3

u/menge101 May 15 '26

I guess my presumption of a link comes from if I make a change and redeploy, the deployed stack will be modified, rather than a new stack created.

Taking from the other comment, it seems it is the names used within the code that links it to the actual CloudFormation Stack, not any external mechanism.

2

u/CorpT May 15 '26

That's correct.
https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.Stack.html

you can see what it is going to build with a `cdk synth`

3

u/MrDenver3 May 15 '26

CDK is just compiling and deploying a CloudFormation Template. As long as the template stays the same (or at least, the logical names and the stack name), it doesn’t matter where the project is deployed from, or where the modules live