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

• Related Articles

• Cross account recovery of encrypted volumes may fail

  A cross account recovery of an encrypted snapshot may fail with this error: Encrypted snapshots can only create volumes in the owner's account Please upgrade to latest 2.X.X version to resolve the issue. Reference defect number - 6676511295, fixed in ...

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

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

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

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

  Problem: DR recovery may fail with the error “Given key ID is not accessible” The following messages may be printed in the CPM Server log: INFO:  recover_volumes_helper(additional_views.py:515)  from account: accountA, to account: accountB ... ...