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.

Procedure

  1. Log in to the VMC Console at https://vmc.vmware.com.
  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 60 days. For more information, see Deploying a Single Host SDDC Starter Configuration.
      Multi-Host

      Select this option to create an SDDC with two or more hosts.

      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 need a minimum of four hosts (two in each AZ) to create a stretched cluster. Hosts must be added in pairs.

    3. Select the host type.
      Currently available host types are i3 and i3en. For more information on host types, see VMC on AWS Host Types.
    4. 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.
    5. 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.
  4. (Optional) Select the size of the SDDC appliances.

    By default, a new SDDC is created with medium-sized NSX Edge and vCenter Server appliances. Large-sized appliances are recommended for deployments with more than 30 hosts or 3000 VMs or in any other situation where management cluster resources might be oversubscribed. Large-sized appliances are also required if you want to Configure a Multi-Edge SDDC With Traffic Groups.

    To deploy the SDDC with large appliances, click Show Advanced Configuration and select Large from the drop-down control.

    If you create the SDDC with a medium appliance configuration and find that you need additional management cluster resources, you can upsize the configuration to large. See Upsize SDDC Management Appliances.

  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. Select a VPC and Subnet from the drop-down menu and click Next.
  7. (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 10.2.0.0/16. 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. For a complete list of IPv4 addresses reserved by VMware Cloud on AWS, see Reserved Network Addresses in the VMware Cloud on AWS Networking and Security guide.
    • If you are deploying a single-host SDDC, the IP address range 192.168.1.0/24 is reserved for the default compute network of the SDDC. If you specify a management network address range that overlaps that address, 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.
    • 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 (10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16). 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.
      Note:

      Because VMware Cloud on AWS reserves the capacity to add hosts (and their IP addresses) to every SDDC to meet SLA requirements during maintenance operations or in case of host failure, the number of usable hosts is reduced from what's shown here by two per SDDC, plus one more per cluster. This means that, for example, an SDDC with two clusters and a /23 management CIDR has enough IP addresses to deploy up to 23 hosts. The remaining addresses are reserved to be used when needed by hosts deployed to meet SLA requirements.

  8. 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.