If traffic between your on-premises network and your SDDC requires higher speeds and lower latency than you can achieve with a connection over the public Internet, you can configure VMware Cloud on AWS to use AWS Direct Connect.

AWS Direct Connect (DX) provides a dedicated network connection between your on-premises network infrastructure and a virtual interface (VIF) your AWS VPC. DX supports two kinds of virtual interfaces:
  • A private VIF enables access to your AWS Virtual Private Cloud (VPC).
  • A public VIF enables access to services such as Amazon EC2 and S3.

Configure DX over a private VIF to carry workload and management traffic, including VPN and vMotion, between your on-premises data center and your connected VPC. Configure DX over a public VIF if you need to connect to AWS public endpoints such as EC2 and S3. You can route VPN traffic over either kind of VIF to provide additional data security.

Private and Public VIFs

A DX connection over a private VIF can be used for all traffic between your on-premises data center and your SDDC. It terminates in your connected Amazon VPC, provides a private IP address space, and uses BGP to advertise routes in your SDDC and learn routes in your on-premise data center.

A DX connection over a public VIF is typically used only for traffic between your on-premises data center and public AWS services, which you cannot access over a private VIF. It terminates at the AWS region level in the region occupied by your connected Amazon VPC, and uses BGP to advertise AWS global routes.