Instance restore may be marked "successful", despite failing to restore a volume

• Related Articles

• Error "Could not share private image ami-12345678 between accounts" may occur during cross-account instance recovery

  Error "Could not share private image ami-12345678 between accounts" may occur during cross-account instance recovery: Error - Could not share private image ami-12345678 between accounts Error - First step (launching instance) failed. Reason: Could ...

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

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

• File level restore may fail with the "Failed adding share permission" error

  File level restore may fail with the "Failed adding share permission" error: ERROR:  share_snapshot(.\cpmserver\cpm\aws_utils.py:265)  Failed adding share permission to snapshot snap-1234567890abcdef (original volume: vol-abcdef1234567890) Failed. ...

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