2 個答案
- 最新
- 最多得票
- 最多評論
0
Hello.
Will it be successful if I force a detach from the AWS CLI instead of from the management console?
If the detach is successful with the command below, try deleting EBS.
https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/detach-volume.html
aws ec2 detach-volume --volume-id "EBS-ID" --force
AWS CLI can be executed from CloudShell.
https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html#how-to-get-started
0
Thanks Riku, I'll raise a ticket under account and billing. I was going to raise a ticket initially, but it said my account was unable to open a case, but you're right I can open one under billing. I'll try that thanks.
已回答 2 個月前
相關內容
AWS 官方已更新 1 年前- AWS 官方已更新 1 年前
Hi Riku, thanks for the suggestion, but trying that results in:
Please check the answers to the questions at the URL below. It appears that the delete and detach commands cannot be used if the EBS status is not 'available'. https://repost.aws/questions/QUGwkiBP0XQXGya8gHNsNB7Q/cannot-detach-volumes
The responding AWS support engineer recommends opening a case with AWS Support under "Account and billing". Inquiries via "Account and billing" can be made free of charge, so I think it's a good idea to try it out. https://docs.aws.amazon.com/awssupport/latest/user/case-management.html
According to the answers to the questions below, it seems that contacting AWS Support may resolve the issue. https://repost.aws/questions/QUytot5r5AR56BbuEFAw0hBQ/ec2-ebs-volume-shows-no-attachments-but-still-in-use-won-t-detach-or-force-detach#ANbhrISi3yTjm2HiekICZ90g