Deploy an SDDC to host your workloads in the cloud.
To create an SDDC, pick an AWS region to host it, give the SDDC a name, and specify how many ESXi hosts you want the SDDC to contain. If you don't already have an AWS account, you can still create a starter configuration SDDC that contains a single ESXi host. There is a one-to-one relationship between SDDCs and customer AWS accounts. You can connect an SDDC to a single customer AWS account and Amazon VPC.
- Log in to the VMC Console at https://vmc.vmware.com.
- Click Create SDDC.
- Configure SDDC properties.
- Select the AWS region in which to deploy the SDDC.
The following regions are available:
US West (Oregon)
US East (N. Virginia)
Asia Pacific (Sydney)
Asia Pacific (Tokyo)
US West (N. California)
US East (Ohio)
- Select deployment options.
Select this option to create Single Host Starter Configuration SDDC. Single Host Starter Configuration SDDCs expire after 30 days. For more information, see Deploying a Single Host SDDC Starter Configuration.
Select this option to create an SDDC with three or more hosts.
If you create a multiple-host SDDC, you also have the option to create a stretched cluster that spans two availability zones. The multiple availability zone stretched cluster provides fault tolerance and availability in the event that there is a problem with one of the availability zones. You must have a minimum of six hosts in a stretched cluster, and you must deploy an even number of hosts.Note:
The US West (N. California) region does not currently support Stretched Clusters.
- Enter a name for your SDDC.
- If you are creating a multiple host SDDC, specify the initial Number of Hosts you want in the SDDC.
You can add or remove hosts later if you need to.Note:
Storage capacity, performance, and redundancy are all affected by the number of hosts in the SDDC. See Storage Capacity and Data Redundancy for more information.
Host Capacity and Total Capacity update to reflect the number of hosts you've specified.
- Select the AWS region in which to deploy the SDDC.
- Connect to an AWS account.
Skip for now
If you don't have an AWS account or don't want to connect to one you have now, you can postpone this step for up to 14 days. This option is currently available for Single Host SDDCs only.
Use an existing AWS account
From the Choose an AWS account drop-down, select an AWS account to use an AWS account that was previously connected to another SDDC. If no accounts are listed in the drop-down, you must Connect to a new AWS account.Note:
Ensure that you do not select an account that is currently connected to an active SDDC. VMware Cloud on AWS does not support connecting multiple SDDCs to the same AWS account.
Connect a new AWS account
From the Choose an AWS account drop-down. select Connect to a new AWS account and follow the instructions on the page. The VMC Console shows the progress of the connection.
See AWS VPC Subnet Configuration and Availability Requirements for important information about requirements for the subnets you create in this AWS account.
- Click NEXT to specify a range of IP addresses for the management subnet in the SDDC.
Enter an IP address range for the management network as a CIDR block or leave the text box blank to use the default, which is 10.2.0.0/16. You can't change the values specified for the management network after the SDDC has been created, so consider the following when you specify this address range:
Choose a range of IP addresses that does not overlap with the AWS subnet you are connecting to. If you plan to connect your SDDC to an on-premises data center, the IP address range of the subnet must be unique within your enterprise network infrastructure. It cannot overlap the IP address range of any of your on-premises networks.
The IP address range 192.168.1.0/24 is reserved for the default compute gateway logical network of the SDDC you are deploying. If you specify a management network address range that overlaps with 192.168.1.0/24, the default compute gateway logical network cannot be created during deployment, so you'll need to create one manually after the SDDC is deployed.
In addition, CIDR blocks 10.0.0.0/15 and 172.31.0.0/16 are reserved for internal use. The management network CIDR block cannot overlap either of these ranges.
CIDR blocks of size 16, 20, or 23 are supported. The primary factor in selecting a Management CIDR block size is the anticipated scalability requirements of the SDDC. If you intend to scale your SDDC beyond four hosts, consider using a /20 CIDR block. For CIDR blocks of size 20 or 16, the maximum number of hosts your SDDC can contain is limited to 160. Regardless of the number of AZs it occupies, an SDDC can have at most ten clusters with at most 16 hosts per cluster.
A /23 CIDR block is appropriate for testing, or for SDDCs that you know will not require much growth in capacity. For CIDR blocks of size 23, the maximum number of hosts your SDDC can contain depends on the CIDR block size you specify and whether the SDDC occupies a single availability zone (AZ) or multiple AZs.
CIDR block size
Number of hosts (Single AZ)
Number of hosts (Multi AZ)
160 (10 clusters with at most 16 hosts per cluster, regardless of the number of AZs.)
- Acknowledge that you understand and take responsibility for the costs you incur when you deploy an SDDC, then click DEPLOY SDDC to create the SDDC.
Charges begin when you click DEPLOY SDDC. You cannot pause or cancel the deployment process after it starts. You won't be able to use the SDDC until deployment is complete. Deployment typically takes about two hours.
What to do next
To connect to vCenter Server and manage your new SDDC, you must either configure a VPN connection to the management gateway or configure a firewall rule to allow access to vCenter Server.