EBS DR Gap / Durability Risk Diagnostic Troubleshooter (Part 2)
Use the interactive troubleshooter below to identify your EBS 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 |
|---|---|---|---|---|
| 5 | EBS Volume Restore / Create Failure | "event": "createVolume", "result": "failed", "cause": "arn:aws:kms:sa-east-1:0123456789ab:key/... is disabled." | The action to create or restore a volume fails because the required AWS KMS encryption key is disabled or pending import. | N/A |
| 6 | Fast Snapshot Restore Enablement Failure | "message": "Server.InsufficientCapacity - There was insufficient capacity available to satisfy the request" | A request to enable fast snapshot restore fails and transitions to a disabled state due to insufficient server capacity or an internal error. | N/A |
| 7 | Attach Volume Failure on Recovery | "event": "attachVolume", "result": "failed", "cause": "arn:aws:kms:us-east-1:... is pending deletion." | The EBS volume fails to attach or reattach to an instance because the associated KMS key is pending deletion or invalid. | N/A |