A cloud account identifies a cloud account type and a data center where the associated cloud account resources are hosted.

The cloud accounts in your project are based on the vendor (cloud account) type and the region (data center or vCenter) where that cloud account resides. As you define profiles and mappings, you specify data in relation to a specific cloud account type and region in your project. Later, a blueprint administrator chooses profile, mapping, and tag settings as they define and deploy blueprints.

As a Cloud Assembly cloud account 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 defined cloud accounts. See WordPress use case: add cloud accounts.

The following cloud account types are supplied with Cloud Assembly:

Image shows all the available cloud accounts in the following bulleted list.

  • Amazon Web Services

  • Microsoft Azure and Microsoft Azure Enterprise

  • Google Cloud Platform

  • VMware Cloud on AWS

  • vCenter

  • NSX-T

  • NSX-V

vCenter-based cloud accounts require that a cloud proxy is deployed to a source vCenter for data collection and communication between the cloud account and an on-premises endpoint.

For network and security purposes, you can associate an NSX-T or NSX-V cloud account with a vCenter cloud account. You can also associate an NSX-T cloud account with a VMware Cloud on AWS cloud account.

VMware Cloud on AWS must be associated to a cloud proxy that 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 Manage > Integrations page. See What are Integrations.