MCS on AWS failed with error "The Catalog could not be loaded due to the following errors: There are no master images associated with this catalog"

MCS on AWS failed with error "The Catalog could not be loaded due to the following errors: There are no master images associated with this catalog"

book

Article ID: CTX245772

calendar_today

Updated On:

Description

Fail to create new machine catalog on AWS. The error in studio shows that  "The Catalog could not be loaded due to the following errors: There are no master images associated with this catalog".
And the following error can be found in the CDF trace.
"Launch of new volume worker instance failed with exception: PluginUtilities.Exceptions.ManagedMachineGeneralException: Timeout waiting for xxxx to reach a required state. Current state PoweredOn."

Resolution

Open 80/443 ports for inbound transport on customer's AWS China account.

Problem Cause

MCS follows the below process to create vm on AWS.
1.Create an S3 Bucket on AWS
2.Uploading our service RPM file to the S3 Bucket
3.Creating a signed URL to retrieve our RPM from the S3 Bucket
4.Creating a volume worker with userdata containing a script to install our service using the signed URL

But for AWS China user, we cannot access the URL as the 80/443 ports for inbound transport is blocked by default.
So step 4 cannot complete, and then MCS will throw the above error at last.