vCenter Setup

Increasing the number of vCenter instances in your vRealize Orchestrator setup causes vRealize Orchestrator to manage more sessions. Too many active sessions can cause vRealize Orchestrator to experience timeouts when more than 10 vCenter connections occur.

For a list of the supported versions of vCenter, see the VMware Product Interoperability Matrix.

Note: If your network has sufficient bandwidth and latency, you can run multiple vCenter instances on different virtual machines in your vRealize Orchestrator setup. If you are using LAN to improve the communication between vRealize Orchestrator and vCenter, a 100-Mb line is mandatory.

Standalone vRealize Orchestrator support for VMware Cloud on AWS

Standalone vRealize Orchestrator deployments do not support VMware Cloud on AWS authentication and because of this you cannot run vRealize Orchestrator workflows on VMware Cloud on AWS vCenters.