Will the AMI have the additional instance store volume data?

A user has launched an EC2 instance from an instance store backed AMI. The user has attached
an additional instance store volume to the instance. The user wants to create an AMI from the
running instance. Will the AMI have the additional instance store volume data?

A.
Yes, the block device mapping will have information about the additional instance store volume

B.
No, since the instance store backed AMI can have only the root volume bundled

C.
It is not possible to attach an additional instance store volume to the existing instance store
backed
AMI instance

D.
No, since this is ephermal storage it will not be a part of the AMI

Explanation:
When the user has launched an EC2 instance from an instance store backed AMI and added an
instance store volume to the instance in addition to the root device volume, the block device
mapping for the new AMI contains the information for these volumes as well. In addition, the block
device mappings for the instances those are launched from the new AMI will automatically contain
information for these volumes.

Show Hint

← Previous question

Next question →

Bala

Correct Answer : A

Exp : When the user has launched an EC2 instance from an instance store backed AMI and added an instance store volume to the instance in addition to the root device volume, the block device mapping for the new AMI contains the information for these volumes as well. In addition, the block device mappings for the instances those are launched from the new AMI will automatically contain information for these volumes.

Block Device Mapping

Each Amazon EC2 instance that you launch has an associated root device volume, either an Amazon Elastic Block Store (Amazon EBS) volume or an instance store volume. You can use block device mapping to specify additional Amazon EBS volumes or instance store volumes to attach to an instance when it’s launched. You can also attach additional Amazon EBS volumes to a running instance; see Attaching an Amazon EBS Volume to an Instance. However, the only way to attach instance store volumes to an instance is to use block device mapping to attach them as the instance is launched. For more information about root device volumes, see Changing the Root Device Volume to Persist.

A block device is a storage device that moves data in sequences of bytes or bits (blocks). These devices support random access and generally use buffered I/O. Examples include hard disks, CD-ROM drives, and flash drives. A block device can be physically attached to a computer or accessed remotely as if it were physically attached to the computer. Amazon EC2 supports two types of block devices:

Instance store volumes (virtual devices whose underlying hardware is physically attached to the host computer for the instance)

Amazon EBS volumes (remote storage devices)

A block device mapping defines the block devices to be attached to an Amazon EC2 instance and the device name to use. You can specify a block device mapping as part of creating an AMI so that the mapping is used by all instances launched from the AMI. Alternatively, you can specify a block device mapping when you launch an instance, so this mapping overrides the one specified in the AMI from which you launched the instance.

There are two types of virtualization available in Amazon EC2: paravirtual (PV) and hardware virtual machine (HVM). The virtualization type is determined by the AMI used to launch the instance; some instance types support both PV and HVM while others support only one or the other. Be sure to note the virtualization type used by your AMI when you are creating your block device mapping because the recommended and available device names that you can use are different based on the virtualization type of your instance. For more information, see Virtualization Types.