1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
VPC Peering does not allow transitive routing. You can peer VPC B and C to A, this configuration does not allow VPC B to communicate to VPC C. For return traffic from VPC A to VPCs B and C you would need to configure specific routing, even down to the instance if need be. Take a look here for options and examples https://docs.aws.amazon.com/vpc/latest/peering/peering-configurations-partial-access.html
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
Thanks but that doesn't work in my case as VPC B and C have the same structure (same IP ranges associated to the subnets) and instances are running on ASG so I can't go too specific on the IP routing. And for simplicity I put only VPC B and C, but in reality I have around 30 VPCs that needs to connect to OpenSearch I found a solution on this link https://aws.amazon.com/blogs/networking-and-content-delivery/how-to-solve-private-ip-exhaustion-with-private-nat-solution/ but it's bit expensive to have a HA solution, as each VPC would required at least 2 extra NATs plus Transit Gateway.