Thanks for reaching out. Which region is your environment in?
It's in us-east-1.
Thanks for getting back.
Can you verify your environment still exists? I am unable to find it.
Yes, the environment with Environment ID: e-vnnpcfxsww still exists. It is grey and in "Health status: Suspended".
Sorry about the confusion. I am able to see your environment now.
It is hard to tell from the logs, but my guess is that the ASG group originally associated with your environment no longer exists or there is an extraneous target group associated with your environment. This is causing Beanstalk confusion, so it retries the termination process several times.
You can get around this problem as described here: https://forums.aws.amazon.com/thread.jspa?threadID=300949#jive-message-895822
Please let me know if that doesn't work.
Edited by: Rahul-AWS on Apr 9, 2019 7:40 PM
It looks like it worked. It's still visible but it is in the "Terminated" state now.
Elastic Beanstalk stuck aborting current environment operationasked 6 months ago
Environment stuck - Can't terminate - Please helpasked 9 months ago
Elastic Beanstalk Environment is stuck on Terminating for 2 hours nowasked 2 years ago
I have a runn p2.xlarge instance that I wish to permanently terminateasked 3 years ago
Cannot terminate environment?asked 2 years ago
Error when accessing Elastic Beanstalk environment Configurationasked 10 months ago
Multiple applications on same environment of Elastic Beanstalkasked 25 days ago
Elastic Beanstalk environment does not terminateasked 3 years ago
Cannot terminate stale beanstalk environment with No Data stateasked 2 years ago
Elastic Beanstalk not terminating environment from pipelineasked 8 months ago