跳至內容

Transit gateway & VPC peering - IP forwarding

0

A customer has the below set-up:

Branch Subnets----(Layer 2)----> Data Center Subnets ------(VPN Tunnel via AWS Transit Gateway)--------->Transit VPC(AWS)------(VPC Peering)-----> Citrix VPC(AWS)-----(VPC Peering)----> Prod VPC(AWS)

Some constraints:

  1. Prod VPC and Data Center Subnets have overlapping CIDRs as few servers have IP address affinity.
  2. Direct VPN connectivity between branches and Citrix VPC would not be possible immediately

Problem - They need to get printing working from Citrix VPC EC2 instances to the printers in Branches. What would be recommended implementation approach for IP forwarding for printing to work knowing the above constraints?

已提問 6 年前檢視次數 679 次

1 個回答
1
已接受的答案

A few observations:

  • Transitive Routing: As VPC Peering doesn't support transitive routing, the path from the Citrix VPC to the Transit VPC over VPC Peering cannot be used to establish connectivity. Unfortunately you comment that "2. Direct VPN connectivity between branches and Citrix VPC would not be possible immediately" rules out one solution approach. Instead you might want to look into connecting the Citrix VPC to the TGW to have a path between Citrix VPC and branches.
  • Overlapping CIDRs: You need to clarify what "Prod VPC and Data Center Subnets have overlapping CIDRs" means here. If a host in the Citrix VPC needs to talk to endpoints in the Prod VPC and Data Center Subnet under the same IP address, you'll need to look into NAT. If not, more specific routes might be sufficient.
AWS
專家

已回答 6 年前

專家

已審閱 2 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。