When we are running the MCS process and it fails with generic error message.

 
Below are the steps we observed happening when we create the catalogue.
 

1. Preparation VM gets created.
2. Preparation VM goes into stopped state.
3. XenDesktopTemp gets created.
4. We can see an object uploaded to S3 from DDC.
5. XenDesktop Temp does not shuts down.
6. After 30 minutes, exception is thrown and MCS process fails.

Changed the DHCP option set for default VPC to point to AWS default DNS servers.

---

Problem Cause

If default VPC is configured with custom DNS server, XenDesktop Temp cannot resolve the name for S3 URL then XenDesktop VM will never be able to initiate an HTTPS connection to S3 bucket. This will not work even if you provide the internal DNS server as primary and AWS as secondary or vice-versa.

This is the default behaviour of a linux machine running on AWS.

https://support.citrix.com/article/CTX241160