- Newest
- Most votes
- Most comments
Hello.
Isn't termination protection set on EC2?
If it is set, try removing it.
Finished validating environment's EC2 instances for termination protection.
Validating environment's EC2 instances have termination protection disabled before performing termination.
Please check the following document for information on configuring termination protection for EC2.
https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/terminating-instances.html#Using_ChangingDisableAPITermination
Also, CloudFormation is running behind the scenes in Elastic Beanstalk, so if the CloudFormation status is "CREATE_FAILED", the following error may occur.
Therefore, you can understand better by checking which resource creation caused the problem from the CloudFormation console.
Environment named <some-name> is in an invalid state for this operation. Must be Ready
It may also be possible to delete the stack directly from the CloudFormation console.
https://repost.aws/knowledge-center/elastic-beanstalk-deletion-failure
Relevant content
- asked 5 years ago
- asked 10 months ago
- Accepted Answerasked a year ago
- asked 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
Thanks for your suggestions. Unfortunately, there are no EC2 instances nor a CloudFormation environment. No application was ever deployed to this environment. Is there something else worth checking?