Administrators may encounter the following error message when using MCS with Amazon (AWS) hosting connections:

Transaction ID: XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Action Name: MC_AddMachineInitialzation
 
Exception:
    <Domain name\machine-name$> : [Domain name\machine-name$, Failed to create the virtual machine; Domain name\machine-name$.
    Error Details
    MachineFailure
     : Domain name\machine-name$ Error:
    You do not have a host with a matching configuration and sufficient capacity. Either target a host resource group that can automatically allocate hosts on your behalf, or manually allocate a new host to your account and then try again.
    Error Details
    ErrorID
     : PluginUtilities.Exceptions.HostingInfrastructureCommunicationsFailureExceptionTaskErrorInformation
     : PluginUtilities.Exceptions.HostingInfrastructureCommunicationsFailureException: You do not have a host with a matching configuration and sufficient capacity. Either target a host resource group that can automatically allocate hosts on your behalf, or manually allocate a new host to your account and then try again. ---> PluginUtilities.Exceptions.WrappedPluginException: You do not have a host with a matching configuration and sufficient capacity. Either target a host resource group that can automatically allocate hosts on your behalf, or manually allocate a new host to your account and then try again.
 

MCs supports AWS dedicated hosts through two workflows: 

1. Create a catalog by specifying the Tenancy Type as a dedicated host

   • To ensure the error highlighted in this article is not triggered, make sure that the availability zone that you are provisioning your VMs into has enough dedicated hosts with sufficient capacity allocated

   • Make sure the dedicated hosts have “Instance auto-placement” enabled

   • See https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/how-dedicated-hosts-work.html#dedicated-hosts-allocating for details and requirements 

2. Use a machine profile source that was launched

   • Onto a dedicated host (see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/how-dedicated-hosts-work.html#launching-dedicated-hosts-instances for requirements and details for the source instance used). The provisioned VMs will be launched onto te same dedicated host as the machine profile source.

   • Into a host resource group (see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/how-dedicated-hosts-work.html#launching-hrg-instances for requirements and details for the source instance used). The provisioned VMs will be launched into the same host resource group as the machine profile source.

Example Walkthrough of Machine Profile Workflow with Host Resource Group

1. In the EC2 console, right click on your desired instance to use as the machine profile source and select "create template from instance" to create a launch template
   • 
     
     
2. Scroll down to "Advanced Details" and find the Tenancy section to specify the HRG fields. Make sure to: (a) select dedicated host for the tenancy, (b) target host by host resource group, and (c) specify the host resource group you’d like to use. Make sure that the rest of your launch template properties are set properly and as expected.
   • 
     
     
3. Use this launch template as the machine profile source (e.g., use New-ProvScheme -MachineProfile "XdHyp:\HostingUnits\<aws-hosting-unit-name>\launch-template-name (lt-xxxx).launchtemplate\lt-xxxx (n).launchtemplateversion" to deploy the machines via MCS)

Problem Cause

Incorrect configuration