Dec 14,2020 Miscellaneous 3

Discovery and Assessment Capabilities for Customers Looking to Migrate from VMware on AWS to Amazon EC2 with CloudChomp CC Analyzer

Published on December 14, 2020 by Lori Day

By Gary Margolis, Solutions Architect at CloudChomp, Inc.
By Jonathan Trelles, Solutions Architect at AWS



Many customers look to VMware Cloud on AWS as a long-term solution as they continue their VMware relationship and search for more efficient ways of handling infrastructure, computing, storage, networking, and support. For others, VMware Cloud on AWS is part of a larger cloud adoption journey that will eventually lead to modernization efforts to AWS cloud native services. CloudChomp provides benefits to both groups. For customers staying on VMC, CloudChomp provides ongoing cost management, application discovery, dependency mapping, and right-sizing of VMs. For those looking to move to native services, CloudChomp offers a full suite of powerful, collaborative assessment tools to evaluate their current VMware Cloud on AWS deployment. These tools help customers migrate their workloads to Amazon EC2, so that they can reap the financial and technological benefits of using native AWS services. CloudChomp provides the customer with a full range of tools from discovery to a migration statement of work. The customer can organize their assessment by any number of factors including cost, complexity, project, and urgency. This allows continuous analysis and modernization to an ever-expanding array of AWS native services


CloudChomp Eco-System

CloudChomp consists of one or more collectors (CC Explorer) that are installed in the customer’s environment. These collectors user a variety of methods including vCenter database calls, SNMP, and WinRM (WMI) to pull configuration and utilization data from the customer’s environment. This data is then sent to the CloudChomp backend processing engine on AWS. The data is ingested and made available for analysis in the CC Analyzer web portal.



CC Explorer Deployment

CloudChomp Explorer is a virtual appliance delivered as an OVA file that is installed in your virtualized environment and collects data about your infrastructure. The OVA will need to be deployed in the VMware on AWS Software-Defined Data Center (SDDC) as shown below.

Power on the newly deployed virtual machine and assign a unique identifier for your CC Explorer deployment.

Configure the network configuration for CC Explorer.

Please note that CC Explorer will need to communicate with CC Analyzer via DNS names ( and If no dedicated DNS server exists in your infrastructure, use a public DNS resolver as shown in the screenshot below.

Then verify the network configuration to ensure that CC Explorer can communicate with CC Analyzer.

Now that CC Explorer has been setup, the collector has to be configured to gather VMware on AWS server information.

CC Explorer for Discovery

Please have the SNMP agent configured on the target machines with credentials ready at hand. CC Explorer supports SNMP v1, v2, v2c and v3 and requires read-only access. You can configure SNMP agents on all target agents after CC Explorer setup, however we highly recommend to have the SNMP agents configured on at least a few machines to help us debug any issues during setup, should they arise. Also, allow the default UDP ports 161 and 162 across all machines to be monitored.

Logon to CC Explorer via the IP address and credentials provided in the WebUI Information.

On the default dashboard page, select CC Explorer for Discovery and click Create Discovery.

Give the discovery task a name and specify the IP range(s) where the target machines are hosted.

Then specify the SNMP credential information and click Create.

CC Explorer will being collecting information for the VMware on AWS machines specified in the IP range(s) during the discovery task creation.

Lastly, register CC Explorer with your CC Analyzer instance to bring up the API Connection Status. CC Analyzer is the web portal leveraged to analyze the collected data from CC Explorer.


VMware Data not collectable by SNMP

It is important to remember that the VMs collected by SNMP or WinRM will look like individual standalone machines rather than VMs. This means that information such as vCenter, host, data center, and cluster name are not automatically available, but can be imported via flat file. WinRM has the added advantage of collecting SQL Server edition and version information. Finally, all storage is viewed as local to the VMs.



CloudChomp’s TCO-based migration assessment technology provides a platform for migration specialists to collect, analyze, and plan cloud migration paths with a focus on total cost of ownership.

CloudChomp’s data collection options ensure that data from heterogeneous sources can be easily fed to the system. The right-sizing and recommendation engines provide the flexibility for migration specialists to tune the algorithms to fit their specific needs.

CC Analyzer’s inventory consists of compute, storage, and SQL software licenses. TCO estimates are calculated for both source and target environments, helping assess the overall ROI for the migration.


Call to Action

You can also visit and for training, demos, assistance, and to learn more.

Leave a Reply

Your email address will not be published. Required fields are marked *