How to manage routing for VPC Peering
This page explains how to manage routing for a VPC Peering connector using the Scaleway console. To allow traffic through a peering connector, you must create a custom route in each of the two peered VPCs. Each route's destination must be a subnet containing the IP addresses of the resources in the opposite VPC that need to communicate through the connector.
How to create a custom route
Each VPC has auto-generated, managed routes to local subnets and Public Gateways, but you can also create your own custom routes.
-
Click VPC in the Network section of the Scaleway console side menu. A list of your VPCs displays.
-
Use the region selector at the top of the page to filter for the region of the VPC where you want to define a custom route, then click the VPC. A list of Private Networks in this VPC displays.
-
Click the Routing tab.
-
Click Create route. The custom route creation wizard displays.
-
Enter a description for your route, e.g. "Route to VPC B".
-
Optionally, enter one or more tags for your route. Tags help you filter and organize your list of routes.
-
Enter a destination for the route. The VPC will apply the route to all traffic with a matching destination IP. You must enter an IPv4 or IPv6 CIDR range with a subnet mask, e.g.
192.168.1.0/24. For a single IP address, use the/32mask for IPv4. -
Choose Peering connector as the next hop for the route, then select the desired peering connector from the drop-down list. The VPC will route traffic for the destination IP to the selected entry.
-
Click Create route to finish.
Your new route now displays in the Routing tab of your VPC. A matching custom route must be added to the target VPC for traffic to flow between the peered VPCs. The destination of that return route must be a subnet that contains the IP address(es) of the resources in the origin VPC that need to reach the peered side.