So.. I’ve long battled with “custom named” resources with cloudformation, and getting errors like:

CloudFormation cannot update a stack when a custom-named resource requires replacing. Rename dev-my-stack-myTableName and update the stack again.

I believe.. cloudformation natively can create dynamic names, or maybe it was CDK POCs I did in the past - can’t seem to remember.

sst

have support for this? I am still of two minds around whether I like the friction or not, but generally - I don’t lol. I’d prefer cdk/sst/cloudform to pick a name with a custom prefix, like

dev-my-stack-myTableNameRANDOMISH

Does

this.getLogicalId()

help?

I had looked into that before, but did not work for me - didn’t seem to have any effect but I imagine I was missing something in interface it provides.

I do the same thing. I prefix with

${stack.stackName}-

. and I ran into this same error not too long ago.. so I just commented out the DB cluster name, and then it worked fine

yeah, I had already done that - but dynamodb is giving the albeit very pretty name. I’ll dig into https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-dynamodb-table.html#cfn-dynamodb-table-tablename and https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-name.html to see what cfn is doing natively appreciate the thoughts tho @Sam Hulick 😄

ah weird