Recovering windows instance might fail with error: The request must contain the parameter ImageID
Issue:
When recovering instance from DR account to DR account, it might fail with the following error in logs:
2020-09-22 00:16:35,135:[140237924660992][----------] ERROR: execute_api_call(__init__.py:140) Failed calling ec2.run_instances (region: me-south-1, account: a2 (12345678), user: General). Exception: The request must contain the parameter ImageId (MissingParameter)
And this error in UI:
Solution:
When recovering a Windows
instance and the image id is not found (e.g., cross account DR), You should locate
the appropriate image id and fill it at the recovery form in the UI.This can be done with the help of the AMI Assistant in the recovery UI
Related Articles
Recovery fails with "Enhanced networking with the Elastic Network Adapter (ENA) is required for the 'xxxx.XXXXX' instance type. Ensure that you are using an AMI that is enabled for ENA."
When attempting a windows instance recovery with ENA enabled, it may fail with the following error: "Enhanced networking with the Elastic Network Adapter (ENA) is required for the 'xxxx.XXXXX' instance type. Ensure that you are using an AMI that is ...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 ...A c5 instance recovery from snapshot may fail
If CPM didn't backup a c5 instance with initial ami (snapshots only), the recovery may fail with the following error: To recover a c5 instance you will need to use the AWS CLI to create an AMI to be used during recovery. The examples below are ...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" ...billingProducts code is null and YUM updates fail after restore of some SUSE and Red Hat Instances
On some operating systems, primarily SUSE and Red Hat, you will find that AWS cannot properly restore the "billingProducts" ID in the metadata for the instance and the field will be set to "null". Also, YUM repository updates will begin to fail. If ...