An infrastructure source endpoint is a connection to the infrastructure that provides a set (or multiple sets) of resources, which can then be made available by IaaS administrators for consumption by end users. vRealize Automation IaaS regularly collects information about known endpoint resources and the virtual resources provisioned therein. Endpoint resources are referred to as compute resources (or as compute clusters, the terms are often used interchangeably).

Infrastructure data is collected through proxy agents that manage and communicate with the endpoint resources. This information about the compute resources on each infrastructure endpoint and the machines provisioned on each computer resource is collected at regular intervals.

During installation of the vRealize Automation IaaS components, you can configure the proxy agents and define their associated endpoints. Alternatively, you can configure the proxy agents and define their associated endpoints separately after the main vRealize Automation installation is complete.

Table 1. Endpoint Design Decisions

Decision ID

Design Decision

Design Justification

Design Implication


Create one vSphere endpoint.

A single vSphere endpoint is required to connect to the consolidated vCenter Server instance.



Create one vRealize Orchestrator endpoint to connect to the embedded vRealize Orchestrator instance.

vRealize Automation extensibility uses vRealize Orchestrator, which requires the creation of a single orchestrator endpoint.



Create one NSX endpoint and associate it with the vSphere endpoint.

The NSX endpoint is required to connect to the NSX Manager and enable all the NSX-related operations supported in vRealize Automation blueprints.