- Mais recentes
- Mais votos
- Mais comentários
Yes, it is possible. See the option 3 in the below link. You can use a Transit Gateway (Transit VIF) along with DirectConnect Gateway, in this scenario you do not need VGW.
It is possible to connect your VPC to Direct Connect via the following methods:
- Virtual Private Gateway
- Direct Connect Gateway and Virtual Private Gateway
- Direct Connect Gateway and Transit Gateway This article provides information on how to pick which is best for your use case (including considering latency) - https://docs.aws.amazon.com/wellarchitected/latest/hybrid-networking-lens/performance-efficiency-pillar.html#:~:text=VPN%20connectivity%20options-,AWS%20Direct,-Connect%20options%20include References:
- Building a Scalable and Secure Multi-VPC AWS Network Infrastructure - https://docs.aws.amazon.com/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/direct-connect.html
- AWS DX – DXGW with AWS Transit Gateway, Multi-Regions, and AWS Public Peering - https://docs.aws.amazon.com/whitepapers/latest/hybrid-connectivity/aws-dx-dxgw-with-aws-transit-gateway-multi-regions-and-aws-public-peering.html
- Connect your network to AWS with hybrid connectivity solutions - https://www.youtube.com/watch?v=uq8C-DmrKXc
Hope this helps.
Thank you Carlos for these documentation references. I had read these before I posted my question. The documentation does not answer my question explicitly which is why I posted it.
Actually it does, As Tushar_J demonstrated in his answer to you which references the white paper - Building a Scalable and Secure Multi-VPC AWS Network Infrastructure - https://docs.aws.amazon.com/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/direct-connect.html Option #3 shows how this is possible. Glad you were able to get the answer you were looking for.
Conteúdo relevante
AWS OFICIALAtualizada há 2 anos- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há 2 anos
The reason why the VPC does not need a VGW in this scenario is because of the VPC "attachment" which connects the VPC to the Transit Gateway.
The attachment is an ENI placed in the VPC subnet which is mapped to the Transit Gateway.
Hyperplane provides the connectivity from the ENI in the VPC subnet to the Transit Gateway.
This diagram from the Transit Gateway guide shows the VPC attachment and no VGW: https://docs.aws.amazon.com/vpc/latest/tgw/how-transit-gateways-work.html
Transit Gateway uses Hyperplane https://docs.aws.amazon.com/whitepapers/latest/hybrid-connectivity/aws-hybrid-connectivity-services.html