AWS Storage Services: Mastering EBS Snapshots
In the AWS ecosystem, Elastic Block Store (EBS) Snapshots are a fundamental building block for data durability and disaster recovery. For the SAA-C03 exam, understanding how snapshots behave, how they are billed, and how to optimize their performance is critical.
The “Whiteboard” Analogy
Imagine you are drawing a complex architectural diagram on a whiteboard. Instead of redrawing the entire diagram every hour, you take a photo with your phone. The first photo captures everything (Full Backup). The next photo only captures the new lines you added or the parts you erased (Incremental). If the whiteboard is accidentally wiped, you can use those photos to perfectly recreate the diagram at any specific point in time.
Core Concepts & Architecture
EBS Snapshots are point-in-time, incremental backups of your EBS volumes. While EBS volumes exist within a specific Availability Zone (AZ), snapshots are stored in Amazon S3, providing 99.999999999% (11 nines) of durability. Note: You cannot access the S3 buckets directly; they are managed by AWS.
- Incremental Nature: Only the blocks that have changed since the last snapshot are saved. This minimizes the time required to create snapshots and saves on storage costs.
- Crash Consistency: Snapshots are crash-consistent by default. To ensure application consistency (flushing caches to disk), it is recommended to pause write operations or unmount the volume before snapshotting.
- Region Scope: Snapshots are constrained to the Region where they were created. To move a snapshot to another region, you must explicitly Copy it.
Comparison: Snapshot Tiers & Features
| Feature | Standard Tier | Archive Tier | Fast Snapshot Restore (FSR) |
|---|---|---|---|
| Use Case | Frequent backups/recovery | Long-term (90+ days) retention | Eliminating “latency” on volume creation |
| Cost | Standard storage rates | Lowest cost (up to 75% cheaper) | High (billed per AZ/Hour) |
| Retrieval | Immediate | Minutes to Hours (24-72h) | Instant (Pre-warmed) |
Data Lifecycle & Automation
Managing snapshots manually is prone to error. AWS provides two primary ways to automate this:
- Amazon Data Lifecycle Manager (DLM): A policy-based tool specifically for automating the creation, retention, and deletion of EBS snapshots and EBS-backed AMIs.
- AWS Backup: A centralized backup service that manages EBS snapshots along with other services like RDS, EFS, and DynamoDB.
Exam Tips and Gotchas
- The S3 Secret: Snapshots are stored in S3, but they are NOT visible in your S3 buckets. If an exam question asks where snapshots reside: it’s S3.
- Deletion Logic: Deleting a snapshot only removes the data unique to that snapshot. If data is still needed by a subsequent incremental snapshot, it is preserved.
- Encryption is Persistent: If a volume is encrypted, the resulting snapshot is encrypted. If you copy an unencrypted snapshot, you can encrypt it during the copy process.
- Multi-Account Sharing: You can share snapshots with other AWS accounts. However, you cannot share a snapshot that is encrypted with the default AWS Managed Key (KMS). You must use a Customer Managed Key (CMK) and share that key too.
Decision Matrix / If–Then Guide
- IF you need to move an EBS volume to a different AZ… THEN take a snapshot and restore it as a new volume in the target AZ.
- IF you need to reduce costs for backups kept for 6 months… THEN use EBS Snapshot Archive.
- IF your application requires maximum performance immediately upon volume creation… THEN enable Fast Snapshot Restore (FSR).
- IF you need to share an encrypted volume across accounts… THEN copy the snapshot using a custom KMS key and share the key.
Topics covered:
Summary of key subtopics covered in this guide:
- Incremental vs. Full backup logic.
- Storage location (S3) and durability.
- EBS Snapshot Archive vs. Standard Tier.
- Automation via DLM and AWS Backup.
- Encryption and Cross-Account sharing constraints.
- Fast Snapshot Restore (FSR) for low-latency initialization.
EBS Snapshot Architecture Visualized
KMS: Manages encryption keys. Encryption is “baked in” from volume to snapshot.
CloudWatch: Monitor snapshot completion events via EventBridge.
IAM: Control who can create, delete, or share snapshots.
FSR: Use this for VDI or Auto Scaling groups where “warming up” a volume from S3 is too slow.
AMI Creation: Snapshots are the foundation of Amazon Machine Images (AMIs).
Incremental: You only pay for the blocks that changed.
Archive Tier: Perfect for regulatory data that you rarely access but must keep for years.