reference deployment

VMware SD-WAN on AWS

Software-based WAN to connect on-premises networks and VPCs

View deployment guide

This Quick Start deploys VMware SD-WAN on the Amazon Web Services (AWS) Cloud. It is for organizations that want software-defined wide area network (WAN) connections between on-premises data centers, branch offices, and workloads on AWS.

This Quick Start deploys a high-availability cluster of VMware SD-WAN Virtual Edge (vEdge) appliances to Amazon Elastic Compute Cloud (Amazon EC2) instances. AWS Cloud WAN provides network segmentation and connectivity to customer workloads in AWS virtual private clouds (VPCs). VMware SD-WAN Orchestrator provides a single pane of glass for monitoring, reporting, and managing the vEdge appliances.

VMWare logo

This Quick Start was developed by VMware in collaboration with AWS. VMware is an AWS Partner.

  •  What you'll build

  • The Quick Start sets up the following:

    • A highly available architecture that spans two Availability Zones.
    • A VPC configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS. This VPC serves as a transit VPC connecting branch-office network VMware SD-WAN Edges with workload VPCs.
    • An internet gateway that allows the transit VPC to connect to the internet.
    • In the public subnets, a VMware SD-WAN vEdge cluster deployed to Amazon EC2 instances. The VMware SD-WAN vEdge instances provide full-mesh VPN attachments to the AWS Cloud WAN core network edge.
    • An AWS Cloud WAN core network edge for connecting workload VPCs to the transit VPC. This contains two segment networks, or isolated routing domains, to which workload VPCs attach.
    • AWS Lambda to make API calls during deployment to configure VMware SD-WAN Orchestrator.
    • Amazon CloudWatch for storing the AWS Lambda function logs.
    • AWS Secrets Manager for securely storing VMware SD-WAN Orchestrator credentials.
  •  How to deploy

  • To deploy this Quick Start, follow the instructions in the deployment guide, which includes these steps. The stack takes about 15 minutes to launch.

    1. Sign in to your AWS account. If you don't have an account, sign up at https://aws.amazon.com.
    2. Subscribe to the Amazon Machine Image (AMI) for VMware SD-WAN by VeloCloud Virtual Edge in AWS Marketplace.
    3. Create a VMware SD-WAN administrator account, hub profile, and segments.
    4. Launch the Quick Start. Before you create the stack, choose the AWS Region from the top toolbar.
    5. Complete postdeployment steps, which include adding static routes to the route tables of your workload VPCs.

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on this solution.  

    View deployment guide for details
  •  Cost and licenses

  • The Quick Start requires the following:

    • A subscription to the Amazon Machine Image (AMI) for VMware SD-WAN by VeloCloud Virtual Edge, which is available from AWS Marketplace. 
    • A VMware SD-WAN license, available from your VMware sales associate or reseller. For more information, refer to https://sase.vmware.com/. Additional pricing, terms, and conditions may apply.

    You are responsible for the cost of the AWS services and any third-party licenses used while running this Quick Start reference deployment. There is no additional cost for using this Quick Start.

    The AWS CloudFormation templates for this Quick Start include configuration parameters that you can customize. Some of these settings, such as instance type, affect the cost of deployment. For cost estimates, refer to the pricing pages for each AWS service you use. Prices are subject to change.

    Tip: After you deploy the Quick Start, create AWS Cost and Usage Reports to track costs associated with the Quick Start. These reports deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. They provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information about the report, refer to What are AWS Cost and Usage Reports?