Topic lessonTopic: EC2: launch and operation
AMI vs EBS snapshot: what each preserves and how recovery differs
An AMI is an image for launching EC2; an EBS snapshot preserves a volume’s data at a point in time. An EBS-backed AMI combines launch information with references to EBS snapshots. Choose by the required recovery outcome, rather than asking which is universally the better backup.
Distinguish the preservation scope and recovery requirements for launching an instance versus restoring volume data.
Know EC2, EBS, Regions and AZs. The lesson focuses on EBS-backed Linux in a regular AWS Region; it does not create, restore or delete real resources.
Separate launch information from volume data
| Dimension | EBS-backed AMI | EBS snapshot |
|---|---|---|
| Primary role | An image used to launch EC2 | Point-in-time volume data |
| Information | Boot information and block device mappings | Stored volume-block data |
| Relationship to EBS | References root and applicable data snapshots | A source for creating a new EBS volume |
| Do not assume it includes | The complete VPC, SG, IAM or external database setup | RAM, unwritten cache or data outside the volume |
- AMI → SnapshotsThe AMI references preserved data; these are separate resources.
- AMI → New EC2Launch a new instance from the AMI.
- Snapshots → New EBSCreate a new volume with the preserved point-in-time data.
- New EC2 → New EBSAttach storage according to the AMI’s block device mappings.
- AMI
- Holds launch information and volume mappings.
- Snapshots
- Preserve stored data for root/applicable volumes.
- New EC2
- Review compatibility, placement, networking and access.
- New EBS
- A volume created from snapshot data.
Choose the recovery outcome: launch a server or retrieve data
| Desired outcome | Artifact and approach | Additional checks |
|---|---|---|
| Launch EC2 from a preserved OS/configuration | Launch a new instance from a suitable EBS-backed AMI | Compatibility, Region, SGs, permissions and post-launch behavior |
| Retrieve earlier files from a data volume | Create and attach a new volume from its snapshot | Same AZ as the instance, filesystem, mounts and permissions |
| Only a root-volume snapshot remains | Assess registering a suitable AMI or an approved root-recovery procedure | Architecture, boot mode and OS/licensing metadata |
| Restore an entire system after an incident | Inventory whether AMIs/snapshots cover the required system | External DBs, S3, configuration, keys, networking and application consistency |
Creating an EBS volume from a snapshot does not itself launch EC2. To read its data, create the volume in the receiving instance’s AZ and handle attachment and the filesystem correctly. A root snapshot can support AMI registration when the required boot and OS information is available.
Choose an option to see the result and explanation.
A completed capture is not proof of consistent recovery
An EBS snapshot includes data written to the volume at request time, not data held only in application or OS caches. AWS recommends coordinating writes and, for a root-volume snapshot, stopping the instance first. Select a method that accounts for the application and interruption impact.
| Setting | Meaning to review | Avoid this inference |
|---|---|---|
| Normal reboot enabled | A reboot coordinates written state; plan the service interruption | Application recovery is therefore guaranteed |
| NoReboot=true | No reboot; snapshots are crash-consistent for written volume data | Memory contents and unwritten data are also preserved |
Worked example: do not assume yesterday’s data matches today’s app
| Artifact | Established fact | Still unknown |
|---|---|---|
| Yesterday’s data snapshot | A volume can be created from preserved blocks | Whether today’s app accepts that data format |
| Yesterday’s AMI | A launch image exists for a new instance | Compatibility with today’s external DB and permissions |
| Snapshot status is completed | The capture operation completed | Successful file reads or business-process recovery |
Choose an option to see the result and explanation.
Before recovery, check placement, encryption and artifact state
- Record the required recovery point, target volumes and snapshots referenced by the AMI.
- Check snapshot completion and availability in the target Region.
- Create EBS in the receiving EC2 instance’s AZ; distinguish source and recovery target.
- For encrypted data, check availability of the required KMS key and permissions.
- Validate files, configuration and application consistency in a separate recovery target; record established outcomes and unknowns.
An encrypted snapshot preserves encryption requirements during restoration. Access to the required KMS (Key Management Service) key is part of the prerequisites. Seeing an artifact in a list does not establish that you can use its data.
Cleanup: review AMI and snapshot dependencies
Deregistering an AMI does not terminate instances already launched from it. Associated snapshots can be selected for deletion during deregistration or handled separately. A snapshot referenced by other AMIs is not deleted by that option. Review retained artifacts and their costs.
Check, then explain in your own words
- Separate launch information from preserved volume blocks.
- Identify the recovery outcome and placement, encryption and consistency conditions.
- Verify capture, recovery testing and cleanup separately.
Check your understanding: Does an AMI restore the complete system, including VPCs and external databases?
No. Reconcile what the AMI preserves with separately managed configuration and data.
Launching a new EC2 instance is different from restoring a working service. Check all required data, configuration, networking and access.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsAMI launch/boot information, block device mapping and Region/OS/architecture/root type specificity; not a complete infrastructure snapshot.
Used in this lessonSeparate launch information from volume data
- Create an Amazon EBS-backed AMIChecked:
Scope and conditionsAMI references root/applicable EBS snapshots and launches new volumes; root-snapshot registration requires suitable boot/OS/licensing information.
Used in this lessonSeparate launch information from volume data Choose the recovery outcome: launch a server or retrieve data
- CreateImage API referenceChecked:
Scope and conditionsNoReboot=false default versus crash-consistent written-volume snapshots with true. No application recovery guarantee.
Used in this lessonA completed capture is not proof of consistent recovery
- Create Amazon EBS snapshotsChecked:
Scope and conditionsWritten data at request time, exclusion of caches, asynchronous completion and coordinated writes/root-volume stopping considerations.
Used in this lessonSeparate launch information from volume data A completed capture is not proof of consistent recovery
Scope and conditionsCreate a new volume in the receiving instance AZ; attachment and filesystem/mount steps are separate. No live restoration performed.
Used in this lessonChoose the recovery outcome: launch a server or retrieve data
- Amazon EBS encryptionChecked:
Scope and conditionsKMS-backed encryption of snapshots and restored volumes; visibility alone does not demonstrate decrypt/use authorization.
Used in this lessonBefore recovery, check placement, encryption and artifact state
- Deregister an Amazon EC2 AMIChecked:
Scope and conditionsDeregistration does not terminate launched instances; associated-snapshot deletion is optional and shared AMI references prevent that deletion.
Used in this lessonCleanup: review AMI and snapshot dependencies
- Amazon EBS pricingChecked:
Scope and conditionsProvisioned capacity, additional performance and snapshots; no unit rate or price quote is embedded.
Used in this lessonCleanup: review AMI and snapshot dependencies
Scope and conditionsRequired KMS permissions/key-policy and instance-side grants for encrypted AMIs/volumes/snapshots. No permission changes or secret retrieval performed.
Used in this lessonLesson overview and review