ec2-mount-volume prepares EBS volumes, exposed as NVMe block devices, for immediate use. It mounts each volume at the location specified in a resource tag.
It provides tag-based mapping to work around unpredictable device names. For example, an instance that mounts at boot a root volume and one data volume may encounter device names "/dev/nvme0n1" and "/dev/nvme1n1" after one boot, but reversed names after the next.
It was made after encountering this issue while migrating from an M4 to M5 instance type.
To install:
go get -v github.com/codeactual/ec2-mount-volume/cmd/ec2-mount-volume
Usage:
ec2-mount-volume --helpDisplay the mount plan for 2 expected EBS volumes (dry run):
ec2-mount-volume --device-num 2Mount 2 expected EBS volumes:
ec2-mount-volume --device-num 2 --forceSame as above but read mount points from EBS volume tags named "mount-point" instead of the default:
ec2-mount-volume --device-num 2 --force --tag mount-pointSame as above but wait 30 seconds instead of the default:
ec2-mount-volume --device-num 2 --force --tag mount-point --timeout 30The program requires access to the EC2's metadata service and the EC2 instance role requires ec2:DescribeVolumes access.
Mozilla Public License Version 2.0 (About, FAQ)
- Please feel free to submit issues, PRs, questions, and feedback.
- Although this repository consists of snapshots extracted from a private monorepo using transplant, PRs are welcome. Standard GitHub workflows are still used.