Instance recovery may fail with the following error: "Recovery Operation Failed. Reason: EBS-optimized instances are not supported for your requested configuration."
Issue:
Instance recovery may fail with an error:
Recovery Operation Failed. Reason: EBS-optimized instances are not supported for your requested configuration. Please check the documentation for supported configurations.
Cause:
This issue may appear if you are running on a not up-to-date version of CPM, that does not support your target instance type.
Solution:
Please upgrade to the latest available version:
Related Articles
Instance recovery may fail with the error "You are not authorized to perform this operation"
Instance recovery may fail with the error "You are not authorized to perform this operation" : ERROR: recover_ebs_based_instance(.\cpmserver\cpm\recovery.py:749) Run_instance failed. Exception: EC2ResponseError: 403 Forbidden <?xml version="1.0" ...Instance recovery may fail with the "Address xxx.xx.xx.xx is in use" error
Issue: When attempting instance recovery, it may fail with the following error in the recovery log: Error - First step (launching instance) failed. Reason: Address xxx.xx.xx.xx is in use. Solution: This usually happens because you are trying to ...Error on Instance recovery - Instance recovery failed: Failed checking snapshot availability
Issue: Error - Instance recovery failed: Failed checking snapshot availability When running a recovery, first CPM downloads the data from the bucket, then it creates a temporary snapshot and then creates the instance. This error occurs when a timeout ...EBS/RDS DR & Recovery with KMS key
When copying cross account an EBS/RDS Volume encrypted with custom KMS, a KMS key should also be available in the other account. There are 2 ways that CPM uses for checking KMS key - Alias & Tag KMS Tag When using custom tag, you are telling CPM to ...CPM Server upgrade may fail with the "Reason: The instance ID 'i-1234567890abcdef' does not exist" and "Configuration Failed" errors
CPM Server upgrade may fail with the "Reason: The instance ID 'i-1234567890abcdef' does not exist" and "Configuration Failed" errors: The reason for this failure is using wrong AWS Access Key and Secret Key - maybe they belong to the wrong account.