book
Article ID: CTX492468
calendar_today
Updated On:
Description
Unable to create machine catalogue with AWS Instance type t3a.2xlarge
Error,"[AWS]: PluginMachineManager.CreateDesktop: name=Preparation - ********>, template=ami-<********> exception=PluginUtilities.Exceptions.ManagedMachineGeneralException: Timed out waiting for: Creating machine '<********>' with pre-existing ENIs: eni-<********> ---> PluginUtilities.Exceptions.WrappedPluginException: Value (t3a.2xlarge) for parameter instanceType is invalid. Instance type 't3a.2xlarge' cannot be launched with tenancy 'dedicated' ---> PluginUtilities.Exceptions.WrappedPluginException: The remote server returned an error: (400) Bad Request. ---> PluginUtilities.Exceptions.WrappedPluginException: The remote server returned an error: (400) Bad Request.
Resolution
If you need to continue with dedicated tenancy
- select an instance type that has the property 'DedicatedHostsSupported' true.
OR
- On MCS catalog creation security page, select 'Use shared hardware' option to deploy the instance in shared tenancy. This will deploy the machines in shared hardware on AWS instead of dedicated.
Problem Cause
This is caused by dedicated instance\tenancy limitations on AWS. Some instance types cannot be launched on dedicated tenancy. Example t3a.2xlarge.
These instances can be deployed only on shared (default) tenancy type.
To verify this, check the property ‘DedicatedHostsSupported’ (Display name : Dedicated Host Support) of the instance type on AWS console.