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 9d30c6912095729937b6c8b05583ee4d47c6391d Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Fri, 10 Apr 2026 16:16:27 +0200 Subject: [PATCH 2/5] Apply suggestion from @SamyOubouaziz --- .../reference-content/self-hosted-provisioning.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/interlink/reference-content/self-hosted-provisioning.mdx b/pages/interlink/reference-content/self-hosted-provisioning.mdx index 86f2cc00e1..a24fe72353 100644 --- a/pages/interlink/reference-content/self-hosted-provisioning.mdx +++ b/pages/interlink/reference-content/self-hosted-provisioning.mdx @@ -1,10 +1,10 @@ --- 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. +description: Get help with understanding all the different stages of provisioning a self-hosted Scaleway InterLink. tags: interlink provision self-hosted dedicated connection loa cross-connect steps process dates: - validation: 2025-09-30 - posted: 2024-10-24 + validation: 2026-04-10 + posted: 2026-04-10 --- From ad91b52aadf7029fec56b6f7b852cde1e42a2139 Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Mon, 13 Apr 2026 17:34:58 +0200 Subject: [PATCH 3/5] docs(interLink): update --- pages/interlink/reference-content/self-hosted-provisioning.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/pages/interlink/reference-content/self-hosted-provisioning.mdx b/pages/interlink/reference-content/self-hosted-provisioning.mdx index a24fe72353..010cd5ddec 100644 --- a/pages/interlink/reference-content/self-hosted-provisioning.mdx +++ b/pages/interlink/reference-content/self-hosted-provisioning.mdx @@ -27,7 +27,7 @@ Before creating a self-hosted InterLink, you must first provision a dedicated ph 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. +Billing for the dedicated physical connection begins once Scaleway creates the connection resource in its system, i.e. 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. @@ -40,7 +40,6 @@ Once a dedicated physical connection is in place, you can create one or more Int - **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. From 855fd066338a1f1dd39db2229153c34ca9729c55 Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Mon, 13 Apr 2026 17:36:59 +0200 Subject: [PATCH 4/5] docs(interLink): update --- pages/interlink/menu.ts | 6 +++++- .../reference-content/self-hosted-provisioning.mdx | 2 +- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/pages/interlink/menu.ts b/pages/interlink/menu.ts index e9755b2813..5f41339fad 100644 --- a/pages/interlink/menu.ts +++ b/pages/interlink/menu.ts @@ -59,9 +59,13 @@ export const interlinkMenu = { slug: 'overview', }, { - label: 'InterLink provisioning', + label: 'InterLink hosted provisioning', slug: 'provisioning', }, + { + label: 'InterLink self-hosted provisioning', + slug: 'self-hosted-provisioning', + }, { label: 'Configuring an InterLink', slug: 'configuring', diff --git a/pages/interlink/reference-content/self-hosted-provisioning.mdx b/pages/interlink/reference-content/self-hosted-provisioning.mdx index 010cd5ddec..848a5ecadc 100644 --- a/pages/interlink/reference-content/self-hosted-provisioning.mdx +++ b/pages/interlink/reference-content/self-hosted-provisioning.mdx @@ -1,5 +1,5 @@ --- -title: Provisioning a self-hosted InterLink +title: InterLink Self-hosted provisioning process description: Get help with understanding all the different stages of provisioning a self-hosted Scaleway InterLink. tags: interlink provision self-hosted dedicated connection loa cross-connect steps process dates: From 68fda6d50695897e97eb5181788c0c44e7f38180 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Tue, 14 Apr 2026 14:32:48 +0200 Subject: [PATCH 5/5] Apply suggestions from code review Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> --- .../reference-content/self-hosted-provisioning.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/pages/interlink/reference-content/self-hosted-provisioning.mdx b/pages/interlink/reference-content/self-hosted-provisioning.mdx index 848a5ecadc..4ef4f8df61 100644 --- a/pages/interlink/reference-content/self-hosted-provisioning.mdx +++ b/pages/interlink/reference-content/self-hosted-provisioning.mdx @@ -1,5 +1,5 @@ --- -title: InterLink Self-hosted provisioning process +title: InterLink self-hosted provisioning process description: Get help with understanding all the different stages of provisioning a self-hosted Scaleway InterLink. tags: interlink provision self-hosted dedicated connection loa cross-connect steps process dates: @@ -11,7 +11,7 @@ dates: 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. +This document explains the steps in the provisioning process for 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. @@ -22,12 +22,12 @@ Before creating a self-hosted InterLink, you must first provision a dedicated ph - 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. +- 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, i.e. 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. +Billing for the dedicated physical connection begins once Scaleway creates the connection resource in its system, i.e., 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. @@ -45,7 +45,7 @@ Once a dedicated physical connection is in place, you can create one or more Int 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. +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.