Skip to navigationSkip to main contentSkip to footerScaleway Docs HomepageAsk our AI
Ask our AI
Log inSign up

Understanding transitive peering

InformationOutlineIcon
Note

VPC Peering is currently in Public Beta.

Overview

Scaleway VPC Peering natively supports transitive peering.

Transitive peering (or transitive routing) allows two VPCs that are not directly peered to exchange traffic through a third VPC that is peered with both. Traffic is forwarded through this intermediate network, making the connection transitive.

To enable transitivity, you must define custom routes in each VPC.

For example, if VPC A is peered with both VPC B and VPC C, you can route traffic between VPC B and VPC C through VPC A. To do so, define a custom route in VPC B directing traffic to VPC C via VPC A, and a corresponding route in VPC C directing traffic to VPC B via VPC A.

InformationOutlineIcon
Note

As routing complexity increases with each additional VPC in the transitivity chain, transitive peering is limited to four chained VPCs.

Examples

Simple peering connection

With two VPCs, there is no routing transitivity: a single VPC Peering connection is enough for VPC A to communicate with VPC B.

A graphic shows how two different VPCs each create a peering connector, which enables them to communicate over a peering connection.

Three peered VPCs without transitivity

With three chained VPCs, if you only add routes related to the next peer, then VPC A and B can communicate, and VPC B and C can communicate, but VPC A and C cannot.

A graphic shows how three different VPCs each create a peering connector, which enables them to communicate over a peering connection with neighboring VPCs, but not via a common VPC.

Three peered VPCs with transitivity

To enable VPC A and C to communicate with each other, you must add corresponding routes.

A graphic shows how three different VPCs each create a peering connector, which enables them to communicate over a peering connection with neighboring VPCs, and via a common VPC by adding corresponding custom routes.

Four peered VPCs without transitivity

With four chained VPCs, if you only add routes related to the next peer, then each VPC is only able to communicate with its immediate neighbors.

A graphic shows how four different VPCs each create a peering connector, which enables them to communicate over a peering connection with neighboring VPCs, but not via a common VPC.

Four peered VPCs with partial transitivity

To enable VPC A and D to communicate with each other, you must add corresponding routes. This also includes custom routes in VPC B and C, which must have a path to each extremity of the chain.

A graphic shows how four different VPCs each create a peering connector, which enables them to communicate over a peering connection with neighboring VPCs, and via a common VPC by adding corresponding custom routes.

Four peered VPCs with full transitivity

To enable full transitivity and allow any two VPCs of the chain to communicate, you must add additional routes to VPCs A and D.

A graphic shows how four different VPCs each create a peering connector, which enables them to communicate with any other VPC by adding custom routes to each VPC to enable full transitivity.
Still need help?

Create a support ticketArrowRightIcon
No Results