When submitting a Service Broker request form to deploy an AWS VM, certain Instance Types (flavors) may not be available for selection, or the deployment may fail with an error indicating the type does not exist, even though the type is valid in the selected region. This issue is typically observed in regions that contain a large number of available Instance Types (e.g., over 1000).
The deployment fails with an error similar to:
Exception occurred while retrieving instance type info from adapter: Enhancer failed on GET InstanceType object: : Non existing instance type: (Instance Type)
Product: Aria Automation
Component: Service Broker, AWS Cloud Account Integration
Cloud Endpoint: AWS EC2
Affected Version(s): All Automation versions prior to the fix which will be version 8.18.1 Patch 4
This issue is due to a product limitation in the Aria backend component that communicates with the AWS EC2 API.
When the AWS EC2 API action DescribeInstanceTypeOfferings is executed to retrieve the list of available Instance Types, the request has a maximum result limit of 1000 per page. To retrieve results beyond this limit, the AWS API uses a mechanism called Pagination and provides a NextToken in the response. The Aria backend was not configured to implement the NextToken logic to fetch subsequent pages of Instance Types past the initial 1000 limit.
Therefore, in regions which may have more than 1000 Instance Types, any Instance Type that falls outside the first 1000 retrieved results is not visible to the Aria service, leading to the selection failure.
This issue has been identified as a product limitation and a fix is under review with Broadcom Engineering.
The resolution will be implemented in a future release to ensure the Aria backend correctly handles AWS EC2 API pagination for retrieving all Instance Types.
The fix is expected to be in Aria Automation version 8.18.1 Update 4.
VMware By Broadcom is aware of this issue. Please refer to the release notes for existing and forthcoming product releases for any updates in relation to this issue. Should you require further information please contact Broadcom Support.
Until the fix is generally available, a workaround is to use a cloud region for deployment that is known to have less than 1000 Instance Types available.