1 Answer
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
answered 8 months ago
Relevant questions
Access AWS Athena from lambda function in a VPC
asked 3 years agoAccess to AWS Opensearch in a VPC
Accepted Answerasked 5 months agoVPC Peering and DNS resolution of a public Amazon Redshift cluster
Accepted Answerasked 2 years agoAccessing S3 Gateway VPC Endpoint from another VPC (VPC Peering established between both source and destination VPCs)
Accepted Answerasked 2 years agoData transfer cost on VPC peering with different AWS accounts
Accepted Answerasked 2 years agoLambda in VPC can't access S3
asked 6 months agoHow to access OpenSearch from few different VPCs?
asked 8 months agoHow can I access resources in a peered VPC over site to site VPN?
Accepted Answerasked a month agoDo we need VPC Endpoints for SNS and SQS if data not originating from any VPC and directly landing in SNS from external source
asked 8 months agoAWS Client VPN - my systems are in different subnets that are in different VPCs
asked 8 months ago
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.