Amazon Elastic Compute Cloud Developer Guide Creating an AMI Working with AMIs This section details how to build, store, and share AMIs. Creating an AMI There are several techniques for creating an AMI offering a mix of ease of use and detailed customization levels. The easiest method involves starting from an existing public AMI and modifying it according to your requirements, as described in the section called “Starting with an Existing AMI”. Another approach is to build a fresh installation either on a stand-alone machine or on an empty file system mounted by loopback. This essentially entails building an operating system installation from scratch and is described in the section called “Creating through a Loopback File”. Once the installation package has been built to your satisfaction it needs to be bundled and uploaded to Amazon S3 as described in the section called “Bundling an AMI”. Starting with an Existing AMI This is the quickest and easiest of the methods to get a new working AMI. Start with an existing public AMI or one of your own. You can then modify that as you see fit and subsequently create a new AMI with the ec2-bundle-vol utility, as decribed later in the section called “Bundling an AMI”. Select an AMI The first step is to locate an AMI that contains the packages and services that you require. This can be one of your own AMIs or one of the public AMIs provided by Amazon EC2. Use ec2-describe-images to get a list of available AMIs, as is shown below, then select one of the listed AMIs and note its AMI ID, e.g. ami-5bae4b32: PROMPT> ec2-describe-images IMAGE ami-60a54009 ec2-public-images/base-fc4-apache.manifest.xml 475219833042 available public IMAGE ami-61a54028 <your-s3-bucket>/image.manifest.xml 495219933132 available private IMAGE ami-5bae4b32 ec2-public-images/getting-started.manifest.xml 475219833042 available public IMAGE ami-6ea54007 ec2-public-images/base-fc3-mysql.manifest.xml 475219833042 available public API Version 2007-03-01 3
The new reader is still in beta!