1 回答
- 最新
- 投票最多
- 评论最多
1
Hello.
What kind of error is occurring specifically?
Also, ElasticBeanstalk creates a CloudFormation stack on the backend, so checking the CloudFormation stack may reveal the cause of the error.
If you don't need the ElasticBeanstalk environment, you should be able to delete it by directly deleting the CloudFormation stack.
The following document focuses on security groups, but I think it can be used with other AWS resources in the same way.
https://repost.aws/knowledge-center/elastic-beanstalk-deletion-failure
相关内容
- AWS 官方已更新 8 个月前
- AWS 官方已更新 9 个月前
- AWS 官方已更新 9 个月前
- AWS 官方已更新 10 个月前
Deleting the CloudFormation stack worked. Thank you!