Ec2 Instance Without Any Attached Volume?
Solution 1:
You can't have an instance without a root volume. So there will always be at least one volume listed in the block device mapping.
I'm wrong about that. It has been so long since I launched an instance store backed AMI that I kind of forgot they even existed. An instance store backed AMI does not describe its root volume in the block device mapping so if you have such an instance and have no EBS volumes attached the block device mapping would be empty.
For an EBS-based instance the block device mapping will always contain the root volume (at least) even for stopped instances UNLESS you have explicitly detached that volume from the instance.
Solution 2:
It's absolutely possible, at least if the instance isn't currently running.
Consider the common tactic used to rescue yourself from an instance that won't boot:
Stop instance.
Detach root volume, so you can attach it to a working instance and repair the problem.
Right about here, you should have an instance with no volumes, if the root EBS volume were the only volume that instance had.
Other speculations:
I can't confirm, but it's conceivable that instance-store instances, which use an ephemeral disk might also match this.
It seems possible that you could forcibly detach the root EBS volume from a running instance, leaving it in a volume-less state, thought it would crash pretty promptly.
Instances might also end up in this state, briefly, after termination, as their EBS volumes are detached and potentially deleted. (Terminated instances still seem to appear as instances for a short time after you terminate them).
Post a Comment for "Ec2 Instance Without Any Attached Volume?"