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
相關內容
- 已提問 6 個月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 9 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
Deleting the CloudFormation stack worked. Thank you!