DR snapshots may get encrypted with default encryption key on target region instead of custom key

• Related Articles

• 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 DR may fail with the "Encrypted snapshots with EBS default key cannot be shared (OperationNotPermitted)" error

  DR may fail with the "Encrypted snapshots with EBS default key cannot be shared (OperationNotPermitted)" error: Error - Volume DR copy snapshot failed for region Asia Pacific (Sydney), snapshot snap-0123456789abcdef (to DR account). Reason: Failed ...

• Cross-Region DR RDS backup may fail with "Copy failed due to an AWS limitation regarding default encryption key” error

  RDS DR backup of encrypted snapshots between different regions may fail with the following error in the Backup log: Error - RDS DR, copy snapshot failed (to DR account) due to an AWS limitation regarding default encryption key (source US East (Ohio), ...

• CPM supports custom encryption keys for DR

  To support the usage of a custom encryption key for DR, you will need to perform the following: In the account where the custom key resides: Go to KMS and browse to the key you wish to share. Go to the "Other AWS accounts" at the bottom of the page ...

• 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 ...