A cloud account identifies a cloud account type and a data center where the associated cloud account resources are hosted and the credentials that are required to use the clouds account.
As a Cloud Assembly cloud account administrator, you create cloud accounts for the projects in which team members work. See Credentials for Cloud Assembly Cloud Accounts.
The cloud accounts in your project are based on vendor type and data center or vCenter residency, depending on cloud account type. As you define profiles and mappings, you specify data in relation to a specific cloud account/region in your project. A blueprint administrator working in your project can then choose defined profile, mapping, and tag settings to define blueprint characteristics, which Cloud Assembly uses to determine how and where to deploy the blueprint.
The following cloud account types are supplied with Cloud Assembly:
Amazon Web Services
Microsoft Azure and Microsoft Azure Enterprise
VMware Cloud on AWS
When you create a cloud account and associate it with a data center region or a source on-premises endpoint in vCenter, existing resources such as network, compute, and storage information, including tags, are data-collected from the source endpoint. Data collection occurs when you finish defining the cloud account. See WordPress Use Case: Add Cloud Accounts.
vCenter-based cloud accounts require that a cloud proxy be deployed to a source vCenter for data collection and communication between the cloud account and an on-premises endpoint.
NSX-T and NSX-V cloud accounts must be associated with an existing vCenter cloud account.
VMware Cloud on AWS must be associated to a cloud proxy is deployed to a vCenter in a target SDDC.
As a cloud account administrator, you can create additional integrations such as My VMware, vRealize Orchestrator, and Puppet by using options on the page. See What are Integrations.