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.


  1. Log in to the VMC Console at
  2. Click Create SDDC.
  3. Configure SDDC properties.
    1. Select the AWS region in which to deploy the SDDC.
      See Available AWS Regions for a list of available regions and the features they support.
    2. Select deployment options.
      Option Description
      Single Host 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 two or more hosts. Three hosts is the default.

      Stretched Cluster If you create a multiple-host SDDC, you also have the option to create a stretched cluster that spans two availability zones (AZs). This configuration provides data redundancy in the event that there is a problem with one of the AZs. The system deploys management VMs in the first AZ you select. Both AZs can be used by your workloads. Either can be used for failover. You must have a minimum of six hosts in a stretched cluster, and you must deploy an even number of hosts.
    3. Enter a name for your SDDC.
      You can change this name later if you want to. See Rename an SDDC in the VMware Cloud on AWS Operations Guide.
    4. Select the host type.
      Option Description
      i3 (Local SSD) Provision hosts with a fixed amount of local SSD storage per host.
      R5 (EBS) Provision hosts with EBS-based storage. When provisioning R5 hosts, you can select the storage capacity per host. This allows you to provision greater capacity for workloads requiring large storage capacities.
      I3en (Local SSD) Provision hosts with a larger amount of local SSD storage per host. I3en hosts are currently only available with version 1.10v4 of the SDDC software, and are only available in some regions.
    5. If you selected R5 (EBS) hosts, select the storage capacity per host.
      The value you select is used for all hosts in the cluster, including any hosts you add to the cluster after creation.
    6. 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.

      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.
  4. (Optional) Select the size of the SDDC appliances.
    Medium is the default size for the NSX Edge and vCenter Server appliances. A Large appliance size is recommended for deployments with more than 50 hosts or 4000 VMs or in any other situation where management cluster resources might be oversubscribed.
    1. Click Show Advanced Configuration .
    2. Select the appliance size.
  5. Click Next to connect to an AWS account.
    See AWS VPC Configuration and Availability Requirements for important information about requirements for the AWS account and subnets you create in it.
    Option Description
    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.
    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.
  6. (Optional) Click NEXT to configure the Management Subnet in the SDDC.
    Enter an IP address range for the management subnet as a CIDR block or leave the text box blank to use the default, which is You can't change these values after the SDDC has been created, so consider the following when you specify the Management Subnet 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.
    • If you are deploying a single-host SDDC, the IP address range is reserved for the default compute gateway logical network of the SDDC. If you specify a management network address range that overlaps with, single-host SDDC creation fails. If you are deploying a multi-host SDDC, no compute gateway logical network is created during deployment, so you'll need to create one after the SDDC is deployed.

      Addresses in the range are reserved by VMware Cloud on AWS for internal use. (This is a subset of the range reserved for carrier-grade NAT per RFC 6598) You cannot access any remote (on-premises) networks in that address range from workloads in the SDDC, and you cannot you use any addresses in that range within the SDDC. In addition, CIDR blocks and 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, and must be in one of the "private address space" blocks defined by RFC 1918 (,, or The primary factor in choosing a Management CIDR block size is the anticipated scalability requirements of the SDDC. The management CIDR block cannot be changed after the SDDC has been deployed, so a /23 block is appropriate only for SDDCs that will not require much growth in capacity.
      CIDR block size Number of hosts (Single AZ) Number of hosts (Multi AZ)
      23 27 22
      20 251 246
      16 See VMware Configuration Maximums.
  7. 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

After your SDDC is created, do the following:

  • Configure a VPN connection to the management gateway.
  • For full-scale SDDCs, you must configure a logical segment for workload VM networking. Single host SDDCs have a default logical segment. A banner is displayed on the SDDC card after creation is complete to indicate whether you need to create a logical segment. See Create a Network Segment .
  • For single host SDDCs, a banner is displayed on the SDDC card to indicate that a default logical segment has been created for this SDDC. If this default segment causes a conflict, delete it and create a new segment. See Create a Network Segment.