- Newest
- Most votes
- Most comments
Issue could be that you might have associated the security group sg-8d849bf4 to another resource, for example if a new instance is launched with this security group, in that case stack deletion fails. You can find the resource and manually remove the association or you can skip the resource and try deleting it again.
Just a quick note:
Modify the resources in your environment only by using Elastic Beanstalk. If you modify resources using another service's console, CLI commands, or SDKs, Elastic Beanstalk won't be able to accurately monitor the state of those resources, and you won't be able to save the configuration or reliably recreate the environment. Out-of band-changes can also cause issues when terminating an environment.
Ref - https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.managing.html
Relevant content
- asked a year ago
- asked 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 3 years ago