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
  1. VPC peering is not transitive; A needs a supported direct or transit connectivity path to C.
  2. Adding more-specific routes in A always allows traffic to traverse any number of peered VPCs.
  3. VPC peering becomes transitive whenever every security group allows all outbound traffic.
  4. Enable DNS resolution on both peering connections and assume it creates transit routing through B.

Comments — 0