From 401d454f18a0acd455e57fab5978b9bac5569ee8 Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Fri, 10 Apr 2026 16:01:18 +0200 Subject: [PATCH 1/5] docs(interLink): add page on self-hosted provisioning --- .../self-hosted-provisioning.mdx | 56 +++++++++++++++++++ 1 file changed, 56 insertions(+) create mode 100644 pages/interlink/reference-content/self-hosted-provisioning.mdx diff --git a/pages/interlink/reference-content/self-hosted-provisioning.mdx b/pages/interlink/reference-content/self-hosted-provisioning.mdx new file mode 100644 index 0000000000..86f2cc00e1 --- /dev/null +++ b/pages/interlink/reference-content/self-hosted-provisioning.mdx @@ -0,0 +1,56 @@ +--- +title: Provisioning a self-hosted InterLink +description: Get help with understanding all the different stages of provisioning a self-hosted Scaleway InterLink, from establishing the dedicated physical connection, to creating and configuring InterLinks over it, and deprovisioning when no longer needed. +tags: interlink provision self-hosted dedicated connection loa cross-connect steps process +dates: + validation: 2025-09-30 + posted: 2024-10-24 +--- + + +This page concerns the provisioning process for **self-hosted** InterLinks only. For hosted InterLinks, provisioned via a partner, see the [hosted InterLink provisioning documentation](/interlink/reference-content/provisioning/). + + +This document explains the different steps of the provisioning process of self-hosted InterLinks. + +Provisioning a self-hosted InterLink happens in two phases: first, establishing a [dedicated physical connection](/interlink/concepts/#dedicated-physical-connection) between your router and Scaleway's router, then [creating one or more InterLinks](/interlink/how-to/order-interlink/) over that connection. + + +## Establishing the dedicated physical connection + +Before creating a self-hosted InterLink, you must first provision a dedicated physical connection. This process is handled manually by Scaleway teams. [contact the Scaleway sales team](https://www.scaleway.com/en/contact-sales/) to provide the following information: + +- The **PoP location** where your physical connection to Scaleway's network will be established. +- The **port speed**: 1 Gbps, 10 Gbps, or 100 Gbps. +- The **Project** within your Organization to host the physical connection resource. If none is specified, Scaleway defaults to your Organization's default project. + +Once agreed, Scaleway issues a **Letter of Authorization (LOA)** containing the meet-me room details and port assignment on Scaleway's equipment. You must provide this LOA to your data center operator (or carrier) to perform the physical patching. + + +Billing for the dedicated physical connection begins once Scaleway creates the connection resource in its system — when the physical link is detected as active. This applies regardless of whether any InterLinks have been created over the connection, or whether traffic is flowing. + + +When the cross-connect is complete and the link is detected as active, the dedicated physical connection becomes available for you in the [Scaleway console](https://console.scaleway.com). You can then proceed to create InterLinks over it. + +## Partitioning the connection using InterLinks + +Once a dedicated physical connection is in place, you can create one or more InterLinks over it via the Scaleway [InterLink API](https://www.scaleway.com/en/developers/api/interlink/), the [Scaleway console](/interlink/how-to/order-interlink/), or one of our other [developer tools](https://www.scaleway.com/en/developers/). When creating, you set the following parameters: + +- **Connection type**: Self-hosted. +- **Dedicated connection**: The physical connection to use as the basis for the InterLink. +- **Bandwidth**: The bandwidth to allocate to this InterLink. Multiple InterLinks can share the same physical connection, as long as their combined bandwidth does not exceed the total port speed. +- **Region**: The region in which to create the InterLink. It must correspond to the region of the Scaleway VPC you want to later attach to the InterLink. +- **Name**: A name (and, optionally, tags) for the InterLink. + + +Creating InterLink resources over a dedicated physical connection does not incur an additional Scaleway fee beyond the physical connection itself. + + +You can attach an InterLink to a VPC in a different Project than the one hosting the dedicated physical connection, as long as both Projects belong to the same Organization and Region. This allows you to manage physical connections centrally in a dedicated network Project, while other Projects can use the InterLink. + +After creation, the InterLink briefly enters `Configuring` status before moving to `Ready` status. See the [statuses documentation](/interlink/reference-content/statuses/) for help with resolving any error statuses. + +## Demarcation Points + +The Demarcation Point on the user side includes the Cross-Connect and ends at the physical interface (port) of Scaleway’s equipment. +For Scaleway, the Demarcation Point is the physical port of its own networking equipment. From 37448655ea2385a07f2f84b809644c14fb9dd5f3 Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Fri, 10 Apr 2026 16:40:11 +0200 Subject: [PATCH 2/5] docs(vpc-peering): add features and limitations page --- pages/vpc-peering/menu.ts | 4 + .../features-limitations.mdx | 73 +++++++++++++++++++ 2 files changed, 77 insertions(+) create mode 100644 pages/vpc-peering/reference-content/features-limitations.mdx diff --git a/pages/vpc-peering/menu.ts b/pages/vpc-peering/menu.ts index 394e42da0a..7477f1ecb9 100644 --- a/pages/vpc-peering/menu.ts +++ b/pages/vpc-peering/menu.ts @@ -32,6 +32,10 @@ export const vpcPeeringMenu = { label: 'Understanding VPC Peering', slug: 'understanding-vpc-peering', }, + { + label: 'Features and limitations', + slug: 'features-limitations', + }, { label: 'VPC Peering statuses', slug: 'statuses', diff --git a/pages/vpc-peering/reference-content/features-limitations.mdx b/pages/vpc-peering/reference-content/features-limitations.mdx new file mode 100644 index 0000000000..ad753ce4e0 --- /dev/null +++ b/pages/vpc-peering/reference-content/features-limitations.mdx @@ -0,0 +1,73 @@ +--- +title: VPC Peering features and limitations +description: This page presents the different features and limitations of Scaleway VPC Peering. +tags: vpc-peering features limitations specs quota transitivity dhcp technical datasheet +dates: + creation: 2026-04-10 + validation: 2026-04-10 +--- + + +VPC Peering is currently in Public Beta, and available only via the [Scaleway API](https://www.scaleway.com/en/developers/api/vpc/). + + +This page lists the different features and limitations of Scaleway VPC Peering. + +## Features + +### Cross-project and cross-organization peering + +VPC Peering lets you connect any two Scaleway VPCs, whether they belong to the same Project or Organization, or different ones. There is no requirement for the two VPCs to share any common ownership or management. + +### 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. + +### Fine-grained traffic control via custom routes + +Once two VPCs are peered, you control exactly which traffic flows across the peering connection by creating [custom routes](/vpc/how-to/manage-routing/#how-to-create-a-custom-route). Routes support both IPv4 and IPv6, and each side independently manages its own routing configuration. + +### Transitive peering + +VPC Peering natively supports transitive peering. This means that VPC A can communicate with VPC C via an intermediate VPC B (A ↔ B ↔ C), even without a direct peering connector between A and C. Transitivity requires custom routes to be configured in each VPC of the chain. + +### Unlimited traffic + +Once a peering connection is established, there are no caps or rate limits on the traffic flowing across it. + +## Limitations + +### Same-region requirement + +Two VPCs can only be peered if they are located in the same Scaleway region. Cross-region peering is not supported. + +### 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. + +### Custom routes are not created automatically + +Traffic does not flow between two peered VPCs automatically. You must manually create custom routes on each side to define the IP ranges that should be routed across the peering connection. + +### DHCP route propagation delay + +When a new custom route is added to a VPC's route table, it is not propagated immediately to attached resources via DHCP. Resources will receive the updated routing information only upon their next DHCP lease renewal, which can take up to 1 hour. + +### Routing must be activated on older VPCs + +VPCs created before routing was introduced must have [routing activated](/vpc/how-to/manage-routing/#how-to-activate-routing) before a peering connection can be successfully established. + +### Target VPC ID required + +When creating a peering connector, you must specify the exact VPC ID of the target VPC. No additional information about the target VPC (such as its network topology or resources) is disclosed during the process. + +## Quotas + +| Resource | Default limit | +|-------------------------------------|---------------| +| Peering connectors per Organization | 512 | +| Chained VPCs for transitive peering | 4 | + + +The default quota of 512 peering connectors per Organization can be increased on demand. Contact [Scaleway support](https://console.scaleway.com/support) to request a quota increase. + From a7fbfb0180933c6bb3e69717088afd6e3027ba89 Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Fri, 10 Apr 2026 17:56:40 +0200 Subject: [PATCH 3/5] docs(vpc-peering): remove interlink stuff --- .../self-hosted-provisioning.mdx | 56 ------------------- 1 file changed, 56 deletions(-) delete mode 100644 pages/interlink/reference-content/self-hosted-provisioning.mdx diff --git a/pages/interlink/reference-content/self-hosted-provisioning.mdx b/pages/interlink/reference-content/self-hosted-provisioning.mdx deleted file mode 100644 index 86f2cc00e1..0000000000 --- a/pages/interlink/reference-content/self-hosted-provisioning.mdx +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Provisioning a self-hosted InterLink -description: Get help with understanding all the different stages of provisioning a self-hosted Scaleway InterLink, from establishing the dedicated physical connection, to creating and configuring InterLinks over it, and deprovisioning when no longer needed. -tags: interlink provision self-hosted dedicated connection loa cross-connect steps process -dates: - validation: 2025-09-30 - posted: 2024-10-24 ---- - - -This page concerns the provisioning process for **self-hosted** InterLinks only. For hosted InterLinks, provisioned via a partner, see the [hosted InterLink provisioning documentation](/interlink/reference-content/provisioning/). - - -This document explains the different steps of the provisioning process of self-hosted InterLinks. - -Provisioning a self-hosted InterLink happens in two phases: first, establishing a [dedicated physical connection](/interlink/concepts/#dedicated-physical-connection) between your router and Scaleway's router, then [creating one or more InterLinks](/interlink/how-to/order-interlink/) over that connection. - - -## Establishing the dedicated physical connection - -Before creating a self-hosted InterLink, you must first provision a dedicated physical connection. This process is handled manually by Scaleway teams. [contact the Scaleway sales team](https://www.scaleway.com/en/contact-sales/) to provide the following information: - -- The **PoP location** where your physical connection to Scaleway's network will be established. -- The **port speed**: 1 Gbps, 10 Gbps, or 100 Gbps. -- The **Project** within your Organization to host the physical connection resource. If none is specified, Scaleway defaults to your Organization's default project. - -Once agreed, Scaleway issues a **Letter of Authorization (LOA)** containing the meet-me room details and port assignment on Scaleway's equipment. You must provide this LOA to your data center operator (or carrier) to perform the physical patching. - - -Billing for the dedicated physical connection begins once Scaleway creates the connection resource in its system — when the physical link is detected as active. This applies regardless of whether any InterLinks have been created over the connection, or whether traffic is flowing. - - -When the cross-connect is complete and the link is detected as active, the dedicated physical connection becomes available for you in the [Scaleway console](https://console.scaleway.com). You can then proceed to create InterLinks over it. - -## Partitioning the connection using InterLinks - -Once a dedicated physical connection is in place, you can create one or more InterLinks over it via the Scaleway [InterLink API](https://www.scaleway.com/en/developers/api/interlink/), the [Scaleway console](/interlink/how-to/order-interlink/), or one of our other [developer tools](https://www.scaleway.com/en/developers/). When creating, you set the following parameters: - -- **Connection type**: Self-hosted. -- **Dedicated connection**: The physical connection to use as the basis for the InterLink. -- **Bandwidth**: The bandwidth to allocate to this InterLink. Multiple InterLinks can share the same physical connection, as long as their combined bandwidth does not exceed the total port speed. -- **Region**: The region in which to create the InterLink. It must correspond to the region of the Scaleway VPC you want to later attach to the InterLink. -- **Name**: A name (and, optionally, tags) for the InterLink. - - -Creating InterLink resources over a dedicated physical connection does not incur an additional Scaleway fee beyond the physical connection itself. - - -You can attach an InterLink to a VPC in a different Project than the one hosting the dedicated physical connection, as long as both Projects belong to the same Organization and Region. This allows you to manage physical connections centrally in a dedicated network Project, while other Projects can use the InterLink. - -After creation, the InterLink briefly enters `Configuring` status before moving to `Ready` status. See the [statuses documentation](/interlink/reference-content/statuses/) for help with resolving any error statuses. - -## Demarcation Points - -The Demarcation Point on the user side includes the Cross-Connect and ends at the physical interface (port) of Scaleway’s equipment. -For Scaleway, the Demarcation Point is the physical port of its own networking equipment. From 29118662079752cd0931856e352c21d787baa1ab Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Mon, 13 Apr 2026 16:30:29 +0200 Subject: [PATCH 4/5] docs(vpc-peering): update --- .../reference-content/features-limitations.mdx | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/pages/vpc-peering/reference-content/features-limitations.mdx b/pages/vpc-peering/reference-content/features-limitations.mdx index ad753ce4e0..fd1952daa8 100644 --- a/pages/vpc-peering/reference-content/features-limitations.mdx +++ b/pages/vpc-peering/reference-content/features-limitations.mdx @@ -59,15 +59,4 @@ VPCs created before routing was introduced must have [routing activated](/vpc/ho ### Target VPC ID required -When creating a peering connector, you must specify the exact VPC ID of the target VPC. No additional information about the target VPC (such as its network topology or resources) is disclosed during the process. - -## Quotas - -| Resource | Default limit | -|-------------------------------------|---------------| -| Peering connectors per Organization | 512 | -| Chained VPCs for transitive peering | 4 | - - -The default quota of 512 peering connectors per Organization can be increased on demand. Contact [Scaleway support](https://console.scaleway.com/support) to request a quota increase. - +When creating a peering connector, you must specify the exact VPC ID of the target VPC. No additional information about the target VPC (such as its network topology or resources) is disclosed during the process. \ No newline at end of file From 0233113297b2530cb7c6f55a8532a8958c291e1c Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Tue, 14 Apr 2026 16:28:28 +0200 Subject: [PATCH 5/5] Update pages/vpc-peering/reference-content/features-limitations.mdx Co-authored-by: Firdevs Arslan --- pages/vpc-peering/reference-content/features-limitations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/vpc-peering/reference-content/features-limitations.mdx b/pages/vpc-peering/reference-content/features-limitations.mdx index fd1952daa8..f22f559ba6 100644 --- a/pages/vpc-peering/reference-content/features-limitations.mdx +++ b/pages/vpc-peering/reference-content/features-limitations.mdx @@ -17,7 +17,7 @@ This page lists the different features and limitations of Scaleway VPC Peering. ### Cross-project and cross-organization peering -VPC Peering lets you connect any two Scaleway VPCs, whether they belong to the same Project or Organization, or different ones. There is no requirement for the two VPCs to share any common ownership or management. +VPC Peering lets you connect any two Scaleway VPCs, whether they belong to the same Project or Organization, or to different ones. There is no requirement for the two VPCs to share any common ownership or management. ### Mutual consent security model