I want to create a backup or launch multiple copies of my Amazon Elastic Compute Cloud (Amazon EC2) instance, or I received a maintenance notification suggesting that I create an Amazon Machine Image (AMI) of my instance.
Amazon Machine Images (AMIs) are archival copies of instances that you can use to launch other instances. You can use custom AMIs to launch multiple copies of an Amazon EC2 instance that is backed by an Amazon Elastic Block Store (Amazon EBS). You can also use a custom AMI as a backup solution.
By default, when you create an AMI from an instance, snapshots are made of each EBS volume attached to the instance. AMIs can launch with multiple EBS volumes attached. This allows you to replicate both an instance's configuration and the state of all the EBS volumes that are attached to that instance.
Note: Instances created from AMIs don't retain or copy any data stored in instance store volumes. The source instance that you create the AMI from retains all data that's stored in the instance store.
To create an AMI
Note: To maintain data consistency, your instance reboots during the AMI creation process. During the reboot, the public IP address and instance store volumes for your instance remain the same. You can choose the NoReboot option when creating an AMI to prevent the EC2 instance from rebooting. This option can affect the filesystem integrity of the AMI.
(Linux) Amazon Machine Images (AMIs)
(Windows) Amazon Machine Images (AMI)
How can I restrict access to launch Amazon EC2 instances from only tagged AMIs?
Controlling access during AWS requests