Cloud accounts are the configured permissions that Cloud Assembly uses to collect data from the regions or data centers, and to deploy cloud templates to those regions.
The collected data includes the regions that you later associate with cloud zones.
When you later configure cloud zones, mappings, and profiles, you select the cloud account to which they are associated.
As a cloud administrator, you create cloud accounts for the projects in which team members work. Resource information such as network and security, compute, storage, and tags content is data-collected from your cloud accounts.
If you remove a cloud account that is used in a deployment, resources that are part of that deployment become unmanaged.
Some cloud accounts and some integrations require a cloud proxy.
What are cloud proxies
A cloud proxy routes information to, and collects data from, a Cloud Assembly account and your on-premises applications such as vCenter and NSX and integrations such as Puppet and Google Cloud Platform. You deploy a supplied cloud proxy to a vCenter Server of your choice by using on-screen instructions. You can configure one cloud proxy for multiple vCenter Server instances, or you can have one cloud proxy for a specific vCenter Server.
- VMware Cloud on AWS
- vRealize Orchestrator
For details about how the cloud proxy works, see Understanding the VMware Cloud Services Cloud Proxy.
Monitoring the cloud account health
To ensure that your cloud accounts are communicating with the target system, the status of the account appears on the card based on periodic health checks.
OK is good. Warning indicates that there might be a problem that needs your attention.
In some cases, the details will help you resolve the issue. In other cases, you can run the Update option. It might also be the case that the connection is lost, in which case Update does not resolve the project. One possible scenario is that the credentials have expired. Re-establish a connection with updated credentials.