- Newest
- Most votes
- Most comments
Only one Private VIF is needed per Direct Connect connection to access multiple VPCs (up to 20) through a Direct Connect Gateway (DXGW) using virtual private gateway associations. In other words, you only need to set up one single BGP session and one 802.1q VLAN tag.
The diagram you are referring to (option #2) is just an example showing two VPCs connected using a Private VIF and DXGW. Also worth mentioning that option #1 is not recommended. Go with option #2, which allows you to scale for the future.
When using AWS Direct Connect Gateway (DXGW) with Virtual Private Gateway (VGW) associations, you only need a single private Virtual Interface (VIF) to connect to multiple VPCs. This is one of the key advantages of using a Direct Connect Gateway.
With a Direct Connect Gateway, you can connect to up to 20 VPCs (via their associated VGWs) globally across any AWS account using just one private VIF. This is much more efficient than the direct VIF-to-VPC approach (Option 1), which requires one private VIF per VPC.
The Direct Connect Gateway acts as an aggregation point that allows a single private VIF to provide connectivity to multiple VPCs through their respective VGWs. There is only one BGP peering session per Direct Connect Gateway per Direct Connect connection.
You can have up to 30 private VIFs associated with the same AWS Direct Connect gateway, which means you could potentially connect multiple Direct Connect connections to the same DXGW for redundancy or increased bandwidth, each using its own private VIF.
So to directly answer your question: Only one private VIF is needed per Direct Connect connection to access multiple VPCs (up to 20) through a Direct Connect Gateway using virtual private gateway associations.
Sources
AWS Direct Connect - Building a Scalable and Secure Multi-VPC AWS Network Infrastructure
AWS DX – DXGW with VGW, Multi-Regions, and AWS Public Peering - Hybrid Connectivity
Traffic Segmentation Options in AWS Direct Connect - Traffic Segmentation Options in AWS Direct Connect
Relevant content
- asked 3 years ago
- asked 9 months ago
- AWS OFFICIALUpdated 2 years ago
Hi @Jeff, yes, thats a good callout, you can submit doc feedback using the "Provide feedback" hyperlink on that page.
Each orange line on the diagram is a private VIF, correct? If that is the case, shouldn't it be a single orange line from the customer / partner router across the cross connect to the direct connect gateway instead of two?
Edit: Corrected from "transit gateway" to "direct connect gateway"