When creating a new CloudFormation stack, CREATE fails with the following error:
[RESOURCE] already exists in stack [DELETE_COMPLETE status stack ARN]
I have already verified the resource is no longer in the AWS account.
AWS CloudFormation stack fails create due to resource already exists in stack that has been deleted
4.4k Views Asked by josesigna At
1
There are 1 best solutions below
Related Questions in AWS-CLOUDFORMATION
- Slick query for one to optional one (zero or one) relationship
- No Suitable Driver Found For My Java Application Code
- How to grant privileges to current user
- Selecting a count from my database using Java and Netbeans
- ActiveMQ offline message transfer on database level
- Not able to update db table from one server to another server in JAVA
- How to use CachedRowSet in Google App Engine?
- Where should ? be placed in a PreparedStatement?
- How to figure out the optimal fetch size for the select query
- Microsoft SQL Server JDBC Driver -SSL issues
Related Questions in SERVERLESS
- Slick query for one to optional one (zero or one) relationship
- No Suitable Driver Found For My Java Application Code
- How to grant privileges to current user
- Selecting a count from my database using Java and Netbeans
- ActiveMQ offline message transfer on database level
- Not able to update db table from one server to another server in JAVA
- How to use CachedRowSet in Google App Engine?
- Where should ? be placed in a PreparedStatement?
- How to figure out the optimal fetch size for the select query
- Microsoft SQL Server JDBC Driver -SSL issues
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
It's happening with me too (us-east-1), since yesterday (2020-09-30). I tried to redeploy (the same stack) several times WITHOUT SUCCESS.
I also tried:
It seems to be an AWS bug, I would suggest you opening a ticket on AWS support to try to solve it (I'm doing it)
One alternative is to create a new stack changing the resource name (here we usually use a suffix on the resource, based on stackname variable to have multiples deploys stacks)