You can install a new cloud proxy as part of the vCenter-based cloud account creation process, or you can select a previously installed cloud proxy as you create the cloud account in Cloud Assembly.
The supplied cloud proxy OVA contains the credentials and protocols you need to connect a proxy appliance on a host vCenter Server to vCenter-based cloud accounts and integrations in Cloud Assembly. You download the OVA and deploy it to a target vCenter Server. Once the cloud proxy is installed and running, you can associate it to one or more vCenter-based cloud accounts and integrations.
A VMware Cloud on AWS cloud account can only be associated to a cloud proxy that is deployed to a vCenter in a target VMware Cloud on AWS SDDC.
- Verify that you have cloud administrator credentials. See Credentials required for working with cloud accounts in vRealize Automation.
- Verify that you have the cloud administrator user role. See What are the vRealize Automation Cloud user roles.
- If you are creating a cloud proxy to use with a VMware Cloud on AWS cloud account, see Create and deploy a cloud proxy for a VMware Cloud on AWS cloud account in Cloud Assembly.
- To support the cloud proxy, whitelist access to the following domains is required. For more detailed information about cloud proxy requirements, see the Understanding the VMware Cloud services cloud proxy configuration document:
- ci-data-collector.s3.amazonaws.com – enables Amazon Web Services S3 access for cloud proxy OVA download.
- symphony-docker-external.jfrog.io - allows JFrog Artifactory to access Docker images.
- data.mgmt.cloud.vmware.com - enables the data pipeline service connection to VMware Cloud services for secure data communication between cloud and on-premises elements. For non-US regions, substitute the region value. For example, for the UK, use uk.data.mgmt.cloud.vmware.com and for Japan, use ja.data.mgmt.cloud.vmware.com.
- api.mgmt.cloud.vmware.com – enables the Web API and cloud proxy service connection to VMware Cloud services. For non-US regions, substitute the region value. For example, for the UK, use uk.api.mgmt.cloud.vmware.com and for Japan, use ja.data.mgmt.cloud.vmware.com.
- Select New Cloud Proxy.
- Download the cloud proxy OVA.
- Rename the downloaded OVA something unique, for example vCenter1_vmc_va.ova.
You can download and name the cloud proxy OVA to make it obvious what it is used for, for example when using a particular cloud account for a particular purpose.
- Navigate to your vSphere Web Client data center, click the name of your vCenter Server cluster, and select Deploy OVF Template.
- Enter information as prompted to install the OVA on your vCenter Server.
- When prompted to enter the key or token, return to the Install Cloud Proxy page and click Copy.
- (Optional) To configure additional security and force connections to pass through a proxy server, use the Network Proxy Hostname/IP Address, Network Proxy Port, Network Proxy Username, and Network Proxy Password options to configure the network proxy:
For details about configuring these cloud proxy settings, see Understanding the VMware Cloud services cloud proxy.
- Return to the vSphere Web Client and paste the provided key value to install the cloud proxy's virtual appliance.
- In Cloud Assembly, wait for a connection to be made with your vSphere Web Client and then click Done.
It might take several minutes to connect.
- (Optional) To configure a network proxy after the cloud proxy virtual appliance is deployed, modify the configure-network-proxy file in the cloud proxy VA by using the following procedure:
- SSH into the cloud proxy VA.
- Open the /root/configure-network-proxy file and provide the network proxy configuration settings.
- Save the file.
What to do next
To verify that the cloud proxy is running, see Verify that a cloud proxy is running on a target virtual machine.
You can now add vCenter-based cloud accounts and integrations that require the cloud proxy.