scaleway · SamyOubouaziz · May 12, 2026 · May 11, 2026 · May 11, 2026 · May 11, 2026
@@ -35,4 +35,4 @@ The solution when two Private Networks have overlapping CIDR blocks is to:
 
 3. Attach the required resources to the new Private Network, where they will automatically be assigned new private IP addresses on the network by DHCP.
 
-Resources in the VPC should now all have unique private IP addresses. Traffic should be routed successfuly.
+Resources in the VPC should now all have unique private IP addresses. Traffic should be routed successfully.
@@ -8,14 +8,14 @@ dates:
 ---
 
 <Message type="note">
-VPC Peering is currently in Public Beta, and available only via the [Scaleway API](https://www.scaleway.com/en/developers/api/vpc/).
+VPC Peering is currently in Public Beta.
 </Message>
 
 ## CIDR block
 
 When you [create a Private Network](/vpc/how-to/create-private-network/), it gets two CIDR blocks (IPv4 and IPv6). As you attach resources to the Private Network, their private IP addresses will come from these blocks. [Read more about CIDR blocks](/vpc/concepts/#cidr-block).
 
-For two VPCs to be successfuly peered, none of the CIDR blocks attributed to their Private Networks may overlap. If an overlap is detected, the two peering connectors will show a `Conflict` state. As you cannot modify the CIDR block of a Private Network after creation, you must delete Private Networks as necessary and recreate them with different CIDR blocks. Only when no CIDR block overlap is detected, can the two VPCs be peered.
+For two VPCs to be successfully peered, none of the CIDR blocks assigned to their Private Networks may overlap. If an overlap is detected, the two peering connectors will show a `Conflict` status. As you cannot modify the CIDR block of a Private Network after creation, you must delete Private Networks as necessary and recreate them with different CIDR blocks. Only when no CIDR block overlap is detected, can the two VPCs be peered.
 
 ## Custom routes
 
@@ -43,7 +43,7 @@ A connection is established when managers of two [compatible](#cidr-block) VPCs
 
 ## Target VPC
 
-The VPC that is identified in a [peering connection](#peering-content) as the VPC to peer with. While the user creating the connector must have ownership or management rights over the [origin VPC](#origin-vpc), they do not need to have any rights over the target VPC. Peering will only be established when an owner or manager of the target VPC creates a matching connector, defining their own VPC as origin and the other VPC as target.
+The VPC that is identified in a [peering connection](#peering-connection) as the VPC to peer with. While the user creating the connector must have ownership or management rights over the [origin VPC](#origin-vpc), they do not need to have any rights over the target VPC. Peering will only be established when an owner or manager of the target VPC creates a matching connector, defining their own VPC as origin and the other VPC as target.
 
 ## Transitive peering
 

@@ -12,7 +12,7 @@ import peeringDiag from './assets/scaleway-vpc-peering-diag.webp'
 
 
 <Message type="note">
-VPC Peering is currently in Public Beta, and available only via the [Scaleway API](https://www.scaleway.com/en/developers/api/vpc/).
+VPC Peering is currently in Public Beta.
 </Message>
 
 ## Overview
@@ -77,7 +77,7 @@ Refer to the [dedicated documentation](/vpc-peering/reference-content/features-l
 
 ### How is VPC Peering billed?
 
-Billing does not start until two matching, compatible connectors are detected and enter a `Peered` state. Unmatched or uncompatible connectors in an `Orphan` or `Conflict` state are not billed.
+Billing does not start until two matching, compatible connectors are detected and enter a `Peered` status. Unmatched or incompatible connectors in an `Orphan` or `Conflict` status are not billed.
 
 Once billing begins, each peered connector is billed at a fixed hourly rate. The cost of the peering is therefore 'split' between both sides. Traffic is unlimited: no caps or rate-limits apply.
 

@@ -0,0 +1,38 @@
+---
+title: How to create a VPC Peering connector
+description: Find out how to create a VPC Peering connector, and start connecting VPCs to deploy secure network topologies across one or several Organizations.
+tags: vpc peering connector connect pair peer secure private networks
+dates:
+  validation: 2026-05-11
+  posted: 2026-05-11
+---
+
+import Requirements from '@macros/iam/requirements.mdx'
+
+This page explains how to create a peering connector using the [Scaleway console](https://console.scaleway.com/).
+
+<Requirements />
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- [Created a VPC](/vpc/how-to/create-vpc)
+- The unique VPC ID of the VPC you want to peer with
+- [Activated routing](/vpc/how-to/manage-routing/#how-to-activate-routing) on both VPC peers
+
+1. Click **VPC Peering** in the **Network** section of the [Scaleway console](https://console.scaleway.com/organization) side menu.
+
+2. Click **+ Create a peering connector**. The peering connector creation wizard displays.
+
+3. Choose a region in which to create your peering connector.
+
+4. Select an origin VPC from the current Scaleway Project using the drop-down menu.
+
+5. Enter the ID of the target VPC you want to peer with. The target VPC can be in a different Project/Organization.
+
+6. Enter a **name** for your connector, or use the automatically-generated one. Optionally, you can also add **tags** to help organize your resources. Each tag should be separated by a space.
+
+7. Click **Create a peering connector** to finish.
+
+Your new peering connector will be in an `Orphan` status until an owner or manager of the target VPC creates a matching peering connector on their end, defining their VPC as origin, and your VPC as target. 
+
+Once the two matching connectors are created, you must [create custom routes](/vpc-peering/how-to/manage-routing/) in each peered VPC to allow traffic between them.
@@ -0,0 +1,27 @@
+---
+title: How to delete a VPC Peering connector
+description: Find out how to delete a VPC Peering connector using the Scaleway Console.
+tags: vpc peering connector connect pair peer secure private networks
+dates:
+  validation: 2026-05-11
+  posted: 2026-05-11
+---
+import Requirements from '@macros/iam/requirements.mdx'
+
+Deleting a peering connector immediately terminates the connection between the peered VPCs and leaves the matching connector on the target VPC as `Orphan`.
+
+<Requirements />
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- [Created a peering connector](/vpc-peering/how-to/create-peering-connector/)
+
+## How to delete a peering connector
+
+1. Click **VPC Peering** in the **Network** section of the [Scaleway console](https://console.scaleway.com/organization) side menu. A listing of your peering connectors displays.
+
+2. Use the **region selector** at the top of the page to filter for the region of the peering connector you want to delete.
+
+3. Click <Icon name="more" /> next to the peering connector you want to delete, and select **Delete** from the drop-down menu.
+
+3. Type **DELETE** in the box to confirm, then click **Confirm**.
@@ -0,0 +1,4 @@
+---
+title: VPC Peering - How-tos
+description: VPC Peering - How-tos
+---
@@ -0,0 +1,29 @@
+---
+title: How to manage a VPC Peering connector
+description: Find out how to manage a VPC Peering connector using the Scaleway console.
+tags: vpc peering connector connect pair peer secure private networks
+dates:
+  validation: 2026-05-11
+  posted: 2026-05-11
+---
+
+import Requirements from '@macros/iam/requirements.mdx'
+
+This page explains how to manage a peering connector using the [Scaleway console](https://console.scaleway.com/).
+
+<Requirements />
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- [Created a peering connector](/vpc-peering/how-to/create-peering-connector/)
+
+1. Click **VPC Peering** in the **Network** section of the [Scaleway console](https://console.scaleway.com/organization) side menu. A list of your peering connectors displays.
+
+2. Click the name of the peering connector you want to manage. Its **Overview** tab displays.
+
+From here, you can see the information on your connector, its origin VPC, and its target VPC.
+
+<Message type="note">
+To manage routing for your peering connector, refer to the [dedicated documentation](/vpc-peering/how-to/manage-routing/). 
+</Message>
+
@@ -0,0 +1,38 @@
+---
+title: How to manage routing for VPC Peering
+description: Find out how to manage a VPC Peering connector using the Scaleway console.
+tags: vpc peering connector connect pair peer secure private networks
+dates:
+  validation: 2026-05-11
+  posted: 2026-05-11
+---
+
+This page explains how to manage routing for a VPC Peering connector using the [Scaleway console](https://console.scaleway.com/). 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.
+
+1. Click **VPC** in the **Network** section of the Scaleway console side menu. A list of your VPCs displays.
+
+2. 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.
+
+3. Click the **Routing** tab.
+
+4. Click **Create route**. The custom route creation wizard displays.
+
+5. Enter a **description** for your route, e.g. "Route to VPC B".
+
+6. Optionally, enter one or more **tags** for your route. Tags help you filter and organize your list of routes.
+
+7. 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 `/32` mask for IPv4.
+
+    <Message type="note">
+    If you enter a destination of `0.0.0.0/0`, all packets not destined for a local Private Network will be sent through the peering connector.
+    </Message>
+
+8. 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.
+
+9. 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.
@@ -7,7 +7,7 @@ description: Explore Scaleway VPC Peering. Establish a peering connection betwee
   type="note"
   title="VPC Peering is in Public Beta"
 >
-  VPC Peering is currently in Public Beta, and available only via the [Scaleway API](https://www.scaleway.com/en/developers/api/vpc/).
+  VPC Peering is currently in Public Beta.
 </Message>
 
 

@@ -16,6 +16,28 @@ export const vpcPeeringMenu = {
       label: 'FAQ',
       slug: 'faq',
     },
+    {
+      items: [
+        {
+          label: 'Create a peering connector',
+          slug: 'create-peering-connector',
+        },
+        {
+          label: 'Manage a peering connector',
+          slug: 'manage-peering-connector',
+        },
+        {
+          label: 'Manage routing',
+          slug: 'manage-routing',
+        },
+        {
+          label: 'Delete a peering connector',
+          slug: 'delete-peering-connector',
+        },
+      ],
+      label: 'How to',
+      slug: 'how-to',
+    },
     {
       items: [
         {

@@ -3,14 +3,14 @@ title: VPC Peering - Quickstart
 description: Get started quickly with Scaleway VPC Peering. Follow our step-by-step guide to configure and deploy a secure connection between your two Scaleway VPCs in minutes.
 tags: vpc-peering, networking, private-connection, secure-connectivity, cross-project, cross-organization, custom-routes
 dates:
-  creation: 2026-02-10
-  validation: 2026-02-10
+  creation: 2026-05-12
+  validation: 2026-05-12
 ---
 
 import peeringDiag from './assets/scaleway-vpc-peering-diag.webp'
 
 <Message type="note">
-VPC Peering is currently in Public Beta, and available only via the Scaleway API. For specific API calls, read refer to the [VPC Peering API documentation](https://www.scaleway.com/en/developers/api/vpc/). 
+VPC Peering is currently in Public Beta. 
 </Message>
 
 import Requirements from '@macros/iam/requirements.mdx'
@@ -24,34 +24,76 @@ For full details about VPC Peering, refer to [Understanding VPC Peering](/vpc-pe
 <Requirements />
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
-- [A VPC](/vpc/how-to/create-vpc) over which you have appropriate [IAM permissions](/iam/reference-content/permission-sets/)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- [Created a VPC](/vpc/how-to/create-vpc)
 - The unique VPC ID of the VPC you want to peer with
 - [Activated routing](/vpc/how-to/manage-routing/#how-to-activate-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.
+## How to create a peering connector
+
+1. Click **VPC Peering** in the **Network** section of the [Scaleway console](https://console.scaleway.com/organization) side menu.
+
+2. Click **+ Create a peering connector**. The peering connector creation wizard displays.
+
+3. Choose a region in which to create your peering connector.
+
+4. Select an origin VPC from the current Scaleway Project using the drop-down menu.
+
+5. Enter the ID of the target VPC you want to peer with. The target VPC can be in a different Project/Organization.
+
+6. Enter a **name** for your connector, or use the automatically-generated one. Optionally, you can also add **tags** to help organize your resources. Each tag should be separated by a space.
+
+7. Click **Create a peering connector** to finish.
 
         <Message type="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.
         </Message>
 
         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.
+8. 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.
 
         <Message type="tip">
         They will not receive any requests or notifications prompting them to create the matching connector. They must do this autonomously and independently.
         </Message>
 
-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.
+9. Scaleway detects that two matching peering connectors have been created, and automatically carries out a compatibility check to ensure 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](/vpc-peering/troubleshooting/resolving-peering-conflicts/).
+        - If the two VPCs have overlapping CIDR blocks, both connectors go into `Conflict` status. They cannot be peered until you [resolve the conflict](/vpc-peering/troubleshooting/resolving-peering-conflicts/).
 
-4. [Create custom routes](https://www.scaleway.com/en/developers/api/vpc/#path-routes-create-a-route) in the route table of each peered VPC, to establish rules for routing traffic for the IP ranges you specify, across the peering connection.
+## How to create custom routes
 
-        <Message type="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.
-        </Message>
+Once both connectors are in a `Peered` status, you must add custom routes to the route table of each peered VPC to establish rules for routing traffic for the IP ranges you specify, across the peering connection.
+
+<Message type="note">
+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.
+</Message>
+
+1. Click **VPC** in the **Network** section of the Scaleway console side menu. A list of your VPCs displays.
+
+2. 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.
+
+3. Click the **Routing** tab.
+
+4. Click **Create route**. The custom route creation wizard displays.
+
+5. Enter a **description** for your route, e.g. "Route to peered VPC".
+
+6. 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`.
+
+7. 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.
+
+8. 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.
+
+## How to delete a peering connector
+
+1. Click **VPC Peering** in the **Network** section of the [Scaleway console](https://console.scaleway.com/organization) side menu. A listing of your peering connectors displays.
+
+2. Use the **region selector** at the top of the page to filter for the region of the peering connector you want to delete.
 
-5. When you no longer need your VPC peering connection, you and an owner of the matching connector can delete your connectors. 
+3. Click <Icon name="more" /> next to the peering connector you want to delete, and select **Delete** from the drop-down menu.
 
+4. Type **DELETE** in the box to confirm, then click **Confirm**.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -35,4 +35,4 @@ The solution when two Private Networks have overlapping CIDR blocks is to:

		3. Attach the required resources to the new Private Network, where they will automatically be assigned new private IP addresses on the network by DHCP.

		Resources in the VPC should now all have unique private IP addresses. Traffic should be routed successfuly.
		Resources in the VPC should now all have unique private IP addresses. Traffic should be routed successfully.