Some cloud accounts require a deployed cloud proxy to manage the connection between the vendor account and Automation Assembler. You can create a cloud proxy to manage one or more vCenter-based cloud accounts. You can also create a cloud proxy to manage certain vCenter-based integrations, while other integrations require a cloud extensibility proxy.

If your organization is spread across multiple geographic areas, you might want to set up multiple cloud proxies to spread the workload. For example, you might consider setting up cloud proxies by geography, by project, or by deployment intent.

When you add a cloud account that is associated to a deployed cloud proxy, Automation Assembler collects information about that account such as network and machine data.

You can configure a cloud proxy before you create a cloud account or during the process of creating a cloud account. A common practice is to first configure a cloud proxy on a particular vCenter and then select the existing cloud proxy when you create a cloud account.

If you are creating a VMware Cloud on AWS cloud account that you plan to associate with a vCenter server in a data center that exists within the United States, you can associate the cloud account with an Atlas Agent Platform (AAP) instance, rather than with a cloud proxy. Note that you cannot change the association of an existing VMware Cloud on AWS cloud account from cloud proxy to AAP or from AAP to cloud proxy.

for related information about cloud proxies, see Adding cloud accounts to Automation Assembler. For details about how the cloud proxy works, see Understanding the VMware Cloud Services Cloud Proxy.

The step values that you enter in this procedure are only use case examples. You won't be able to use them letter-by-letter in your environment unless otherwise stated in the procedure.