Master AWS Direct Connect Gateway

What is the purpose of an AWS Direct Connect gateway?

How many Transit Gateways can be associated with an AWS Direct Connect gateway?

Can VPCs and Transit Gateways owned by any AWS account be associated with an AWS Direct Connect gateway owned by any AWS account?

How is traffic to and from the desired AWS Region routed when using an AWS Direct Connect gateway?

Are there any charges for using an AWS Direct Connect gateway?

Can private virtual interfaces and AWS Direct Connect gateways owned by different AWS accounts be associated with each other?

Which of the following networking features work with AWS Direct Connect gateway?

Can Provisioned private virtual interfaces be associated with an AWS Direct Connect gateway?

FAQs on AWS Direct Connect Gateway

An AWS Direct Connect gateway is necessary for connecting on-premises networks to multiple VPCs across different AWS Regions.
Up to three Transit Gateways can be associated with an AWS Direct Connect gateway, as long as the IP CIDR blocks don't overlap.
VPCs and Transit Gateways owned by any AWS account can be associated with an AWS Direct Connect gateway owned by any AWS account.
Traffic to and from the desired AWS Region takes the shortest path when using an AWS Direct Connect gateway, regardless of the associated home AWS Region.
There are no charges for using an AWS Direct Connect gateway, but applicable egress data charges and port hour charges apply.
Private virtual interfaces and AWS Direct Connect gateways, as well as transit virtual interfaces and AWS Direct Connect gateways, must be in the same AWS account.
Networking features like Elastic File System, Elastic Load Balancing, and Security Groups work with AWS Direct Connect gateway, but AWS VPN CloudHub functionality is not supported.
Provisioned private virtual interfaces can be associated with an AWS Direct Connect gateway if provisioned as private in the AWS account.
Intra-Region VPC connectivity is still available, and egress rate is charged for related geographic Regions.
Quotas for AWS Direct Connect gateway can be found on the AWS Direct Connect quotas page.
A virtual private gateway (VGW) associated with a VPC cannot be part of more than one AWS Direct Connect gateway, and one private virtual interface can only attach to one AWS Direct Connect gateway or one Virtual Private Gateway.
AWS Direct Connect gateway does not break existing AWS VPN CloudHub functionality, and supported and not supported traffic patterns can be found in the AWS Direct Connect User Guide.

Test your knowledge on AWS Direct Connect Gateway with our FAQs quiz. Learn about the key features, benefits, and limitations of this service, including how it enables on-premises networks to connect to multiple VPCs across different AWS Regions, how it works with Transit Gateways and virtual interfaces, and what networking features are supported. This quiz will help you understand the ins and outs of AWS Direct Connect Gateway and prepare you for using it effectively in your AWS environment.