blimpy
blimpy copied to clipboard
'blimpy destroy' should detach the instances' EBS volumes
Turns out AWS is keeping EBS volumes floating around for a lot longer than I had anticipated, only noticed when I checked my bill.
Better remove those suckers!
It looks like the EBS volumes that I had attached were from poorly destroyed or potentially manually destroyed EC2 instances. I'm wondering if things work correctly, except in these error conditions.
Perhaps a blimpy status command should query EC2 and see what else is going on there?