How do I resolve the "Already Exists" error when redeploying AWS CDK code after deleting the stack?

Key Takeaways

[Music] [Applause] [Music] Hello, I'm Rio, a cloud support engineer here at the AWS office in Oakland, New Zealand. Today, I'm going to show you how to resolve the already exist error that occurs when you redeploy your AWS cloud deployment kit code after you delete the associated AWS cloud for stack. Let's get started. The already exist error was because the most stateful resources in the AWS CDK construct library have a default removal policy that's set to retain. So when you delete the cloudformation stack, the underlying AWS resource are retained in your AWS account instead of being deleted. If you specified a custom name for the resources and then try to redeploy the same CDK code, you will receive an error saying that resource already exists. To resolve this issue, you can manually delete the retain resource, change the name of the retain resource or delete the resource name. To manually delete the retain resource, first sign in to the AWS management console. Then go to the service where the retained resources exist. For example, if it's an S3 bucket, then go to the S3 console, locate and manually delete the retain resource. To change the name of the retain resource, open your CDK code for the resource. update the name parameter to a new unique value that doesn't conflict with the retained resource. And finally, to delete the resource name, remove the name parameter from the resource definition in your CDK code. This will allow CDK to generate a new unique name when you redeploy. To prevent the issue from happening again, set removal policy to destroy. Before you delete the cloudformation st, update your CDK code to set the removal policy property to removal policy dot destroy for the resource that you want to delete. Then run CDK synth to generate the cloudformation template and verify that deletion policy is set to delete. After you make any of these changes, you can run CDK deploy to redeploy your updated CDK app. So now you know how to resolve the already exists error that occurs when you redeploy your AWS CDK code after you delete the associated confirmation stack. Thanks for watching and happy cloud computing from all of us here at AWS. [Applause] [Music]