EBS Snapshot Management: Save Up to 75% with Cost Optimization Strategies

Key Takeaway

Core strategies for reducing EBS snapshot costs: Delete unnecessary snapshots, Automate lifecycle with DLM, Use Archive tier for 90+ day retention (up to 75% savings).

---

1. EBS Snapshot Cost Structure

Pricing

Item	Price (Seoul Region)
Standard Snapshot Storage	~$0.05/GB-month
Archive Storage	~$0.0125/GB-month (75% cheaper)
Snapshot Restore (Archive)	$0.03/GB
Cross-Region Copy	$0.01/GB (data transfer)

Understanding Incremental Backups

┌─────────────────────────────────────────────────────────┐
│                   EBS Incremental Snapshots              │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  Volume State:  [███████████] 100GB                     │
│                                                         │
│  Snapshot 1:  [███████████] 100GB stored (full backup)  │
│                    ↓                                    │
│  Changes:     [███▓▓█████] 20GB changed                 │
│                    ↓                                    │
│  Snapshot 2:  [▓▓] 20GB stored (changes only)           │
│                    ↓                                    │
│  Changes:     [███▓▓██▓██] 10GB more changed            │
│                    ↓                                    │
│  Snapshot 3:  [▓] 10GB stored (changes only)            │
│                                                         │
│  Total stored: 100 + 20 + 10 = 130GB (NOT 300GB!)      │
└─────────────────────────────────────────────────────────┘

Snapshot Deletion Considerations

⚠️ Important: Data reference relationships when deleting snapshots

Snapshot 1 (base)  →  Snapshot 2 (incr)  →  Snapshot 3 (incr)
    │                       │                      │
    └───────────────────────┴──────────────────────┘
            Referenced data is preserved

When deleting Snapshot 2:
- Only data unique to Snapshot 2 is deleted
- Data referenced by Snapshots 1, 3 is preserved
- Cost reduction may be less than expected

---

2. Amazon Data Lifecycle Manager (DLM)

Concept

DLM is a service that automates the creation, retention, and deletion of EBS snapshots and AMIs.

DLM Policy Configuration

┌─────────────────────────────────────────────────────────┐
│                   DLM Lifecycle Policy                   │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  Policy Type: EBS Snapshot Policy                       │
│                                                         │
│  Target Resources:                                      │
│  ├── Tag-based: Backup=Daily                           │
│  └── Resource Type: VOLUME or INSTANCE                  │
│                                                         │
│  Schedule:                                              │
│  ├── Frequency: Daily / Weekly / Monthly / Cron        │
│  ├── Start Time: 00:00 UTC                             │
│  └── Retention Count: Keep latest 7                     │
│                                                         │
│  Advanced Options:                                      │
│  ├── Fast Snapshot Restore (FSR)                       │
│  ├── Cross-Region Copy                                 │
│  └── Tag Inheritance                                   │
└─────────────────────────────────────────────────────────┘

DLM CLI Example

# Create DLM policy with AWS CLI
aws dlm create-lifecycle-policy \
  --description "Daily EBS snapshots" \
  --state ENABLED \
  --execution-role-arn arn:aws:iam::123456789012:role/AWSDataLifecycleManagerDefaultRole \
  --policy-details '{
    "PolicyType": "EBS_SNAPSHOT_MANAGEMENT",
    "ResourceTypes": ["VOLUME"],
    "TargetTags": [{"Key": "Backup", "Value": "Daily"}],
    "Schedules": [{
      "Name": "DailySnapshots",
      "CreateRule": {"Interval": 24, "IntervalUnit": "HOURS", "Times": ["09:00"]},
      "RetainRule": {"Count": 7},
      "CopyTags": true
    }]
  }'

DLM Retention Strategies

Strategy	Description	Use Case
Count-based	Keep latest N snapshots	General backup
Age-based	Keep for N days	Compliance
Generational	Daily/weekly/monthly retention	Long-term archive

---

3. Snapshot Archive

Concept

Move snapshots kept for 90+ days that are infrequently accessed to the Archive tier for up to 75% cost savings.

Standard vs Archive Comparison

Attribute	Standard Tier	Archive Tier
Storage Cost	$0.05/GB-month	$0.0125/GB-month
Restore Cost	None	$0.03/GB
Restore Time	Immediate	Up to 72 hours
Minimum Retention	None	90 days

Archive Workflow

┌─────────────────────────────────────────────────────────┐
│               Snapshot Archive Workflow                  │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  1. Create Snapshot                                     │
│     └── Stored in Standard tier                         │
│            │                                            │
│            ▼                                            │
│  2. Will retain 90+ days?                               │
│     ├── Yes → Move to Archive                           │
│     │         └── 75% cost savings                      │
│     │                                                   │
│     └── No → Keep in Standard tier                      │
│              └── Fast restore available                  │
│                                                         │
│  3. When restore needed                                 │
│     └── Restore from Archive to Standard (up to 72hrs)  │
│         └── Restore cost $0.03/GB incurred              │
└─────────────────────────────────────────────────────────┘

Archive Cost Calculation Example

100GB snapshot, 1 year retention:

Standard Tier:
  100GB × $0.05 × 12 months = $60/year

Archive Tier:
  100GB × $0.0125 × 12 months = $15/year

