The AMI tools libraries install under /usr/lib/site_ruby. Ruby should pick up this path automatically, but if you see a load error when running one of the AMI utilities, it may be because Ruby isn't looking there. To fix this, add /usr/lib/site_ruby to Ruby's library path, which is set in the RUBYLIB environment variable.

The manual describing the operation of each utility can be displayed by invoking it with the --manual parameter. For example:

# ec2-bundle-image --manual 

Invoking a utility with the --help parameter displays a summary and list of command line parameters. For example:

# ec2-bundle-image --help 

Once a machine image has been created it must be bundled as an AMI for use with Amazon EC2, as follows. Use ec2-bundle-image to bundle an image that you have prepared in a loopback file, as described in the previous section.

# ec2-bundle-image -i my-image.img -k pk-HKZYKTAIG2ECMXYIBH3HXV4ZBZQ55CLO.pem -c cert-HKZYKTAIG2ECMXYIBH3HXV4ZBZQ55CLO.pem -u 12345678  

This will create the bundle files:

image.part.00
image.part.01
...
image.part.NN
image.manifest.xml

Alternatively an AMI could be created by snapshotting the local machine root file system and bundling it all at once by using ec2-bundle-vol. (note: you will need to have root privileges to do this and SELinux must be disabled). Use ec2-bundle-vol to re-bundle a (modified) running instance of an existing AMI, as described in the previous section.

# ec2-bundle-vol -k pk-HKZYKTAIG2ECMXYIBH3HXV4ZBZQ55CLO.pem -c cert-HKZYKTAIG2ECMXYIBH3HXV4ZBZQ55CLO.pem -s 1000 -u 495219933132 

As with ec2-bundle-image, ec2-bundle-vol will create image parts files and a manifest file.

	Note
	If selinux is enabled when ec2-bundle-vol is run, the filesystem creation step may fail. Selinux should be disabled while this is done.