VPC Peering - Quickstart

Reviewed on February 10, 2026

Scaleway VPC Peering is a networking service that enables two Scaleway VPCs to establish a private peering connection. You can then securely route traffic between them, away from the public internet.

Open Image over content

For full details about VPC Peering, refer to Understanding VPC Peering.

Before you start

To complete the actions presented below, you must have:

• A Scaleway account logged into the console
• A VPC over which you have appropriate IAM permissions
• The unique VPC ID of the VPC you want to peer with
• Acivated routing on both VPC peers

1. Create a peering connector, defining your VPC as origin, and the VPC you want to peer with as target.

   Tip

   Both VPCs must be in the same Scaleway region. They may be in different Projects/Organizations. The target VPC must be identified by its unique VPC ID.

   The peering connector will be in Orphan status, until the next step is carried out.

2. An owner or manager of the target VPC must create a matching peering connector on their end, defining their VPC as origin and your VPC as target.

   Tip

   They will not receive any requests or notifications prompting them to create the matching connector. They must do this autonomously and independently.

3. Scaleway detects that two matching peering connectors have been created, and automatically carries out a compatibility check. This entails verifying that the Private Networks of the two VPCs do not contain any overlapping CIDR blocks.

   • If the two VPCs are compatible, both connectors go into Peered status, and the peering connection is created.
   • If the two VPCs have overlapping CIDR blocks, both connectors go into Conflict state. They cannot be peered until you resolve the conflict.

4. Create custom routes in the route table of each peered VPC, to establish rules for routing traffic for the IP ranges you specify, across the peering connection.

   Tip

   Creating custom routes is an essential step for facilitating the flow of traffic across the peering connection. Traffic will not be routed between the peered VPCs automatically or via any auto-created, managed routes.

5. When you no longer need your VPC peering connection, you and an owner of the matching connector can delete your connectors.