Register VMware Cloud on AWS Source

3 April 2024

To start protecting your VMware Cloud on AWS SDDC (software-defined data center), you need to register it as a source on Cohesity DataProtect as a Service.

Before you Begin

  • Create a VMware SaaS Connection in your VMC environment (using your VMware Cloud Services console) to establish connectivity between your sources and the Cohesity DataProtect as a Service. For details, see Deploy VMware SaaS Connectors.

  • Ensure that the requirements for the VMware Cloud on AWS source, such as software version, user account role privileges, and firewall ports, are met.

Register

To register your VMware Cloud on AWS source:

  1. In DataProtect as a Service, navigate to Sources and click + Register Source > Virtual Machines.

  2. In the Register Virtual Machines Source form, select an existing SaaS connection from the SaaS Connection drop-down, or click Create SaaS Connection and follow the instructions in the Deploy VMware SaaS Connectors section.

  3. Select the Source Type as VMware: vCenter.

  4. Enter the Hostname or IP Address of the VMware Cloud Services console.

  5. Enter the Username and Password you use to log into the VMware Cloud Services console.

  6. Click Save.

The VMware Cloud Services source is registered and displayed under the Sources page. For information on managing your VMC on AWS source, see Manage the VMC on AWS Source.

Create SaaS Connector Groups

You must create at least one SaaS Connector group for each ESXi cluster that needs to be protected if there is more than one ESXi cluster in the SDDC. When creating the SaaS Connector Groups:

  1. Group the SaaS Connectors at each ESXi cluster into two separate SaaS Connector Groups.

  2. Associate the Connector Groups with the respective ESXi clusters.

For example, to protect two ESXi clusters (EC-1 and EC-2) in your SDDC, add the SaaS Connectors of EC-1 to SaaS Connector Group CG-1 and EC-2 to SaaS Connector Group CG-2. Then associate CG1 to EC-1 and CG2 to EC-2.

If there is only one ESXi cluster in the SDDC and no plans to add more ESXi clusters, SaaS Connector Groups are not required.

Next > You are now ready to protect your VMC on AWS source.