I recently came across a weird error in a private package CDK deploy:
{dynamo table name} already exists in stack {current stack arn}
Upon further investigation it turned out that one of our internal CDK modules for building the dynamo tables has changed how it was naming the construct, resulting in a different CloudFormation Logical ID. Since we were explicitly naming the table, the stack update could not complete, because the table already exists.
This app is a self-contained NPM module, so I wasn't able to modify the construct, but I came up with a workaround.
- Back up the dynamo table data
- Copy the raw stack yaml from CloudFormation and save it on your computer
- Delete the table resource and references from the template
- Update the stack with the new template using the CloudFormation web console
- Verify that the table was deleted (and not retained) by CloudFormation
- Redeploy the CDK app, which will create a new table
- Restore the table data
Top comments (0)