aws ec2 import-image doesn't honour the DeviceName in the disk-container file about aws-cli HOT 3 CLOSED

Thanks for reaching out. The import-image command involves a call to the EC2 ImportImage API. Therefore this behavior is happening on the API side rather than directly via the CLI.

This appears to be expected behavior based on this documentation: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/device_naming.html

(Linux instances) Depending on the block device driver of the kernel, the device could be attached with a different name than you specified. For example, if you specify a device name of /dev/sdh, your device could be renamed /dev/xvdh or /dev/hdh. In most cases, the trailing letter remains the same. In some versions of Red Hat Enterprise Linux (and its variants, such as CentOS), the trailing letter could change (/dev/sda could become /dev/xvde). In these cases, the trailing letter of each device name is incremented the same number of times. For example, if /dev/sdb is renamed /dev/xvdf, then /dev/sdc is renamed /dev/xvdg. Amazon Linux creates a symbolic link for the name you specified to the renamed device. Other operating systems could behave differently.

This could maybe be clearer in the documentation — I recommend using the Provide feedback link at the bottom of the API documentation page if you want to share any specific feedback on this, and any documentation updates would automatically get reflected in the CLI command docs.

from aws-cli.

Thank you @tim-finnigan your answer makes sense and I will modify my bootstrap scripts as needed

from aws-cli.

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

from aws-cli.