EBS Automated Backup DR Gap / Durability Risk Diagnostic Troubleshooter (Part 1)
Use the interactive troubleshooter below to identify your EBS automated backup DR gap or durability risk symptom, review the raw evidence, understand the root cause, and apply the recommended fix.
🚨 Step 1: What specific error symptom are you experiencing?
Please click the most accurate description:
Quick Reference Table
| # | Scenario | Key Error Signal | Root Cause | The Fix |
|---|---|---|---|---|
| 1 | Automated Backup Failure (DLM Policy Error) | "detail-type": "DLM Policy State Change" "state": "ERROR" "cause": "Role provided does not have sufficient permissions" | The IAM role associated with the Data Lifecycle Manager (DLM) policy lacks the sufficient permissions required to create and manage snapshots on your behalf. | N/A |
| 2 | Automated Backup Failure (Snapshot Quota Exceeded) | "detail-type": "DLM Policy State Change" "state": "ERROR" "cause": "Maximum allowed active snapshot limit exceeded" | The AWS account has reached its maximum allowed active EBS snapshot limit, preventing DLM from successfully executing scheduled backups. | N/A |
| 3 | Cross-Region Snapshot Copy Failure (CRR DR Gap) | --metric-name SnapshotsCopiedRegionFailed | The DLM lifecycle policy failed to create cross-Region snapshot copies even after the 24-hour retry window expired, leaving remote regions without recovery points. | N/A |
| 4 | Snapshot Archiving Failure (Data Durability Risk) | "event": "archiveSnapshot" "result": "failed" "cause": "Source snapshot ID is not valid" | The snapshot archive action failed because the specified source snapshot ID is invalid, threatening long-term data compliance and durability. | N/A |