- 最新
- 最多得票
- 最多評論
Hello andyolivares,
I am sorry to hear about the issues.
Can you please try to detach the volumes (their state appears as 'in-use') manually using EC2 Console \[1] or using AWS CLI \[2]?
Also, can you please try to detach the ENIs manually using EC2 Console \[3] (using the Network Interfaces page) or using AWS CLI \[4]?
Links:
[1] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-detaching-volume.html
[2] https://docs.aws.amazon.com/cli/latest/reference/ec2/detach-volume.html
[3] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html#detach_eni
[4] https://docs.aws.amazon.com/cli/latest/reference/ec2/detach-network-interface.html
Regards,
awstomas
Forgot to mention that buttons for detach appear grayed out in the AWS console.
Trying from AWS CLI reports an error of resources being "in-use".
So, cannot detach nor delete those resources. They seem to be "in-use" by a ghost EC2 instance.
Hello,
I have checked the 2 volumes and the 2 ENIs and they now show as in "available" state. Are you still experiencing any issues or have the issues been resolved now?
Regards,
awstomas
相關內容
- AWS 官方已更新 2 年前