Skip to main content
NetApp Solutions

Deploy and configure the Virtualization Environment on AWS

Contributors kevin-hoke reno
PDFs

As with on-premises, planning VMware Cloud on AWS is critical for a successful production-ready environment for creating VMs and migration.

This section describes how to set up and manage VMware Cloud on AWS SDDC and use it in combination with the available options for connecting NetApp storage.

Note In-guest storage is currently the only supported method of connecting Cloud Volumes ONTAP (CVO) to AWS VMC.

The setup process can be broken down into the following steps:

Deploy and configure VMware Cloud for AWS

VMware Cloud on AWS provides for a cloud native experience for VMware based workloads in the AWS ecosystem. Each VMware Software-Defined Data Center (SDDC) runs in an Amazon Virtual Private Cloud (VPC) and provides a full VMware stack (including vCenter Server), NSX-T software-defined networking, vSAN software-defined storage, and one or more ESXi hosts that provide compute and storage resources to your workloads.

This section describes how to set up and manage VMware Cloud on AWS and use it in combination with Amazon FSx ONTAP and/or Cloud Volumes ONTAP on AWS with in-guest storage.

Note In-guest storage is currently the only supported method of connecting Cloud Volumes ONTAP (CVO) to AWS VMC.

The setup process can be broken down into three parts:

Register for an AWS Account

Register for an Amazon Web Services Account.

You need an AWS account to get started, assuming there isn’t one created already. New or existing, you need administrative privileges in the account for many steps in this procedure. See this link for more information regarding AWS credentials.

Register for a My VMware Account

Register for a My VMware account.

For access to VMware’s cloud portfolio (including VMware Cloud on AWS), you need a VMware customer account or a My VMware account. If you have not already done so, create a VMware account here.

Provision SDDC in VMware Cloud

After the VMware account is configured and proper sizing is performed, deploying a Software-Defined Data Center is the obvious next step for using the VMware Cloud on AWS service. 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 into the VMware Cloud Console using your existing or newly created VMware credentials.

    Figure showing input/output dialog or representing written content

  2. Configure the AWS region, deployment, and host type and the SDDC name:

    Figure showing input/output dialog or representing written content

  3. Connect to the desired AWS account and execute the AWS Cloud Formation stack.

    Figure showing input/output dialog or representing written content
    Figure showing input/output dialog or representing written content
    Figure showing input/output dialog or representing written content
    Figure showing input/output dialog or representing written content

    Note Single-host configuration is used in this validation.

  4. Select the desired AWS VPC to connect the VMC environment with.

    Figure showing input/output dialog or representing written content

  5. Configure the VMC Management Subnet; this subnet contains VMC-managed services like vCenter, NSX, and so on. Do not choose an overlapping address space with any other networks that need connectivity to the SDDC environment. Finally, follow the recommendations for CIDR size notated below.

    Figure showing input/output dialog or representing written content

  6. Review and acknowledge the SDDC configuration, and then click deploy the SDDC.

    Figure showing input/output dialog or representing written content

    The deployment process typically takes approximately two hours to complete.

    Figure showing input/output dialog or representing written content

  7. After completion, the SDDC is ready for use.

    Figure showing input/output dialog or representing written content

For a step-by-step guide on SDDC deployment, see Deploy an SDDC from the VMC Console.

Connect VMware Cloud to FSx ONTAP

To connect VMware Cloud to FSx ONTAP, complete the following steps:

  1. With VMware Cloud deployment completed and connected to AWS VPC, you must deploy Amazon FSx ONTAP into a new VPC rather than the original connected VPC (see the screenshot below). FSx (NFS and SMB floating IPs) is not accessible if it is deployed in the connected VPC. Keep in mind that ISCSI endpoints like Cloud Volumes ONTAP work just fine from the connected VPC.

    Figure showing input/output dialog or representing written content

  2. Deploy an additional VPC in the same region, and then deploy Amazon FSx ONTAP into the new VPC.

    Configuration of an SDDC group in the VMware Cloud console enables the networking configuration options required to connect to the new VPC where FSx is deployed. In step 3, verify that “Configuring VMware Transit Connect for your group will incur charges per attachment and data transfers” is checked, and then choose Create Group. The process can take a few minutes to complete.

    Figure showing input/output dialog or representing written content
    Figure showing input/output dialog or representing written content
    Figure showing input/output dialog or representing written content

  3. Attach the newly created VPC to the just created SDDC group. Select the External VPC tab and follow the instructions for attaching an External VPC to the group. This process can take 10 to 15 minutes to complete.

    Figure showing input/output dialog or representing written content
    Figure showing input/output dialog or representing written content

  4. As part of the external VPC process, you are prompted through the AWS console to a new shared resource via the Resource Access Manager. The shared resource is the AWS Transit Gateway managed by VMware Transit Connect.

    Figure showing input/output dialog or representing written content
    Figure showing input/output dialog or representing written content

  5. Create the Transit Gateway Attachment.

    Figure showing input/output dialog or representing written content

  6. Back on the VMC Console, Accept the VPC attachment. This process can take approximately 10 minutes to complete.

    Figure showing input/output dialog or representing written content

  7. While in the External VPC tab, click the edit icon in the Routes column and add in the following required routes:

    • A route for the floating IP range for Amazon FSx ONTAP floating IPs.

    • A route for the floating IP range for Cloud Volumes ONTAP (if applicable).

    • A route for the newly created external VPC address space.

      Figure showing input/output dialog or representing written content

  8. Finally, allow bidirectional traffic firewall rules for access to FSx/CVO. Follow these detailed steps for compute gateway firewall rules for SDDC workload connectivity.

    Figure showing input/output dialog or representing written content

  9. After the firewall groups are configured for both the Management and Compute gateway, the vCenter can be accessed as follows:

    Figure showing input/output dialog or representing written content

The next step is to verify that Amazon FSx ONTAP or Cloud Volumes ONTAP is configured depending on your requirements and that the volumes are provisioned to offload storage components from vSAN to optimize the deployment.