Savings: $60 - $15 = $45/year (75% savings)

---

4. Cost Optimization Strategies

Strategy 1: Identify and Delete Unnecessary Snapshots

# Query snapshots older than 30 days
aws ec2 describe-snapshots \
  --owner-ids self \
  --query 'Snapshots[?StartTime<=`2025-12-27`].{ID:SnapshotId,Size:VolumeSize,Time:StartTime}' \
  --output table

# Find orphaned snapshots (no attached volume)
aws ec2 describe-snapshots \
  --owner-ids self \
  --query 'Snapshots[?!VolumeId].SnapshotId'

Strategy 2: Automate with DLM

Recommended DLM Policy Configuration:

Production Environment:
├── Daily snapshots: Keep 7
├── Weekly snapshots: Keep 4
└── Monthly snapshots: Keep 12 → Then archive

Development Environment:
├── Daily snapshots: Keep 3
└── Weekly snapshots: Keep 2

Strategy 3: Tag-based Cost Tracking

┌─────────────────────────────────────────────────────────┐
│                Tag-based Cost Allocation                 │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  Tag Examples:                                          │
│  ├── Environment: Production / Development / Test       │
│  ├── Project: ProjectA / ProjectB                       │
│  ├── Team: Engineering / Marketing                      │
│  └── CostCenter: CC-001 / CC-002                       │
│                                                         │
│  Usage:                                                 │
│  ├── Analyze costs by tag in Cost Explorer             │
│  ├── Chargeback snapshot costs by dept/project         │
│  └── Identify unnecessary snapshot owners              │
└─────────────────────────────────────────────────────────┘

Strategy 4: Volume Type Optimization

Snapshot costs are proportional to actual data size, so optimize volumes themselves.

Action	Effect
gp2 → gp3 migration	20% cost savings, same performance with smaller volumes
Delete unused volumes	Save both volume + snapshot costs
Right-size volumes	Reduce snapshot size

---

5. Cost Monitoring

Using Cost Explorer

Cost Explorer Settings:

1. Service filter: EC2-Other (includes snapshots)

2. Usage type filter:
   - EBS:SnapshotUsage (Standard snapshots)
   - EBS:SnapshotArchive (Archive snapshots)
   - EBS:SnapShotRestore (Archive restore)

3. Group by tag:
   - Analyze costs by team/project

AWS Budgets Alerts

Budget Example:

Name: EBS-Snapshot-Monthly-Budget
Type: Cost Budget
Amount: $100/month

Alerts:
├── Actual cost > 80% → Warning email
├── Forecasted cost > 100% → Warning email
└── Actual cost > 100% → Urgent alert (SNS)

---

6. Snapshot Management Best Practices

Checklist

✅ Snapshot Management Checklist

□ Configure auto create/delete with DLM policies
□ Establish and apply tag strategy
□ Move 90+ day snapshots to Archive
□ Monthly cleanup of unnecessary snapshots (manual)
□ Monitor monthly costs with Cost Explorer
□ Set up Budgets alerts
□ Review gp2 → gp3 volume migration

Recommended Settings by Environment

Environment	Backup Frequency	Retention	Archive
Production	Daily	30 days + monthly	After 90 days
Staging	Weekly	14 days	Not recommended
Development	Weekly	7 days	Not recommended

---

SAA-C03 Exam Focus Points

Common Question Types

1. Cost Optimization

   • "How to reduce long-term snapshot costs?" → Snapshot Archive
   • "How to automate snapshot lifecycle?" → Amazon DLM

2. Concept Understanding

   • "How are snapshots stored?" → Incremental backup
   • "What happens to data when deleting intermediate snapshot?" → Referenced data preserved

3. Limitations

   • "Minimum retention for archived snapshots?" → 90 days
   • "Archive snapshot restore time?" → Up to 72 hours

---

FAQ

Q1: What's the difference between DLM and AWS Backup?

DLM is a lifecycle management tool specialized for EBS snapshots and AMIs. AWS Backup centrally manages multiple services like EC2, RDS, EFS. Use DLM for EBS-only management; use AWS Backup for multi-service unified management.

Q2: What happens if I delete an archived snapshot after 30 days?

60 days of additional charges are incurred. If you don't meet the 90-day minimum retention, prorated charges apply for the remaining period.

Q3: Why don't costs decrease after deleting snapshots?

EBS snapshots are stored incrementally. If data from the deleted snapshot is referenced by other snapshots, that data isn't deleted and costs continue.

Q4: When should I use Fast Snapshot Restore (FSR)?

Enabling FSR allows volumes to be created from snapshots at immediate full performance. However, hourly per-AZ charges apply, so only use for production workloads requiring fast recovery.

---

Summary

Key points for EBS snapshot cost optimization:

1. Automate with DLM: Minimize manual management
2. Use Archive: 75% savings for 90+ day snapshots
3. Regular cleanup: Delete unnecessary snapshots
4. Monitoring: Cost Explorer + Budgets

On exams, when "snapshot cost reduction" appears, think DLM (automation) and Snapshot Archive (long-term storage).

Related Posts

• EBS Volume Types Complete Comparison
• AWS Backup Complete Guide
• Cost Explorer Guide

References

• Amazon Data Lifecycle Manager
• Archive Amazon EBS Snapshots
• EBS Snapshot Pricing