How do EBS snapshots work?
EBS snapshots are point-in-time backups of EBS volumes stored durably in Amazon S3. The first snapshot is a full copy, and subsequent snapshots are incremental — only the blocks that changed since the last snapshot are saved. Snapshots can be used to restore volumes, copy data across regions, or create AMIs.
An EBS snapshot captures the exact state of an EBS volume at a specific moment in time. Snapshots are stored in Amazon S3 (managed by AWS, not visible in your S3 console) and are highly durable (99.999999999% — 11 nines). Despite being incremental, each snapshot is a complete and independent restore point — you can always create a new volume from any snapshot without needing the previous ones.
- 1
Snapshot 1 (Full) — The first snapshot copies ALL blocks of the volume to S3. This takes the most time and storage.
- 2
Snapshot 2 (Incremental) — Only the blocks that changed since Snapshot 1 are saved. Unchanged blocks are referenced from Snapshot 1.
- 3
Snapshot 3 (Incremental) — Only the blocks that changed since Snapshot 2 are saved.
- 4
Restoration — When restoring from Snapshot 3, AWS assembles the full volume by combining data from all referenced snapshots automatically. No manual chain management needed.
- 5
Deletion — Deleting an intermediate snapshot does NOT cause data loss. AWS automatically moves referenced blocks to adjacent snapshots.
- 1
Cross-AZ restore — create a new EBS volume from a snapshot in ANY Availability Zone within the same region
- 2
Cross-region copy — copy snapshots to other AWS regions for disaster recovery
- 3
Cross-account sharing — share snapshots with specific AWS accounts or make them public
- 4
AMI creation — create a new Amazon Machine Image from a snapshot of a root volume
- 5
Encryption inheritance — if you create a volume from an encrypted snapshot, the new volume is automatically encrypted
- 6
Data Lifecycle Manager (DLM) — automate snapshot creation, retention, and deletion using policies
- 1
Take snapshots of idle or quiesced volumes for consistency — for databases, flush and freeze I/O before snapshotting
- 2
Use AWS Data Lifecycle Manager (DLM) to automate daily/weekly snapshots and automatic cleanup
- 3
Copy critical snapshots to a different region for disaster recovery
- 4
Tag snapshots with meaningful metadata: environment, application, date, owner
- 5
Monitor snapshot costs — incremental snapshots are cost-effective, but frequent full-change workloads can accumulate costs
- 6
Use Snapshot Archive for long-term retention at 75% lower cost (with a retrieval time of 24–72 hours)
Scenario Questions
0-2 years experience
- 1How would you create a snapshot of an EBS volume attached to an EC2 instance using the AWS console?
- 2What happens to the data on the volume while a snapshot is being taken?
- 3If you delete an EBS volume after taking a snapshot, can you still recover the data? Explain.
2-5 years experience
- 1Your nightly backup job that creates EBS snapshots is failing intermittently. How would you troubleshoot the issue?
- 2Explain the trade‑offs between taking a snapshot while the volume is in use versus stopping the instance first.
- 3You notice snapshot storage costs are higher than expected; what factors could be causing this and how would you reduce cost?
5-8 years experience
- 1Design a backup strategy for a fleet of production EC2 instances that need point‑in‑time recovery within 15 minutes, considering snapshot consistency, cross‑region replication, and cost.
- 2How would you restore a large (10 TB) volume from an incremental snapshot chain to minimize downtime?
- 3Discuss the impact of snapshot frequency on I/O performance and how you would mitigate any degradation.
8+ years experience
- 1Your organization wants to migrate from on‑premises storage to AWS using EBS snapshots as the primary migration mechanism. What architectural considerations, automation, and governance would you put in place?
- 2How would you evaluate and evolve a multi‑account snapshot lifecycle policy to meet compliance, cost, and disaster‑recovery requirements across the enterprise?
- 3Explain how you would design a cross‑region, immutable backup solution using EBS snapshots, CloudWatch events, and IAM policies to satisfy a zero‑RPO, zero‑RTO objective.
Follow-up Questions
- What mechanisms does AWS use to ensure snapshot consistency?
- How does the incremental nature of snapshots affect storage cost?
- Can you restore a snapshot to a different instance type, and what considerations arise?