vol-new = New, unencrypted, blank volume, identical in size to vol-cmk, and in the same Availability Zone as vol-cmk.&nbsp; This will be used to receive the data from vol-cmk, and then to create an unencrypted snapshot that is shareable with another account.

9. As sudoer/root, dd the data from the encrypted original volume v-cmk (input file is /dev/xvdf) to the unencrypted new volume v-new (output file is /dev/xvdg):

# dd if=/dev/xvdf of=/dev/xvdg bs=4096

Notes regarding dd:

If you don't specify a block size (bs=4096 or whatever you choose), block size defaults to 512 bytes and the transfer speed will be negatively impacted. Larger block size does introduce an increased chance for error, but it provides significantly faster transfer speed up to a point.

dd clones everything, including the MBR, bootloader, partitions, UUIDs, and data. Therefore, you do not need to partition the destination EBS volume before performing the data copy from the encrypted volume to the unencrypted volume.

10. Wait for the process to complete. Larger volumes take longer than smaller volumes, slower instances take longer than faster instances.

11. Detach /dev/xvdg (vol-new) from temporary copy instance i-temp and attach it to the original instance i-cmk using the identical root device name noted in step 3.

12. Connect to the original instance i-cmk to confirm the new instance launches properly with the new unencrypted (copied) root volume.

13. Select i-cmk in the EC2-console, and view the volume’s properties to ensure the root volume is now unencrypted. You might need to run the partprobe command as root/sudoer on the instance to register the partition changes to the kernel (a reboot or a stop/start will accomplish the task as well).

14. Repeat the process for any other encrypted volumes on instance i-cmk to create "cloned" volumes that are unencrypted.