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公式更新しました 9ヶ月前- AWS公式更新しました 7ヶ月前
Deleting the CloudFormation stack worked. Thank you!