Hi, and welcome back. In this short lecture, we'll set up the AWS Discovery Connector. To do this, we first need to download and deploy the OVA file from the AWS website. So first, we choose to download the agent from the AWS site here. Now we need to sign into vCenter as a VMware administrator. Once in there, choose File, deploy OVF template.

Now the most important thing to remember is the disk formatting, right. So on the disk format page, select one of the thick provision disk types, ideally Thick Provision Eager Zeroed, because it has the best performance and reliability. It does, however, require a couple of hours to zero out the disk, so there is gonna be some delay. So don't choose thin provision, right, that option makes deployment faster, but significantly reduces disk performance in the long run. The console displays the IP address of the Connector console, so save that IP address into a secure location so you can access it later, you're gonna need it to complete the Connector setup process.

So after you complete this initial setup you can access the Connector settings by using SSH, and the Connector IP address, :root@Connector_IP_address. Okay, a few things to consider in the setup. The agentless Discovery Connector has an auto-update feature, so turning on the auto-update feature ensures that you have the latest version of the Discovery Connector. So you can enable auto-updates under the Actions menu, and just choose Enable Auto-Updates.

Now a few common problems to avoid. So the agentless Discovery Connector doesn't support standalone ESX hosts, so you need to have all hosts registered in vCenter. If you don't see inventory information coming through to the migration hub, after starting data collection with the Connector, make sure you have registered the Connector with your vCenter server. So you may need to stop and start the services a few times to confirm that it is registered.

The Discovery Connector can see all the VMs, but not within the actual VM itself. So you'll get some information, but not all of the information about what's actually inside the Virtual Machine. Discovery Connector doesn't provide the same level of granularity as you do get with the Discovery agent.

To discover data about all ESX hosts and Vms, under the current vCenter set, set your role in the vCenter user to read only, and that will show you all the hosts. However, perhaps you only plan to migrate a subset of VMs, or perhaps you have constraints on reporting and visibility of your entire fleet, so you may not want to report all services within your vCenter environment.

Now you can use these permission settings to restrict which hosts and VMs are included in your data collection. So you can either allow all hosts and VMs under the current vCenter to be inventoried, or you can grant permissions, on a case by case basis, to restrict access to those that you do not want to make visible. That brings this lecture, on the Discovery Connector, to a close.