diff --git a/pages/ipam/troubleshooting/conflicting-private-ips.mdx b/pages/ipam/troubleshooting/conflicting-private-ips.mdx index b4e7131675..23a186d855 100644 --- a/pages/ipam/troubleshooting/conflicting-private-ips.mdx +++ b/pages/ipam/troubleshooting/conflicting-private-ips.mdx @@ -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. \ No newline at end of file +Resources in the VPC should now all have unique private IP addresses. Traffic should be routed successfully. \ No newline at end of file diff --git a/pages/vpc-peering/concepts.mdx b/pages/vpc-peering/concepts.mdx index 3c43e0b742..de872d427a 100644 --- a/pages/vpc-peering/concepts.mdx +++ b/pages/vpc-peering/concepts.mdx @@ -8,14 +8,14 @@ dates: --- -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. ## 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 diff --git a/pages/vpc-peering/faq.mdx b/pages/vpc-peering/faq.mdx index 10576849f3..281f00ff7b 100644 --- a/pages/vpc-peering/faq.mdx +++ b/pages/vpc-peering/faq.mdx @@ -12,7 +12,7 @@ import peeringDiag from './assets/scaleway-vpc-peering-diag.webp' -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. ## 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. diff --git a/pages/vpc-peering/how-to/create-peering-connector.mdx b/pages/vpc-peering/how-to/create-peering-connector.mdx new file mode 100644 index 0000000000..a3d58fe1a5 --- /dev/null +++ b/pages/vpc-peering/how-to/create-peering-connector.mdx @@ -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/). + + + +- 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. \ No newline at end of file diff --git a/pages/vpc-peering/how-to/delete-peering-connector.mdx b/pages/vpc-peering/how-to/delete-peering-connector.mdx new file mode 100644 index 0000000000..58a2be696c --- /dev/null +++ b/pages/vpc-peering/how-to/delete-peering-connector.mdx @@ -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`. + + + +- 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 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**. diff --git a/pages/vpc-peering/how-to/index.mdx b/pages/vpc-peering/how-to/index.mdx new file mode 100644 index 0000000000..1437304d03 --- /dev/null +++ b/pages/vpc-peering/how-to/index.mdx @@ -0,0 +1,4 @@ +--- +title: VPC Peering - How-tos +description: VPC Peering - How-tos +--- \ No newline at end of file diff --git a/pages/vpc-peering/how-to/manage-peering-connector.mdx b/pages/vpc-peering/how-to/manage-peering-connector.mdx new file mode 100644 index 0000000000..f8772f9256 --- /dev/null +++ b/pages/vpc-peering/how-to/manage-peering-connector.mdx @@ -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/). + + + +- 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. + + +To manage routing for your peering connector, refer to the [dedicated documentation](/vpc-peering/how-to/manage-routing/). + + diff --git a/pages/vpc-peering/how-to/manage-routing.mdx b/pages/vpc-peering/how-to/manage-routing.mdx new file mode 100644 index 0000000000..521288c22a --- /dev/null +++ b/pages/vpc-peering/how-to/manage-routing.mdx @@ -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. + + + 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. + + +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. \ No newline at end of file diff --git a/pages/vpc-peering/index.mdx b/pages/vpc-peering/index.mdx index 868bf25e47..953995b6d6 100644 --- a/pages/vpc-peering/index.mdx +++ b/pages/vpc-peering/index.mdx @@ -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. diff --git a/pages/vpc-peering/menu.ts b/pages/vpc-peering/menu.ts index 7477f1ecb9..9bd9104d10 100644 --- a/pages/vpc-peering/menu.ts +++ b/pages/vpc-peering/menu.ts @@ -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: [ { diff --git a/pages/vpc-peering/quickstart.mdx b/pages/vpc-peering/quickstart.mdx index bb91111a2b..bf7d4609d3 100644 --- a/pages/vpc-peering/quickstart.mdx +++ b/pages/vpc-peering/quickstart.mdx @@ -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' -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. import Requirements from '@macros/iam/requirements.mdx' @@ -24,11 +24,26 @@ For full details about VPC Peering, refer to [Understanding VPC Peering](/vpc-pe - 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. 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. @@ -36,22 +51,49 @@ For full details about VPC Peering, refer to [Understanding VPC Peering](/vpc-pe 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. 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. +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 - - 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. - +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. + + +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. + + +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 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**. diff --git a/pages/vpc-peering/reference-content/features-limitations.mdx b/pages/vpc-peering/reference-content/features-limitations.mdx index 732cf2489e..0043434d7d 100644 --- a/pages/vpc-peering/reference-content/features-limitations.mdx +++ b/pages/vpc-peering/reference-content/features-limitations.mdx @@ -8,7 +8,7 @@ dates: --- -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. This page lists the different features and limitations of Scaleway VPC Peering. @@ -21,7 +21,7 @@ VPC Peering lets you connect any two Scaleway VPCs, whether they belong to the s ### Mutual consent security model -Peering connections are always mutually consented. An owner or manager of each VPC must independently create a [peering connector](/vpc-peering/concepts/#peering-connector) towards the other. If only one side creates a connector, it remains in an `Orphan` state and no connection is established. No requests or notifications are sent between Organizations. +Peering connections are always mutually consented. An owner or manager of each VPC must independently create a [peering connector](/vpc-peering/concepts/#peering-connector) toward the other. If only one side creates a connector, it remains in an `Orphan` status and no connection is established. No requests or notifications are sent between Organizations. ### Fine-grained traffic control via custom routes @@ -43,7 +43,7 @@ Two VPCs can only be peered if they are located in the same Scaleway region. Cro ### No overlapping CIDR blocks -For peering to be established, none of the CIDR blocks attributed to Private Networks in one VPC may overlap with those in the other VPC. If an overlap is detected, both connectors enter a `Conflict` state. Since CIDR blocks cannot be modified after a Private Network is created, conflicting Private Networks must be deleted and recreated with non-overlapping CIDR ranges. See our [troubleshooting guide](/vpc-peering/troubleshooting/resolving-peering-conflicts/) for more details. +For peering to be established, none of the CIDR blocks attributed to Private Networks in one VPC may overlap with those in the other VPC. If an overlap is detected, both connectors enter a `Conflict` status. Since CIDR blocks cannot be modified after a Private Network is created, conflicting Private Networks must be deleted and recreated with non-overlapping CIDR ranges. See our [troubleshooting guide](/vpc-peering/troubleshooting/resolving-peering-conflicts/) for more details. ### Custom routes are not created automatically diff --git a/pages/vpc-peering/reference-content/index.mdx b/pages/vpc-peering/reference-content/index.mdx new file mode 100644 index 0000000000..9e3f168ac5 --- /dev/null +++ b/pages/vpc-peering/reference-content/index.mdx @@ -0,0 +1,5 @@ +--- +title: VPC Peering - Additional content +description: VPC Peering - Additional content +--- + diff --git a/pages/vpc-peering/reference-content/statuses.mdx b/pages/vpc-peering/reference-content/statuses.mdx index 7059e26148..2ad5c8b284 100644 --- a/pages/vpc-peering/reference-content/statuses.mdx +++ b/pages/vpc-peering/reference-content/statuses.mdx @@ -8,7 +8,7 @@ dates: --- -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. ## VPC Peering connector statuses @@ -19,7 +19,7 @@ This section explains the different statuses possible for a peering connector, a | **Status** | **Description** | |------------------------|-----------------------------------------| -| **Pending/Configuring** | The connector is configuring and is in a transient state. No user actions can be carried out. This status generally occurs after a new configuration is being applied, or you have just created a connector. This status should be momentary; if it persists, contact our support. | +| **Pending/Configuring** | The connector is configuring and is in a transient status. No user actions can be carried out. This status generally occurs after a new configuration is being applied, or you have just created a connector. This status should be momentary; if it persists, contact our support. | | **Orphan** | The connector has been created, but no matching connector has been created for the target VPC. There is no VPC peering connection between the two VPCs. An owner or manager of the target VPC must create a matching connector, where their VPC is defined as origin and yours is defined as target. | | **Peered** | This connector has matched with a compatible connector for the target VPC, and a peering connection is established between the two VPCs. | | **Conflict** | This connector has matched with a connector for the target VPC, but the two VPCs contain Private Networks with overlapping CIDR ranges. No VPC peering connection can be established until the [conflict is resolved](/vpc-peering/troubleshooting/resolving-peering-conflicts/). | diff --git a/pages/vpc-peering/reference-content/understanding-vpc-peering.mdx b/pages/vpc-peering/reference-content/understanding-vpc-peering.mdx index 9a8a893b83..b608935850 100644 --- a/pages/vpc-peering/reference-content/understanding-vpc-peering.mdx +++ b/pages/vpc-peering/reference-content/understanding-vpc-peering.mdx @@ -10,7 +10,7 @@ dates: import peeringDiag from './assets/scaleway-vpc-peering-diag.webp' -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. @@ -34,7 +34,7 @@ The system is designed to protect privacy and avoid information leakage: when cr ### Use custom routes to route traffic -Once two VPCs are peered, you must create [custom routes](/vpc/how-to/manage-routing/#how-to-create-a-custom-route) to enable traffic to flow across the peering connection. These routes are not managed by Scaleway, and are not created automatically. Creating custom routes lets you precisely control the traffic flow between the peered VPCs, by defining specific destination IP ranges that should be routed through the peering connection. This gives you full flexiblity to implement your desired network topology and segmentation policies. +Once two VPCs are peered, you must create [custom routes](/vpc/how-to/manage-routing/#how-to-create-a-custom-route) to enable traffic to flow across the peering connection. These routes are not managed by Scaleway, and are not created automatically. Creating custom routes lets you precisely control the traffic flow between the peered VPCs, by defining specific destination IP ranges that should be routed through the peering connection. This gives you full flexibility to implement your desired network topology and segmentation policies. Each side of the peering connection must independently create their own custom routes in their VPC's route table - these are not shared automatically between the peered VPCs. @@ -84,7 +84,7 @@ VPC Peering connectors are a regional resource, and are available in multiple re ## Pricing -Billing for VPC Peering does not start until two matching, compatible connectors are detected and enter a `Peered` state. Unmatched or incompatible connectors in an `Orphan` or `Conflict` state are not billed. +Billing for VPC Peering 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. diff --git a/pages/vpc-peering/troubleshooting/resolving-peering-conflicts.mdx b/pages/vpc-peering/troubleshooting/resolving-peering-conflicts.mdx index d2a5751491..28561d23c0 100644 --- a/pages/vpc-peering/troubleshooting/resolving-peering-conflicts.mdx +++ b/pages/vpc-peering/troubleshooting/resolving-peering-conflicts.mdx @@ -1,6 +1,6 @@ --- title: Resolving peering conflicts -description: Learn how to proceed when your VPC Peering connector has a conflict state, and what to do to resolve the issue of overlapping CIDR networks. +description: Learn how to proceed when your VPC Peering connector has a conflict status, and what to do to resolve the issue of overlapping CIDR networks. tags: vpc, private-network, delete, resources, ipam, error dates: validation: 2026-02-10 @@ -8,7 +8,7 @@ dates: --- -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. You may create a peering connector, and then see that it has a status of `Conflict`. This page explains that status, and gives you tips on resolving the issue so your connector can move to a status of `Peered`. @@ -52,7 +52,7 @@ Once you have resolved the conflict, you must use the dedicated refresh button ( If the conflict is resolved, the peering connectors will now show a `Peered` status, and the connection is established. -Note that after creating a peering connector towards a target VPC, you cannot create a new Private Network the origin VPC where its CIDR range overlaps with a Private Network in the target VPC. This restriction applies regardless of whether the peering connection is successfuly established yet. Attempting to create such a Private Network will result in a validation error, as overlapping subnets across peered VPCs would cause routing ambiguities and potential traffic blackholing. +Note that after creating a peering connector toward a target VPC, you cannot create a new Private Network in the origin VPC where its CIDR range overlaps with a Private Network in the target VPC. This restriction applies regardless of whether the peering connection is successfully established yet. Attempting to create such a Private Network will result in a validation error, as overlapping subnets across peered VPCs would cause routing ambiguities and potential traffic blackholing. Always ensure that new Private Networks have non-overlapping CIDR blocks with all VPCs they may peer with or are already connected to. diff --git a/pages/vpc/how-to/manage-routing.mdx b/pages/vpc/how-to/manage-routing.mdx index 944822273b..460f2d9e6e 100644 --- a/pages/vpc/how-to/manage-routing.mdx +++ b/pages/vpc/how-to/manage-routing.mdx @@ -23,7 +23,9 @@ Read more about the VPC routing feature, including detailed explanations, usage ## How to activate routing + Routing is activated as standard whenever you [create a new VPC](/vpc/how-to/create-vpc/#how-to-create-a-vpc). + To activate routing on a pre-existing VPC, follow these steps: @@ -31,7 +33,7 @@ To activate routing on a pre-existing VPC, follow these steps: 2. Use the **region selector** at the top of the page to filter for the region of the VPC on which you want to configure routing. - The **Routing** column allows you to see whether routing is already activated for a given VPC. + The **Routing** column allows you to see whether routing is already activated and up-to-date for a given VPC. 3. Click **Activate** next to the VPC on which you want to activate routing. @@ -195,10 +197,11 @@ Follow the steps below to define a custom route: - Other Private Networks who have opted in to receive default routes from throughout the VPC will also receive this route. -8. Enter a **next hop** for the route. The VPC will route traffic for the destination IP to the resource designated as next hop. +8. Enter a **next hop** for the route. The VPC will route traffic for the destination IP to the resource designated as the next hop. + - Select a peering connector if you are setting up [VPC peering](/vpc-peering/how-to/manage-routing/). - Select the Private Network which the next hop resource is attached to. - - Select a resource type, e.g. **Instance**, **Public Gateway** or **Elastic Metal**. - - Select the **name** of the specific resource you want to route traffic to. The resource must be attached to a Private Network in this VPC. + - Select a resource type, e.g. **Instance**, **Public Gateway**, or **Elastic Metal**. + - Select the **name** of the specific resource you want to route traffic to. The resource must be attached to a Private Network in this VPC. If you entered an IPv6 destination, resources not compatible with IPv6, e.g. Public Gateways, will not be available for selection as next hop.