Using cloud proxies in vRealize Operations Cloud, you can collect and monitor data from your on-prem data center or cloud (VMC on AWS, VMC on Dell EMC, Azure VMware Solution, Google Cloud VMware Engine). You can deploy one or more cloud proxies in vRealize Operations Cloud to create a one-way communication between your end-point environment and vRealize Operations Cloud. The cloud proxies work as one-way remote collectors and upload data from the end-point environment to vRealize Operations Cloud. Cloud proxies can support multiple vCenter Servers or cloud accounts. For public cloud (AWS, Azure, GCP), the default collector can collect and monitor data. For more information on cloud proxies, see the topic called Cloud Proxy FAQ in the VMware vRealize Operations Cloud Getting Started Guide.
Prerequisites
- Verify that you have an IP address, a DNS entry, and permissions to deploy OVF templates in vSphere.
- Log in to vSphere and verify that you are connected to a vCenter Server system.
- Allow outgoing HTTPS traffic for cloud proxy over port 443.
- Allow outgoing traffic from the endpoints to cloud proxy over 443, 4505, and 4506.
- Ensure firewalls are configured to allow outgoing traffic to:
- *.vmwareidentity.com
- gaz.csp-vidm-prod.com
- *.vmware.com
- *.vrops-cloud.com
- s3-us-west-2.amazonaws.com/vrops-cloud-proxy
- Add a vCenter cloud account and provide an account with the following read and write privileges:
- vCenter IP address or FQDN
- Permissions required to install a cloud proxy on the vCenter Server.
For more information on privileges, see, Privileges Required for Configuring a vCenter Adapter Instance.
Procedure
What to do next
Upgrade your cloud proxy. For more information, see the topic called Upgrading Cloud Proxy in the VMware vRealize Operations vApp Deployment Guide.
Troubleshoot any cloud proxy issues. For more information, see Troubleshooting Cloud Proxy.