AWS Application Discovery Service is no longer open to new customers. Alternatively, use AWS Transform which provides similar capabilities. For more information, see [AWS Application Discovery Service availability change](https://docs.aws.amazon.com/application-discovery/latest/userguide/application-discovery-service-availability-change.html).

# Using the VMware vCenter Agentless Collector data collection module
<a name="agentless-collector-gs-data-collection-vcenter"></a>

This section describes the Application Discovery Service Agentless Collector (Agentless Collector) VMware vCenter data collection module, which is used to collect server inventory, profile, and utilization data from your VMware VMs.

**Topics**
+ [Setting up the Agentless Collector data collection module for VMware vCenter](agentless-collector-gs-vcenter.md)
+ [Viewing VMware data collection details](agentless-collector-gs-vcenter-details.md)
+ [Controlling the scope of vCenter data collection](control-data-collection-scope.md)
+ [Data collected by the Agentless Collector VMware vCenter data collection module](agentless-collector-data-collected-vmware.md)

# Setting up the Agentless Collector data collection module for VMware vCenter
<a name="agentless-collector-gs-vcenter"></a>

This section describes how to set up the Agentless Collector VMware vCenter data collection module to collect server inventory, profile, and utilization data from your VMware VMs.

**Note**  
Before starting vCenter setup, make sure you can provide vCenter credentials with Read and View permissions set for the System group.

**To set up the VMware vCenter data collection module**

1. On the **Agentless Collector** dashboard page, under **Data collection**, choose **Set up** in the **VMware vCenter** section.

1. On the **Set up VMware vCenter data collection** page, perform the following:

   1. Under **vCenter credentials**:

      1. For **vCenter URL/IP**, enter the IP address of your VMware vCenter Server host.

      1. For **vCenter Username**, enter the name of a local or domain user that the collector uses to communicate with vCenter. For domain users, use the form *domain*\$1*username* or *username*@*domain*.

      1. For **vCenter Password**, enter the local or domain user password.

   1. Under **Data collection preferences**:

      1. To automatically start collecting data immediately following a successful setup, select **Start data collection automatically**.

   1. Choose **Set up**.

Next, you'll see the **VMware data collection details** page, which is described in the next topic.

# Viewing VMware data collection details
<a name="agentless-collector-gs-vcenter-details"></a>

The **VMware data collection details** page shows details about the vCenter you set up in [Setting up the Agentless Collector data collection module for VMware vCenter](agentless-collector-gs-vcenter.md).

Under **Discovered vCenter servers**, the vCenter you set up is listed with the following information about the vCenter:
+ The IP address of the vCenter server.
+ The number of servers in the vCenter.
+ The status of the data collection.
+ How long since the last update.

Choose **Remove vCenter server** to remove the displayed vCenter server and return you to the **Set up VMware vCenter data collection** page.

If you did not choose to start data collection automatically, you can start data collection by using the **Start data collection** button on this page. After data collection starts, the start button changes to **Stop data collection**.

If the **Collection status** column shows **Collecting**, data collection has started.

You view the collected data in the AWS Migration Hub console. If you’re collecting data for a VMware vCenter server inventory, you can access data that appears in the console approximately 15 minutes after turning on data collection.

You can choose **View servers in Migration Hub** on this page to open the Migration Hub console, if your access to the internet is not blocked. Whether you choose this button or not, for information about how to access the Migration Hub console, see [Viewing your collected data](agentless-collector-gs-view-collected-data.md).

The following are the guidelines for recommended length of data collection according to migration planning activities: 
+ TCO (total cost of ownership) - 2 to 4 weeks
+ Migration planning - 2 to 6 weeks

# Controlling the scope of vCenter data collection
<a name="control-data-collection-scope"></a>

The vCenter user requires read-only permissions on each ESX host or VM to inventory using Application Discovery Service. Using the permission settings, you can control which hosts and VMs are included in the data collection. You can either allow all hosts and VMs under the current vCenter to be inventoried, or grant permissions on a case-by-case basis.

**Note**  
As a security best practice, we recommend against granting additional, unneeded permissions to the vCenter user of the Application Discovery Service.

The following procedures describe configuration scenarios ordered from least granular to most granular. These procedures are for vSphere Client v6.7.0.2. The procedures for other versions of the client might be different, depending on which version of the vSphere client you are using.

**To discover data about *all* ESX hosts and VMs under the current vCenter**

1. In your VMware vSphere client, choose **vCenter** and then choose either **Hosts and Clusters** or **VMs and Templates**. 

1. Choose a datacenter resource and then choose **Permissions**.

1. Choose the vCenter user and then choose the symbol to add, edit, or remove a user role.

1. Choose **Read-only** from the **Role** menu.

1.  Choose **Propagate to children** and then choose **OK**.

**To discover data about a *specific* ESX host and *all* of its child objects**

1. In your VMware vSphere client, choose **vCenter** and then choose either **Hosts and Clusters** or **VMs and Templates**. 

1. Choose **Related Objects**, **Hosts**. 

1. Open the context (right-click) menu for the host name and choose **All vCenter Actions**, **Add Permission**.

1. Under **Add Permission**, add the vCenter user to the host. For **Assigned Role**, choose **Read-only**. 

1. Choose **Propagate to children**, **OK**.

**To discover data about a *specific* ESX host or child VM**

1. In your VMware vSphere client, choose **vCenter** and then choose either **Hosts and Clusters** or **VMs and Templates**. 

1. Choose **Related Objects**.

1. Choose **Hosts** (showing a list of ESX hosts known to vCenter) or **Virtual Machines** (showing a list of VMs across all ESX hosts). 

1. Open the context (right-click) menu for the host or VM name and choose **All vCenter Actions**, **Add Permission**.

1.  Under **Add Permission**, add the vCenter user to the host or VM. For **Assigned Role**, choose **Read-only**, . 

1. Choose **OK**. 

**Note**  
If you chose **Propagate to children**, you can still remove the read-only permission from ESX hosts and VMs on a case-by-case basis. This option has no effect on inherited permissions applying to other ESX hosts and VMs. 

# Data collected by the Agentless Collector VMware vCenter data collection module
<a name="agentless-collector-data-collected-vmware"></a>

The following information describes the data that's collected by the Application Discovery Service Agentless Collector (Agentless Collector) VMware vCenter data collection module. For information about setting up data collection, see [Setting up the Agentless Collector data collection module for VMware vCenter](agentless-collector-gs-vcenter.md).

**Table legend for Agentless Collector VMware vCenter collected data:**
+ Collected data is in measurements of kilobytes (KB) unless stated otherwise.
+ Equivalent data in the Migration Hub console is reported in megabytes (MB).
+ Data fields denoted with an asterisk (\$1) are available only in the .csv files that are produced from the Application Discovery Service API export function. 

  The Agentless Collector supports data export using the AWS CLI. To export collected data using the AWS CLI, follow the instructions described under **Export System Performance Data for All Servers** on the page [ Export Collected Data](https://docs.aws.amazon.com/application-discovery/latest/userguide/export-data.html) in the *Application Discovery Service User Guide*. 
+ The polling period is in intervals of approximately 60 minutes.
+ Data fields denoted with a double asterisk (\$1\$1) currently return a *null* value.


| Data field | Description | 
| --- | --- | 
| applicationConfigurationId\$1 | ID of the migration application the VM is grouped under. | 
| avgCpuUsagePct | Average percentage of CPU usage over polling period. | 
| avgDiskBytesReadPerSecond | Average number of bytes read from disk over polling period. | 
| avgDiskBytesWrittenPerSecond | Average number of bytes written to disk over polling period. | 
| avgDiskReadOpsPerSecond\$1\$1 | Average number of read I/O operations per second null. | 
| avgDiskWriteOpsPerSecond\$1\$1 | Average number of write I/O operations per second. | 
| avgFreeRAM | Average free RAM expressed in MB. | 
| avgNetworkBytesReadPerSecond | Average amount of throughput of bytes read per second. | 
| avgNetworkBytesWrittenPerSecond | Average amount of throughput of bytes written per second. | 
| computerManufacturer | Vendor reported by the ESXi host. | 
| computerModel | Computer model reported by the ESXi host. | 
| configId | ID assigned by Application Discovery Service to the discovered VM. | 
| configType | Type of resource discovered. | 
| connectorId | ID of the virtual appliance. | 
| cpuType | vCPU for a VM, actual model for a host. | 
| datacenterId | ID of the vCenter. | 
| hostId\$1 | ID of the VM host. | 
| hostName | Name of host running the virtualization software. | 
| hypervisor | Type of hypervisor. | 
| id | ID of server. | 
| lastModifiedTimeStamp\$1 | Latest date and time of data collection before data export. | 
| macAddress | MAC address of the VM. | 
| manufacturer | Maker of the virtualization software. | 
| maxCpuUsagePct  | Max. percentage of CPU usage during polling period. | 
| maxDiskBytesReadPerSecond | Max. number of bytes read from disk over polling period. | 
| maxDiskBytesWrittenPerSecond | Max. number of bytes written to disk over polling period. | 
| maxDiskReadOpsPerSecond\$1\$1 | Max. number of read I/O operations per second. | 
| maxDiskWriteOpsPerSecond\$1\$1 | Max. number of write I/O operations per second. | 
| maxNetworkBytesReadPerSecond | Max. amount of throughput of bytes read per second. | 
| maxNetworkBytesWrittenPerSecond | Max. amount of throughput of bytes written per second. | 
| memoryReservation\$1 | Limit to avoid overcommitment of memory on VM. | 
| moRefId | Unique vCenter Managed Object Reference ID. | 
| name\$1 | Name of VM or network (user specified). | 
| numCores | Number of CPU cores assigned to VM. | 
| numCpus | Number of CPU sockets on the ESXi host. | 
| numDisks\$1\$1 | Number of disks on VM. | 
| numNetworkCards\$1\$1 | Number of network cards on VM. | 
| osName | Operating system name on VM. | 
| osVersion | Operating system version on VM. | 
| portGroupId\$1 | ID of group of member ports of VLAN. | 
| portGroupName\$1 | Name of group of member ports of VLAN. | 
| powerState\$1 | Status of power. | 
| serverId | Application Discovery Service assigned ID to the discovered VM. | 
| smBiosId\$1 | ID/version of the system management BIOS. | 
| state\$1 | Status of the virtual appliance. | 
| toolsStatus | Operational state of VMware tools | 
| totalDiskFreeSize | Free disk space expressed in MB. Available for vCenter Server 7.0 and later versions. | 
| totalDiskSize | Total capacity of disk expressed in MB. | 
| totalRAM | Total amount of RAM available on VM in MB. | 
| type | Type of host. | 
| vCenterId | Unique ID number of a VM. | 
| vCenterName\$1 | Name of the vCenter host. | 
| virtualSwitchName\$1 | Name of the virtual switch. | 
| vmFolderPath | Directory path of VM files. | 
| vmName | Name of the virtual machine. |