- Le plus récent
- Le plus de votes
- La plupart des commentaires
I found the answer!
I was doing nothing wrong, and Amazon had a bug. I was able to get someone at Amazon tech support to kick the thing for me and unstick it. Because I don't pay for support, I filed an issue with "billing" as I was being billed for a volime that couldn't be deleted.
EC2 "volumes" really do get stuck and can't be force-detached and the only option is to get technical support from Amazon.
Are you able to get more details about the volume using AWS Config? A query something like the below and then looking at the configuration to see if it gives you any additional data?
SELECT
resourceId, resourceName, resourceType, tags, configuration
WHERE
resourceType = 'AWS::EC2::Volume'
and resourceId = 'vol-cd8365a4'
Just a thought, is your account's "home" region in your config/env settings the same region as the volume is in (us-east-1)? If it isn't then maybe append --region us-east-1
to the command.
If you think this is superfluous then I agree, as Resource IDs should be globally unique. But it's surely worth a try.
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- Réponse acceptéedemandé il y a 7 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
Thanks for the idea. It didn't give me any more information. Shows as "in-use" with no attachements