- 最新
- 最多得票
- 最多評論
This pattern is explained in the below whitepaper, see the second section 'How to use Private NAT gateway to provide approved IPs for on-premises network'
One way of connecting two VPCs with overlapping IP addresses together - and especially in this case where one VPC (A) only ever calls the other (D) - is PrivateLink. Well worth considering to eliminate all the other complexity.
For more information: https://aws.amazon.com/blogs/networking-and-content-delivery/connecting-networks-with-overlapping-ip-ranges/
this is an interesting idea!
My problem with this solution is Private Link will only help us connect to AWS Services or a network load balancer which doesn't make sense to implement if we only have a single fixed endpoint in 10.47.9.0/24
Consider VPC B & C are already connected with direct connect and the virtual private gateway
I've checked all the use cases from https://docs.aws.amazon.com/whitepapers/latest/aws-privatelink/use-case-examples.html
相關內容
- AWS 官方已更新 6 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
thankyou, but your solution assumes the transit gateway (TGW) is connected directly to the direct connect gateway (DCG), which it isn't.
In my setup, the DCG is directly connected to a virtual private gateway which is in turn connected to VPC B.
The problem I face if I try to modify my solution to the whitepaper you suggested are that it's not possible to connect TGW to DCG if it's already attached to a virtual private gateway (VPGW), if I disconnect the VPGW it won't accept that the DCG already has virtual interfaces configured.