Anupam Dixit
08/20/2021, 7:18 AMStagingBucket cdk-hnb659fds-assets-741386957827-ap-south-1 already exists
. How to get around with this ? (or why this might be happening?)
2. SST is also creating resources prefixed with cdk-*
for iam roles and bucket names (in addition to the resources prefixed with stage name). Can I rename them somehow in my code ? So I can use prefixes like dev-*
for these resources based on the stage name ?
3. What is the role of aws ssm in serverless stack deployment ? -> I was not giving ssm permissions earlier, as I did not think it is necessary, but getting this error user is not authorized to perform: ssm:PutParameter on resource: arn:aws:ssm:ap-south-1:741386957827:parameter/cdk-bootstrap/hnb659fds/version
. Do I have to give these permissions to the user too then ?
Please let me know if any more clarification is needed.Aram
08/20/2021, 8:48 AMsst remove
and sst deploy
again resolves that issues for me, sometimes I have to manually remove the resources from aws console though.
2. You should be able to give custom names to your resources, like for example you can set the value of functionName
for functions or queueName
for queues. You can append stage to the name with something like functionName: ${scope.stage}-your-function-name
3. Not sure about this one, I think we had to create those roles manually (I'm not the devops guy)) )Anupam Dixit
08/20/2021, 11:54 AMFrank
Frank
Frank
StagingBucket cdk-hnb659fds-assets-741386957827-ap-south-1 already exists
This often happens when the CDK bootstrapped CloudFormation stack is removed. To get around this issue, remove the bucket manually.
2. The bootstrap stack is not tied to your app. CDK just needs to bootstrap once per Account/Region, even if you deploy multiple apps/stages into the same Account/Region. Prefixing the resources with the stage name is often not desired.
3. CDK stores the bootstrapped version in an SSM parameter. That requires the ssm:PutParameter
permission.Anupam Dixit
08/21/2021, 8:18 AM