Encrypted Snapshot Recovery from DR account may fail with the “Given key ID is not accessible” error

• Related Articles

• Encrypted Snapshot may fail DR with the “Given key ID is not accessible” error

  Problem: DR copy may fail with errors like “Given key ID is not accessible” The following error may be printed in the CPM Backup log and the CPM Server log: Error - Volume DR copy snapshot failed for region US East (Ohio) (in DR account), ...

• Cross-region DR copy of encrypted snapshot may fail with "Copy failed due to an AWS limitation regarding default encryption key” error

  DR of encrypted snapshots may fail with the following error in the Backup log: Error - <DR Policy>, copy snapshot failed (in Backup account) due to an AWS limitation regarding default encryption key source <source region>, target <target region>, ...

• Cross account Recovery of an encrypted snapshot with shared custom encryption key may fail

  Cross account recovery of an encrypted snapshot which is encrypted with a shared custom encryption key may fail when trying to recover a resource either from DR to backup account or from backup to DR account (same account recovery works). CPM server ...

• Recovery of an encrypted volume may fail: "Not authorized to use key"

  Performing a cross account recovery of an encrypted volume, or of an instance containing an encrypted volume may not work if the target account cannot access the encryption key from the source account. Error may appear in the CPM Server log as below: ...

• DR of an encrypted snapshot may fail with the “Not Authorized to use key” error

  Problem: DR copy may fail with errors like “Not authorized to perform” or “not authorized to use key” Example in CPM backup log: 10-24-18 10:11:04 - Error - Volume DR copy snapshot failed for region US East (N. Virginia), snapshot ...