Snapshot vs AMI vs AWS Backup
An EBS snapshot is a volume-level backup. An AMI is a launch template for instances (which internally uses snapshots). AWS Backup is a centralized backup management service spanning multiple AWS services.
| Aspect | EBSスナップショット | AMI | AWS Backup |
|---|---|---|---|
| Scope | Point-in-time copy of an EBS volume | Launch template including OS/config (uses snapshots internally) | Centralized management across EC2/EBS/RDS/DynamoDB/EFS, etc. |
| Main use | Volume restore/duplication, copy to other AZ/region | Duplicating identical instances, copy to other account/region | Org-wide centralized backup policy and compliance |
| Scheduling | Automatable via Data Lifecycle Manager (DLM) | Automatable via DLM or EC2 Image Builder | Backup plans define schedule, retention, and copy destinations centrally |
| Typical use | Periodic volume backups, disaster recovery | Golden image creation, launch templates for Auto Scaling | Applying unified backup/retention policy across services |
How to Choose
Use snapshots for periodic single-volume backups. Use an AMI when you need a template to repeatedly launch identically configured instances (e.g., with Auto Scaling). Use AWS Backup to centrally manage and audit backup policy across multiple services — not just EC2, but RDS, DynamoDB, EFS, and more. Since an AMI internally relies on EBS snapshots, the two are layered rather than mutually exclusive.
Exam Points
- SOA frequently tests snapshot automation/lifecycle management via DLM and cross-region DR design
- SAA frequently tests the basic question "what underlies an Auto Scaling launch template?" → AMI
- SAP/DOP cover cross-account, cross-service backup governance via AWS Backup (e.g., Backup Vault Lock)
Related Service Guides
References
Last updated: 2026-09-06
This page is created from AWS official documentation and reviewed/edited by the operator. See our editorial & quality policy for details.