There are two types of AMI / instances: EBS loading and instance storage (sometimes called the S3 base). You are probably using EBS loading, so this answer will be of this type.
EBS Boot AMI is an EBS snapshot of an EBS boot EBS volume with some additional attributes, including:
- Registered as AMI with the identifier AMI
- AKI (core)
- ARI (ramdisk) Architecture
- (e.g. 64-bit)
- device block mapping (for example, when volumes should be created / attached)
- description, name
- (who is allowed to run AMI)
If you create an AMI of a working instance, you can start new instances in the same state. Make sure you test this process so that you know that it works.
If you simply remove the EBS volume of your executable instance, you can create volumes from these snapshots to access configuration and data.
You can also take an EBS snapshot of the EBS boot volume and register it as AMI boot AMI so that you can run more instances starting from this state. When registering AMI, you will need to specify the correct AKI, architecture, and other metadata for this to work, so research and practice before trusting this approach.
Eric hammond
source share