This website uses cookies to ensure you get the best experience.
Learn more.
VPC A is peered with VPC B, and VPC B is peered with VPC C. A workload in A cannot reach a private address in C even though administrators added routes pointing toward B. What explains the failure?
Published
- VPC peering is not transitive; A needs a supported direct or transit connectivity path to C.
- Adding more-specific routes in A always allows traffic to traverse any number of peered VPCs.
- VPC peering becomes transitive whenever every security group allows all outbound traffic.
- Enable DNS resolution on both peering connections and assume it creates transit routing through B.
Comments — 0
Sign in to comment