Starting with an Existing AMI
From Amazon Elastic Compute Cloud: 2009-10-31
To quickly and easily get a new working AMI, start with an existing public AMI or one of your own. You can then modify it and create a new AMI as described in Creating an AMI.
![[Note]](/ec2-ug-2009-10-31/note.png){kind=small}
|
Note |
|---|---|
|
Before selecting an AMI, determine whether the instance types you plan to launch are 32-bit or 64-bit. For more information, see Instance Types Make sure you are using GNU Tar 1.15 or later. |
To use an existing AMI to create a new AMI, complete the following tasks.
First, locate an AMI that contains the packages and services you require. This can be one of your own AMIs or a public AMI provided by Amazon EC2.
|
|
Note |
|---|---|
|
If you are planning on creating an AMI that uses an Amazon EBS volume as its root device, we recommend selecting an existing AMI backed by Amazon EBS and modifying it to meet your needs. For more information, see AMI and Instance Concepts |
This task is only required if you selected one of the public AMIs provided by Amazon EC2. You must create a public/private key pair to ensure that only you have access to instances that you launch.
After you generate a key pair, the public key is stored in Amazon EC2 using the key pair name you selected. Whenever you launch an instance using the key pair name, the public key is copied to the instance metadata. This allows you to access the instance securely using your private key.
To create a public/private key pair
-
Enter the following command:
$ec2-add-keypair<keypair-name>The
<keypair-name>is the name you select for the key pair.The resulting private key is displayed.
-
Open a text editor.
-
Paste the entire private key, starting with the line "
-----BEGIN RSA PRIVATE KEY-----" and ending with the line "-----END RSA PRIVATE KEY-----". -
Save the file and exit.
Note This file should only be readable by the file owner.
You are now ready to launch an instance of the AMI that you previously selected.
![[Important]](/ec2-ug-2009-10-31/important.png){kind=small}
|
Important |
|---|---|
|
Once you launch an instance, you will be billed for all usage, including hourly CPU time. Make sure to stop (Amazon EBS-backed instances only) or terminate any instances that you do not want to leave running. For information on Amazon EC2 pricing, go to the Amazon EC2 home page. |
After starting an instance, you can log in and modify it according to your requirements.
You now have complete control over the instance. You can add, remove, modify, or upgrade
packages and files to suit your needs.
Important
We recommend exercising extreme care when changing some of the basic Amazon EC2
configuration settings, such as the network interface configuration and the
/etc/fstab contents. Otherwise, the AMI might become unbootable or
inaccessible from the network once running.
Your new AMI is encrypted and signed to ensure that only you and Amazon EC2 can access
it. Therefore, you must upload your Amazon EC2 private key and X.509 certificate to the running instance,
for use in the AMI bundling process.
Note
For information on obtaining your Amazon EC2 private key and X.509 certificate, refer to the
Amazon Elastic Compute Cloud Getting Started Guide.
To upload your Amazon EC2 private key and X.509 certificate
-
Copy your Amazon EC2 private key and X.509 certificate to the /mnt directory.
-
Enter the following command:
$
scp <private_keyfile> <certificate_file> root@<dns_location>:/mnt
The <private_keyfile> is the file that contains the private key,
certificate_file is the file that contains the certificate, and
dns_location is the DNS location of the instance within Amazon EC2.
Amazon EC2 returns the name of the files and some performance statistics.
Note
It is important that the key and cert files are uploaded into /mnt to prevent them from being
bundled with the new AMI.