diff --git a/menu/navigation.json b/menu/navigation.json index 69a93b21be..b7e603f89e 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -4001,11 +4001,11 @@ { "items": [ { - "label": "Order an InterLink", + "label": "Create an InterLink", "slug": "order-interlink" }, { - "label": "Complete InterLink provisioning", + "label": "Complete hosted InterLink provisioning", "slug": "complete-provisioning" }, { diff --git a/pages/account/reference-content/products-availability.mdx b/pages/account/reference-content/products-availability.mdx index 76d86213bb..ce70945d58 100644 --- a/pages/account/reference-content/products-availability.mdx +++ b/pages/account/reference-content/products-availability.mdx @@ -3,7 +3,7 @@ title: Scaleway account - Product availability guide description: Check availability details of Scaleway products. tags: availability region zone availability-zone dates: - validation: 2025-06-17 + validation: 2025-09-30 posted: 2023-01-05 --- @@ -38,6 +38,7 @@ Scaleway products are available in multiple regions and locations worldwide. Thi | | SQL Databases | Across Paris region | Not available yet | Not available yet | | **Network** | VPC Private Networks | Across Paris region | Across Amsterdam region | Across Warsaw region | | | Public Gateways | PAR1, PAR2 | AMS1, AMS2, AMS3 | WAW1, WAW2, WAW3 | +| | InterLink | Across Paris region | Not available yet | Not available yet | | | Load Balancers | PAR1, PAR2, PAR3 | AMS1, AMS2, AMS3 | WAW1, WAW2, WAW3 | | | Edge Services | Global | Global | Global | | **Serverless** | Containers | Across Paris region | Across Amsterdam region | Across Warsaw region | diff --git a/pages/interlink/assets/scaleway-hosted-interlink-ordering.webp b/pages/interlink/assets/scaleway-hosted-interlink-ordering.webp new file mode 100644 index 0000000000..e992d83020 Binary files /dev/null and b/pages/interlink/assets/scaleway-hosted-interlink-ordering.webp differ diff --git a/pages/interlink/assets/scaleway-interlink-config.webp b/pages/interlink/assets/scaleway-interlink-config.webp index 6454339bc6..a0e4e43e5d 100644 Binary files a/pages/interlink/assets/scaleway-interlink-config.webp and b/pages/interlink/assets/scaleway-interlink-config.webp differ diff --git a/pages/interlink/assets/scaleway-interlink-listing.webp b/pages/interlink/assets/scaleway-interlink-listing.webp deleted file mode 100644 index 4bca10cf2a..0000000000 Binary files a/pages/interlink/assets/scaleway-interlink-listing.webp and /dev/null differ diff --git a/pages/interlink/assets/scaleway-interlink-ordering.webp b/pages/interlink/assets/scaleway-interlink-ordering.webp deleted file mode 100644 index 6d06561261..0000000000 Binary files a/pages/interlink/assets/scaleway-interlink-ordering.webp and /dev/null differ diff --git a/pages/interlink/assets/scaleway-interlink-overview-requesting.webp b/pages/interlink/assets/scaleway-interlink-overview-requesting.webp deleted file mode 100644 index 1fd56d561b..0000000000 Binary files a/pages/interlink/assets/scaleway-interlink-overview-requesting.webp and /dev/null differ diff --git a/pages/interlink/assets/scaleway-interlink-overview-up.webp b/pages/interlink/assets/scaleway-interlink-overview-up.webp deleted file mode 100644 index f746f3a570..0000000000 Binary files a/pages/interlink/assets/scaleway-interlink-overview-up.webp and /dev/null differ diff --git a/pages/interlink/assets/scaleway-interlink-overview.webp b/pages/interlink/assets/scaleway-interlink-overview.webp new file mode 100644 index 0000000000..84e0f6bc76 Binary files /dev/null and b/pages/interlink/assets/scaleway-interlink-overview.webp differ diff --git a/pages/interlink/assets/scaleway-order-interlink.webp b/pages/interlink/assets/scaleway-order-interlink.webp index 923b555132..c16fb8fcb5 100644 Binary files a/pages/interlink/assets/scaleway-order-interlink.webp and b/pages/interlink/assets/scaleway-order-interlink.webp differ diff --git a/pages/interlink/assets/scaleway-self-hosted-interlink-ordering.webp b/pages/interlink/assets/scaleway-self-hosted-interlink-ordering.webp new file mode 100644 index 0000000000..f2467f3341 Binary files /dev/null and b/pages/interlink/assets/scaleway-self-hosted-interlink-ordering.webp differ diff --git a/pages/interlink/concepts.mdx b/pages/interlink/concepts.mdx index 1c1a34291f..3b057b6eab 100644 --- a/pages/interlink/concepts.mdx +++ b/pages/interlink/concepts.mdx @@ -4,14 +4,9 @@ description: Understand Scaleway InterLink terminology with our glossary of the tags: interlink direct-connect dedicated self-hosted hosted connection dates: creation: 2024-10-31 - validation: 2025-03-18 + validation: 2025-09-30 --- -import image from './assets/scaleway-interlink-diag-simple.webp' - - - -InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/). - +import scalewayInterlinkDiagSimple from './assets/scaleway-interlink-diag-simple.webp' ## Attached VPC @@ -27,30 +22,36 @@ Every InterLink has a defined bandwidth, representing the maximum data transfer ## Connection type -The type of physical connection for an InterLink. In the long term, InterLink will be available in both **hosted** and **self-hosted** connection types. For now, only **hosted** connections (facilitated via a partner) are available: +The type of physical connection for an InterLink. InterLink is available in both **hosted** and **self-hosted** connection types: -- **Hosted InterLink**: The customer provisions an InterLink via a [partner](#partner). The available bandwidth of the partner's physical connection is shared between multiple customers: each gets a specified amount when creating their InterLink. -- **Self-hosted InterLink**: The customer gets sole use of a single InterLink port on Scaleway's router, with the entire bandwidth of that port. They create their own dedicated physical connection, and can use its available bandwidth to provision several InterLinks for themselves. +- **Hosted InterLink**: The customer provisions an InterLink via a [partner](#partner), who facilitates the physical connection between the external infrastructure and the Scaleway VPC. The physical connection may be shared between several clients: each gets a specified amount of bandwidth when creating their InterLink. +- **Self-hosted InterLink**: The customer provisions an InterLink using their own dedicated physical connection. They get the entire bandwidth of the connection, which can be used to provision several InterLinks for themselves. [Find out more about connection types](/interlink/reference-content/overview/#types-of-interlink). -## InterLink +## Dedicated physical connection -InterLink, currently in Public Beta, is Scaleway's product to let you create a secure, private connection between your external infrastructure, and your Scaleway VPC. This allows you to direct your traffic safely from your Scaleway infrastructure to your on-premises infrastructure, away from the public internet. +To create a self-hosted InterLink, you must first provision a dedicated physical connection between your router and Scaleway's router. You get sole use of a single InterLink port on Scaleway's router, and can use connection and its bandwidth to create several InterLinks. To provision a dedicated physical connection, [contact our sales team](https://www.scaleway.com/en/contact-sales/). -Currently, InterLink is available in **hosted** version only. This means that you must choose a compatible [partner](#partner) to facilitate the physical connection between the external infrastructure and the Scaleway VPC. The physical connection may be shared between several clients, each allocated a specific amount of bandwidth for their InterLink. +## Hosted InterLink - +See [connection type](#connection-type). + +## InterLink + +InterLink is Scaleway's product to let you create a secure, private connection between your external infrastructure, and your Scaleway VPC. This allows you to direct your traffic safely from your Scaleway infrastructure to your on-premises infrastructure, away from the public internet. + + For more information on how InterLink works, see our [detailed overview](/interlink/reference-content/overview/). ## Location -A location, aka a **P**oint **o**f **P**resence (PoP), is a physical location where you can establish an InterLink between your on-premises infrastructure and the Scaleway network. Locations are facilitated by partners. +A location, aka a **P**oint **o**f **P**resence (PoP), is a physical location where you can establish an InterLink between your on-premises infrastructure and the Scaleway network. For hosted InterLinks, locations are facilitated by partners. ## Pairing key -A pairing key is a unique identifier used to establish and authenticate an InterLink via a partner. It is provided by Scaleway once an InterLink order is made. You must then share this key with your selected partner to facilitate the setup of the physical link. The pairing key ensures that the correct endpoints are securely connected. +A pairing key is a unique identifier used to establish and authenticate a hosted link InterLink via a partner. It is provided by Scaleway once an InterLink order is made. You must then share this key with your selected partner to facilitate the setup of the physical link. The pairing key ensures that the correct endpoints are securely connected. ## Partner @@ -68,10 +69,14 @@ When creating an InterLink, you must specify a [region](/vpc/concepts/#region-an ## Route propagation -Route propagation can be activated or deactivated at any given time on an InterLink. When activated, the Scaleway VPC and external infrastructure dynamically exchange and update information about their routes. Route propagation must be activated to allow traffic to flow over the InterLink. When deactivated, all pre-learned/announced routes are removed from the VPC's route table, and traffic cannot flow. Note that even with route propagation activated, the default rule blocks all route announcements: you must attach a [routing policy](#routing-policy) to specify the route ranges to whitelist. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink) +Route propagation can be activated or deactivated at any given time on an InterLink. When activated, the Scaleway VPC and external infrastructure communicate via BGP sessions to dynamically exchange and update information about their routes. Route propagation must be activated to allow traffic to flow over the InterLink. When deactivated, all pre-learned/announced routes are removed from the VPC's route table, and traffic cannot flow. Note that even with route propagation activated, the default rule blocks all route announcements: you must attach a [routing policy](#routing-policy) to specify the route ranges to whitelist. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink) ## Routing policy The default rule blocks any and all routes from being propagated over InterLink. Attaching a routing policy allows you to define the ranges of routes that should be whitelisted. When creating a routing policy, you specify one or many IP ranges representing the outgoing routes to announce from the Scaleway VPC, and one or many IP ranges representing the incoming route announcements to accept from the external infrastructure. -Each InterLink can have one routing policy attached to it, but a single routing policy can be attached to multiple InterLinks, if desired. When [route propagation](#route-propagation) is activated, the route ranges defined in the routing policy are whitelisted, and traffic can flow across the InterLink along these routes. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink) \ No newline at end of file +IPv4 and IPv6 routes must be whitelisted in separate routing policies. An InterLink must therefore have a **minimum of one** and a **maximum of two** attached routing policies, one for each IP traffic type to be routed (IPv4 and/or IPv6). When [route propagation](#route-propagation) is activated, the route ranges defined in the attached routing policies are whitelisted, and traffic can flow across the InterLink along these routes. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink). + +## Self-hosted InterLink + +See [connection type](#connection-type). \ No newline at end of file diff --git a/pages/interlink/faq.mdx b/pages/interlink/faq.mdx index 1d437de8a3..9899fef2d6 100644 --- a/pages/interlink/faq.mdx +++ b/pages/interlink/faq.mdx @@ -1,24 +1,20 @@ --- -title: InterLink FAQ +title: InterLink description: Discover Scaleway InterLink and find answers to your most common questions. dates: - validation: 2025-03-18 + validation: 2025-09-30 productIcon: InterlinkProductIcon --- - -InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/). - - ## What is InterLink and how does it work? InterLink is Scaleway's product to let you create a secure, private connection between your external infrastructure, and your Scaleway VPC. This allows you to direct your traffic safely from your Scaleway infrastructure to your on-premises infrastructure, away from the public internet. -Currently, InterLink is available in **hosted** version only. This means that you must choose a compatible **partner** to facilitate your InterLink. The partner provides the physical connection, and this connection may be shared between several clients, each allocated a specific amount of bandwidth for their InterLink. +Two types of InterLink are available: **hosted InterLink** where the physical connection is facilitated via a partner, or **self-hosted InterLink** where the customer provisions their own dedicated physical connection. At its simplest level, InterLink can be understood as a configurable connection between your own infrastructure, and your Scaleway VPC. You can configure details such as bandwidth, the VPC to connect to, and routing policies. -## How can I find a partner to provision my InterLink? +## How can I find a partner to provision my hosted InterLink? To establish a hosted InterLink via a partner, generally you must be a client of that partner, e.g. with your infrastructure in their data center, or on your own premises using the partner as a network provider. For more details, see our [information on choosing a partner](/interlink/reference-content/overview/#hosted-interlinks). @@ -26,9 +22,9 @@ You can see available partners in the Scaleway console by opening the [InterLink ## I want to create a dedicated InterLink without a partner, how can I do this? -We plan to make **self-hosted** InterLinks available soon, whereby a single client can provision their own physical connection without a partner, getting sole use of a single InterLink port on Scaleway's router. The bandwidth of this connection can then be used by the client to create several InterLinks just for them. +You can create a **self-hosted** InterLink, provisioning your own physical connection without a partner, getting sole use of a single InterLink port on Scaleway's router. You can then use the bandwidth of this connection to create several InterLinks just for you. -You can [contact a sales representative](https://www.scaleway.com/en/contact-sales/) to register your interest in a self-hosted InterLink. +[Contact a sales representative](https://www.scaleway.com/en/contact-sales/) to register your interest in a self-hosted InterLink. The process of provisioning the dedicated physical connection must be done via our sales team, and cannot be achieved via the Scaleway console or developer tools. ## What are the benefits of using InterLink compared to other connectivity solutions? @@ -40,4 +36,4 @@ See the [pricing page](https://www.scaleway.com/en/pricing/network/) for full de ## How can I get help with my InterLink? -Join the `#interlink` channel on the [Scaleway Slack Community](/tutorials/scaleway-slack-community/) to get help and support for your InterLink during the Public Beta phase. \ No newline at end of file +Join the `#interlink` channel on the [Scaleway Slack Community](/tutorials/scaleway-slack-community/) to get help and support for your InterLink \ No newline at end of file diff --git a/pages/interlink/how-to/assets/scaleway-attach-routing-pol.webp b/pages/interlink/how-to/assets/scaleway-attach-routing-pol.webp new file mode 100644 index 0000000000..a29567d4fe Binary files /dev/null and b/pages/interlink/how-to/assets/scaleway-attach-routing-pol.webp differ diff --git a/pages/interlink/how-to/assets/scaleway-attach-routing-policy.webp b/pages/interlink/how-to/assets/scaleway-attach-routing-policy.webp deleted file mode 100644 index af217c26f4..0000000000 Binary files a/pages/interlink/how-to/assets/scaleway-attach-routing-policy.webp and /dev/null differ diff --git a/pages/interlink/how-to/assets/scaleway-create-routing-policy.webp b/pages/interlink/how-to/assets/scaleway-create-routing-policy.webp index 190ac60f64..2b80fe1e68 100644 Binary files a/pages/interlink/how-to/assets/scaleway-create-routing-policy.webp and b/pages/interlink/how-to/assets/scaleway-create-routing-policy.webp differ diff --git a/pages/interlink/how-to/assets/scaleway-hosted-interlink-ordering.webp b/pages/interlink/how-to/assets/scaleway-hosted-interlink-ordering.webp new file mode 100644 index 0000000000..e992d83020 Binary files /dev/null and b/pages/interlink/how-to/assets/scaleway-hosted-interlink-ordering.webp differ diff --git a/pages/interlink/how-to/assets/scaleway-interlink-config.webp b/pages/interlink/how-to/assets/scaleway-interlink-config.webp index 6454339bc6..05ef46f4c5 100644 Binary files a/pages/interlink/how-to/assets/scaleway-interlink-config.webp and b/pages/interlink/how-to/assets/scaleway-interlink-config.webp differ diff --git a/pages/interlink/how-to/assets/scaleway-interlink-listing.webp b/pages/interlink/how-to/assets/scaleway-interlink-listing.webp deleted file mode 100644 index 4bca10cf2a..0000000000 Binary files a/pages/interlink/how-to/assets/scaleway-interlink-listing.webp and /dev/null differ diff --git a/pages/interlink/how-to/assets/scaleway-interlink-ordering.webp b/pages/interlink/how-to/assets/scaleway-interlink-ordering.webp deleted file mode 100644 index 6d06561261..0000000000 Binary files a/pages/interlink/how-to/assets/scaleway-interlink-ordering.webp and /dev/null differ diff --git a/pages/interlink/how-to/assets/scaleway-interlink-overview-up.webp b/pages/interlink/how-to/assets/scaleway-interlink-overview-up.webp index f746f3a570..a57b47c363 100644 Binary files a/pages/interlink/how-to/assets/scaleway-interlink-overview-up.webp and b/pages/interlink/how-to/assets/scaleway-interlink-overview-up.webp differ diff --git a/pages/interlink/how-to/assets/scaleway-order-interlink.webp b/pages/interlink/how-to/assets/scaleway-order-interlink.webp index 923b555132..c16fb8fcb5 100644 Binary files a/pages/interlink/how-to/assets/scaleway-order-interlink.webp and b/pages/interlink/how-to/assets/scaleway-order-interlink.webp differ diff --git a/pages/interlink/how-to/assets/scaleway-self-hosted-interlink-ordering.webp b/pages/interlink/how-to/assets/scaleway-self-hosted-interlink-ordering.webp new file mode 100644 index 0000000000..f2467f3341 Binary files /dev/null and b/pages/interlink/how-to/assets/scaleway-self-hosted-interlink-ordering.webp differ diff --git a/pages/interlink/how-to/complete-provisioning.mdx b/pages/interlink/how-to/complete-provisioning.mdx index 77e4208098..1315220220 100644 --- a/pages/interlink/how-to/complete-provisioning.mdx +++ b/pages/interlink/how-to/complete-provisioning.mdx @@ -1,42 +1,34 @@ --- -title: How to complete InterLink provisioning +title: How to complete hosted InterLink provisioning description: Learn how to complete the provisioning process for your Scaleway InterLink, to ensure your hosted connection between your on-premises infrastructure and Scaleway VPC is up and running as soon as possible. dates: - validation: 2025-03-18 + validation: 2025-09-30 posted: 2025-03-18 tags: interlink direct-connect provision hosted partner contact error --- import Requirements from '@macros/iam/requirements.mdx' -import image from './assets/scaleway-interlink-ordering.webp' -import image2 from './assets/scaleway-interlink-overview-requesting.webp' -import image3 from './assets/scaleway-interlink-listing.webp' +import scalewayHostedInterlinkOrdering from './assets/scaleway-hosted-interlink-ordering.webp' - -InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/). - - -After you have [ordered your InterLink](/interlink/how-to/order-interlink), further action is required on both the customer side and the [partner](/interlink/concepts/#partner) side before the InterLink is provisioned and ready for active use. This page walks you through the steps to take and how to deal with potential problems that could arise. +After you have [created a hosted InterLink](/interlink/how-to/order-interlink), further action is required on both the customer side and the [partner](/interlink/concepts/#partner) side before the InterLink is provisioned and ready for active use. This page walks you through the steps to take and how to deal with potential problems that could arise. - + - 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 -- [Ordered an InterLink](/interlink/how-to/order-interlink) +- [Created a hosted InterLink](/interlink/how-to/order-interlink) ## Contact partner to request InterLink -After ordering the InterLink from Scaleway, you **must** contact your chosen partner to request that they provision the connection on their side. Scaleway is not able to automatically do this step for you. +After creating the hosted InterLink on the Scaleway side, you **must** contact your chosen partner to request that they provision the connection on their side. Scaleway is not able to automatically do this step for you. 1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your InterLinks displays. 2. Click on the InterLink that you want to finish provisioning. The InterLink's **Overview** page displays. - - 3. Note down the [pairing key](/interlink/concepts/#pairing-key) for your InterLink. This is a unique identification number which the partner will need in order to provision your InterLink. 4. Contact your partner. After [creating your InterLink order](/interlink/how-to/order-interlink/), either their online portal URL, or their email address was displayed to you for this purpose. Use the relevant method to contact your partner, provide the pairing key, and request that they provision your InterLink from their side. @@ -51,8 +43,6 @@ Your InterLink will remain in `Requested` status until the partner responds to y Once you have requested the InterLink from your partner, you must wait for them to respond to your request. There is no further action for you to take at this point. You can keep track of your InterLink's [status](/interlink/reference-content/statuses/) via the [InterLink listing](https://console.scaleway.com/interlink/links) in the Scaleway console. - - When the partner approves your request, the InterLink moves to `Provisioning` status. This means that the partner has agreed to facilitate your InterLink, and is now preparing the resources and configuration necessary to do so. Your InterLink will remain in `Provisioning` status until this process has been completed. diff --git a/pages/interlink/how-to/configure-interlink.mdx b/pages/interlink/how-to/configure-interlink.mdx index d1d92d923c..df78bf10fa 100644 --- a/pages/interlink/how-to/configure-interlink.mdx +++ b/pages/interlink/how-to/configure-interlink.mdx @@ -2,32 +2,26 @@ title: How to configure your InterLink description: Learn how to configure your Scaleway InterLink, from attaching a VPC to creating a routing policy and activating route propagation. We walk you through al the steps necessary to start using your hosted connection. dates: - validation: 2025-03-18 + validation: 2025-09-30 posted: 2025-03-18 tags: interlink direct-connect configure attach-vpc route-propagation allowed-routes routing-policy --- -import Requirements from '@macros/iam/requirements.mdx' -import image from './assets/scaleway-interlink-config.webp' -import image2 from './assets/scaleway-interlink-overview-up.webp' -import image3 from './assets/scaleway-interlink-attach-vpc.webp' -import image4 from './assets/scaleway-interlink-overview-up.webp' -import image5 from './assets/scaleway-attach-routing-policy.webp' -import image6 from './assets/scaleway-interlink-overview-up.webp' -import image7 from './assets/scaleway-interlink-attach-vpc.webp' +import Requirements from '@macros/iam/requirements.mdx' +import scalewayInterlinkConfig from './assets/scaleway-interlink-config.webp' +import scalewayInterlinkAttachVpc from './assets/scaleway-interlink-attach-vpc.webp' +import scalewayAttachRoutingPol from './assets/scaleway-attach-routing-pol.webp' - -InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/). - -Once your InterLink has been [provisioned](/interlink/how-to/complete-provisioning/) by your chosen partner, a number of configuration steps become available to you. These steps must be carried out in order for traffic to successfully flow over your InterLink: +Once you have created your InterLink (and in the case of hosted InterLinks, it has been [provisioned](/interlink/how-to/complete-provisioning/) by your chosen partner), a number of configuration steps become available to you. These steps must be carried out in order for traffic to successfully flow over your InterLink: - Attach a VPC -- Create and attach a routing policy +- Create and attach routing policies +- Set up network device (self-hosted InterLinks only) - Activate route propagation - + This document explains how to complete these configuration steps with the Scaleway console. @@ -35,7 +29,7 @@ This document explains how to complete these configuration steps with the Scalew - 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 -- [Ordered an InterLink](/interlink/how-to/order-interlink/) which has been [provisioned](/interlink/how-to/complete-provisioning/) by the partner +- [Ordered an InterLink](/interlink/how-to/order-interlink/) (which, if self-hosted, has been [provisioned](/interlink/how-to/complete-provisioning/) by the partner) ## How to attach a VPC @@ -45,11 +39,9 @@ Attaching an InterLink to a VPC allows you to complete the connection from your 2. Click on the InterLink that you want to configure. The InterLink's **Overview** page displays. - - 3. In the **Attached VPC** section, click **Attach VPC**. A pop-up displays: - + 4. Select one of your existing VPCs from the dropdown list. It must be in the same region as the InterLink. Alternatively, click **+ Create VPC** to create and attach a new VPC. @@ -63,24 +55,25 @@ Attaching an InterLink to a VPC allows you to complete the connection from your To enable traffic to flow across the InterLink, you must still create and attach a routing policy, and activate route propagation. -## How to attach a routing policy +## How to attach routing policies -After attaching a VPC, the next step in configuring your InterLink is to create and attach a routing policy. +After attaching a VPC, the next step in configuring your InterLink is to create and attach routing policies. The VPC and the external infrastructure's routers both announce their routes to each other via [BGP](/interlink/concepts/#border-gateway-protocol-bgp) when route propagation is activated, but all of these routes are blocked by default. Routing policies let you whitelist ranges of route announcements to allow, so that traffic can flow along these routes across the InterLink. -Each InterLink can have one routing policy attached to it, but a single routing policy can be attached to multiple InterLinks, if desired. +An InterLink must have a **minimum of one** and a **maximum of two** attached routing policies, one for each IP traffic type to be routed (IPv4 and/or IPv6). + +Each routing policy can be attached to multiple InterLinks, if desired. See the dedicated documentation on [creating a routing policy](/interlink/how-to/create-routing-policy/) to create a policy, then follow these instructions to attach it: 1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your InterLinks displays. 2. Click on the InterLink that you want to configure. The InterLink's **Overview** page displays. - -3. In the **Route propagation** section, click **Attach routing policy**. A pop-up displays. +3. In the **Route propagation** section, click **Attach routing policy** for either IPv4 or IPv6 . A pop-up displays. - + 4. Select a routing policy from the drop-down list, and click **Attach policy**. @@ -90,27 +83,42 @@ See the dedicated documentation on [creating a routing policy](/interlink/how-to The policy is attached, ad you are returned to the InterLink's **Overview** page. +Repeat the process to attach up to two routing policies in total (one for IPv4 and one for IPv6). + +## How to set up your network device (self-hosted only) + + +This step is necessary for [self-hosted InterLinks](/interlink/reference-content/overview/#self-hosted-interlink) only. If you have a hosted InterLink, provisioned via a partner, you do not need to set up a network device. + + +You must configure the real physical or software-based networking device, located on the remote network you are connecting to your Scaleway VPC via the InterLink. You will need the following information, which is available from your InterLink's **Overview** screen in the Scaleway console: + +- **Scaleway ASN** (12876) +- **VLAN ID** for the InterLink + +You also need to set up route announcements and filters on the customer side. For this, you will need the following information, also available from the InterLink's **Overview** screen. + +- **BGP interconnection subnet(s)**: The private subnet used for the VPC and external infrastructure to establish a BGP session and exchange routing information. For InterLinks that have both IPv4 and IPv6 routing policies, one IPv4 and one IPv6 subnet will be provided. + +- **Routing policy**: Take into account the routing policy(ies) you attached to the connection, when configuring routing policy on the customer gateway device. + ## How to activate route propagation -Once you have attached a VPC and attached a routing policy, you can activate route propagation. This is the final step in configuring your InterLink so that traffic can flow between the VPC and your external infrastructure: it triggers the dynamic exchange of route information between the VPC and external infrastructure. +Activating route propagation is the final step in configuring your InterLink so that traffic can flow between the VPC and your external infrastructure: it triggers the dynamic exchange of route information between the VPC and external infrastructure. 1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your InterLinks displays. 2. Click on the InterLink that you want to configure. The InterLink's **Overview** page displays. - +3. In the **Route propagation** section, click **Activate propagation**. -3. In the **Route propagation** section, use the toggle to turn route propagation **ON**. - - A pop-up displays, showing the attached routing policy which will define the incoming and outgoing route announcements to accept. You can change the attached routing policy if you wish. - - It is not possible to activate route propagation without attaching a routing policy, as all route announcements would be blocked, rendering the action ineffective. + A pop-up displays, confirming that the action will launch the BGP session(s), allowing traffic to flow over the InterLink via the routes whitelisted in the attached routing policy(ies). 4. Click **Activate route propagation**. - Route propagation is activated, and you are returned to your InterLink's overview page. + Route propagation is activated. You are returned to your InterLink's overview page. - While route propagation remains active, traffic can flow across the InterLink along the routes allowed by the routing policy. The VPC and external infrastructure will dynamically exchange and update route information. You can deactivate route propagation at any time: if you do so, all routes are blocked and no traffic can flow. + While route propagation remains active, the VPC and external infrastructure will dynamically exchange and update route information. Traffic can flow across the InterLink along the routes whitelisted in the routing policy(ies). You can deactivate route propagation at any time: if you do so, all routes are blocked and no traffic can flow. ## How to modify your InterLink configuration @@ -118,19 +126,19 @@ You can modify the following aspects of your InterLink configuration at any time - The attached Scaleway VPC - The attached routing policy -- Whether route propagation is on or off +- The activation or deactivation of route propagation -It is not possible to modify settings that were defined at the time of creating the InterLink, such as its region, partner, location, or bandwidth. To modify any of those settings, you must delete the InterLink and create a new one. +It is not possible to modify settings that were defined at the time of creating the InterLink, such as its region, partner, dedicated connection, location, or bandwidth. To modify any of those settings, you must delete the InterLink and create a new one. -### How to change the attached VPC +### How to detach or change the attached VPC 1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your InterLinks displays. 2. Click on the InterLink that you want to configure. The InterLink's **Overview** page displays. -3. In the **Attached VPC** section, click the unlink icon next to the VPC you want to detach. +3. In the **Attached VPC** section, click the unlink icon next to the VPC to detach. A pop-up displays, confirming that this action will detach the VPC, and the InterLink will not be connected to any Scaleway resources until you reattach a VPC. @@ -142,59 +150,21 @@ It is not possible to modify settings that were defined at the time of creating The VPC is detached, and you are returned to the InterLink's **Overview** page. No traffic can currently flow over the InterLink, and all associated routes are removed from the VPC's route table. - Follow the next steps to attach another VPC. + If you want to attach a new VPC, follow the [normal process](#how-to-attach-a-vpc) for doing so. Remember to check that the InterLink's routing policies are appropriate for the new VPC. -5. In the **Attached VPC** section, click **Attach VPC**. A pop-up displays: - - - -6. Select one of your existing VPCs from the dropdown list. It must be in the same region as the InterLink. Alternatively, click **+ Create VPC** to create and attach a new VPC. - - - Ensure that the routing policy attached to the InterLink is suitable for the VPC you are attaching. Remember that the outgoing routes in the policy should correspond to the route announcements to whitelist from the VPC itself. - - -7. Click **Attach VPC**. - - The VPC is attached and you are returned to the InterLink's **Overview** page. Remember to check the routing policy and activate route propagation so that traffic can flow across the InterLink. - -### How to change the attached routing policy - -1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your InterLinks displays. - -2. Click on the InterLink that you want to configure. The InterLink's **Overview** page displays. - -3. In the **Route propagation** section, click the three dot icon next to the routing policy you want to detach. Then click **Detach policy** in the menu that displays. - - A pop-up confirms that this action will detach the current policy from your InterLink. If route propagation was active, it will be automatically deactivated because with no attached routing policy, the default rule will block the propagation of any new or updated routes. - -4. Click **Detach policy**. - - The policy is detached, and you are returned to your InterLink's Overview page. - -5. In the **Route propagation** section, under **Routing policy** click **+** to add a new policy. See the dedicated documentation on [creating and attaching a routing policy](/interlink/how-to/create-routing-policy/) for a step by step guide. - -### How to edit an existing routing policy +### How to replace or detach an attached routing policy 1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your InterLinks displays. 2. Click on the InterLink that you want to configure. The InterLink's **Overview** page displays. -3. In the **Route propagation** section, click the three dot icon next to the routing policy. Then click **Edit policy** in the menu that displays. - - - You can also edit routing policies from their dedicated tab in the console, including policies that aren't currently attached to an InterLink. - - - The **Edit routing policy** wizard displays. See the dedicated documentation on [creating and attaching a routing policy](/interlink/how-to/create-routing-policy/) for help with routing policies. - -4. Make the required edits, and click **Edit routing policy** +3. In the **Route propagation** section, click the three dot icon next to the routing policy you want to detach. Then click either **Replace policy** or **Detach** depending on the desired action. - A warning displays, to remind you that modifications will immediately be propagated on InterLinks using this policy. + A pop-up displays, asking you either to select the policy to replace the current one with, or to confirm that you want to detach the policy without selecting a new one. -5. Click **Save**. +4. Confirm the action. -The policy is modified and modifications are immediately applied. + The policy is detached or replaced, and you are returned to your InterLink's Overview page. ### How to deactivate route propagation @@ -202,10 +172,10 @@ The policy is modified and modifications are immediately applied. 2. Click on the InterLink that you want to configure. The InterLink's **Overview** page displays. -3. In the **Route propagation** section, use the toggle to turn route propagation **OFF**. +3. In the **Route propagation** section, click **Deactivate propagation**. A pop-up displays, confirming that this action will turn off route propagation. All existing InterLink routes will be removed from the VPC route table. Traffic will not be able to flow over the InterLink until route propagation is reactivated. 4. Click **Deactivate**. - Route propagation is deactivated, and you are returned to your InterLink's overview page. + Route propagation is deactivated, and you are returned to your InterLink's **Overview** page. diff --git a/pages/interlink/how-to/create-routing-policy.mdx b/pages/interlink/how-to/create-routing-policy.mdx index b9d43d0cce..4f41ad45ca 100644 --- a/pages/interlink/how-to/create-routing-policy.mdx +++ b/pages/interlink/how-to/create-routing-policy.mdx @@ -1,19 +1,17 @@ --- -title: How to create a routing policy +title: How to create and manage routing policies description: Find out how to create a routing policy for your Scaleway InterLink. Whitelist incoming and outgoing route announcements, so that traffic can flow securely over your InterLink. dates: - validation: 2025-03-18 + validation: 2025-09-30 posted: 2025-03-18 tags: interlink direct-connect allowed-routes route-propagation whitelist range IP announcements BGP --- -import image from './assets/scaleway-create-routing-policy.webp' +import scalewayCreateRoutingPolicy from './assets/scaleway-create-routing-policy.webp' - -InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/). - +InterLink uses [**B**order **G**ateway **P**rotocol](/interlink/concepts/#border-gateway-protocol-bgp) to exchange routing information between the customer’s infrastructure and the Scaleway VPC. Each side advertises IP prefixes for its own internal subnets and resources, to allow the other side to dynamically learn and update its internal routes, facilitating efficient traffic flow. However, by default, **all routes across an InterLink are blocked**. You must create and attach [routing policies](/interlink/concepts/#routing-policy), to set IP prefix filters for the route advertisements you want to whitelist. This facilitates traffic flow across the InterLink. -InterLink uses [**B**order **G**ateway **P**rotocol](/interlink/concepts/#border-gateway-protocol-bgp) to exchange routing information between the customer’s infrastructure and the Scaleway VPC. Each side advertises IP prefixes for its own internal subnets and resources, to allow the other side to dynamically learn and update its internal routes, facilitating efficient traffic flow. However, by default, **all routes across an InterLink are blocked**. You must create and attach a [routing policy](/interlink/concepts/#routing-policy), to set IP prefix filters for the route advertisements you want to whitelist. This facilitates traffic flow across the InterLink. +An InterLink must have a **minimum of one** and a **maximum of two** attached routing policies, one for each IP traffic type to be routed (IPv4 and/or IPv6). When creating a routing policy, you specify one or many IP ranges representing the outgoing routes to announce from the Scaleway VPC, and one or many IP ranges representing the incoming route announcements to accept from the external infrastructure. When [route propagation](#route-propagation) is activated, the route ranges defined in the routing policy are whitelisted, and traffic can flow across the InterLink along these routes. @@ -27,30 +25,48 @@ Learn more about routing across an InterLink in our [detailed overview](/interli 3. Click **+Create routing policy**. The **Create a routing policy** wizard displays. - + -4. Enter a name for the policy, or leave the randomly-generated name in place. +4. Choose a region for the policy. It can only be attached to InterLinks within the same region. -5. Choose a region for the policy. It can only be attached to InterLinks within the same region. +5. Define the type of IP traffic to be covered by the routing policy. 6. Whitelist the outgoing routes to allow. For each entry: - - Select whether it is of type IPv4 or IPv6. - Enter an IP prefix to define a range of route announcements to whitelist, e.g. `172.16.4.0/22`. - Click **Add** when complete. Routes within these destinations will be propagated, allowing traffic from your external infrastructure to be routed via InterLink to your VPC. For example, adding `172.16.4.0/22` whitelists all 1,024 IPs in this block, from `172.16.4.0` to `172.16.7.255`. - - IPv4 and IPv6 routes must be defined separately. 7. Whitelist the incoming routes to allow, in the same way you did for outgoing routes. Outgoing routes concern announcements to accept from the external infrastructure. Traffic can be routed via InterLink from your Scaleway VPC to your external infrastructure along these routes. -8. Click **Create routing policy**. +8. Enter a name for the policy, or leave the randomly-generated name in place. Optionally, you can also add tags. + +9. Click **Create routing policy**. + The policy is created, and you are returned to the listing of your routing policies. -Remember to [attach the policy to an InterLink](/interlink/how-to/configure-interlink/#how-to-attach-a-routing-policy) for it to take effect. Each InterLink can have one routing policy attached to it, but a single routing policy can be attached to multiple InterLinks, if desired. +Remember to [attach the policy to an InterLink](/interlink/how-to/configure-interlink/#how-to-attach-routing-policies) for it to take effect. Each InterLink can have only one routing policy for each IP traffic type attached to it, but a single routing policy can be attached to multiple InterLinks, if desired. See our dedicated documentation on using [BGP communities](/interlink/reference-content/bgp-communities/) to influence route priority for InterLink traffic. - \ No newline at end of file + + +## How to edit an existing routing policy + +1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your InterLinks displays. + +2. Click on the **Routing Policy** tab. A list of your routing policies displays. + +3. Click next to the routing policy to edit, and select **Edit** in the menu that displays. + +4. The **Edit routing policy** wizard displays. See the dedicated documentation on [creating and attaching a routing policy](/interlink/how-to/create-routing-policy/) for help with routing policies. + +5. Make the required edits, and click **Edit routing policy** + + A warning displays, to remind you that modifications will immediately be propagated on InterLinks using this policy. + +6. Click **Save**. + +The policy is modified and modifications are immediately applied. \ No newline at end of file diff --git a/pages/interlink/how-to/delete-interlink.mdx b/pages/interlink/how-to/delete-interlink.mdx index 3b15417dd0..368f8a4b55 100644 --- a/pages/interlink/how-to/delete-interlink.mdx +++ b/pages/interlink/how-to/delete-interlink.mdx @@ -1,19 +1,15 @@ --- title: How to delete an InterLink -description: Learn how to delete a Scaleway InterLink so that it is correctly deprovisioned on both the Scaleway side and the partner side. Follow our step by step guide. +description: Learn how to delete a Scaleway InterLink so that it is correctly deprovisioned on both the Scaleway side and (if relevant) the partner side. Follow our step by step guide. dates: - validation: 2025-03-18 + validation: 2025-09-30 posted: 2025-03-18 tags: interlink direct-connect allowed-routes routing-policy route-propagation whitelist range IP announcements BGP --- -import image from './assets/scaleway-interlink-overview-up.webp' +import scalewayInterlinkOverviewUp from './assets/scaleway-interlink-overview-up.webp' - -InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/). - - -You can delete your InterLink at any time. Action is required on both the Scaleway side and the partner side to completely deprovision the InterLink. Follow the steps below. +You can delete your InterLink at any time by following the steps below. ## How to delete an InterLink @@ -21,7 +17,7 @@ You can delete your InterLink at any time. Action is required on both the Scalew 2. Click on the InterLink that you want to delete. The InterLink's **Overview** page displays. - + 3. [Deactivate route propagation](/interlink/how-to/configure-interlink/#how-to-deactivate-route-propagation). @@ -29,14 +25,16 @@ You can delete your InterLink at any time. Action is required on both the Scalew A pop-up displays, confirming that this action will permanently delete your InterLink on the Scaleway side. -5. Type **DELETE** in the box, and click **Delete InterLink**. +5. Type **DELETE** in the box, and click **Delete InterLink**, and confirm when prompted. + + Scaleway stops billing you for your InterLink at this point, and it can no longer be configured, un-deleted, or used to route traffic. - You are returned to the InterLink's **Overview** page, where its status now shows as **Deprovisioning**. Scaleway stops billing you for your InterLink at this point, and it can no longer be configured, un-deleted, or used to route traffic. +6. **Hosted InterLinks only**: Contact your partner to request that they delete the InterLink resource on their side. They may continue to bill you until you do so, and they deprovision the resource on their side. To get in touch with the partner, you can use the same contact information that you used when [requesting the InterLink from the partner](/interlink/how-to/complete-provisioning/). -6. Contact your partner to request that they delete the InterLink resource on their side. They may continue to bill you until you do so, and they deprovision the resource on their side. To get in touch with the partner, you can use the same contact information that you used when [requesting the InterLink from the partner](/interlink/how-to/complete-provisioning/). + + If the provisioning of your InterLink by the partner was never completed, e.g. you a) never contacted the partner to request provisioning of the InterLink, or b) the partner refused to provision your InterLink, you do not need to contact the partner again to request that they deprovision the resource. Deleting it on the Scaleway side is sufficient. + - -If the provisioning of your InterLink by the partner was never completed, e.g. you a) never contacted the partner to request provisioning of the InterLink, or b) the partner refused to provision your InterLink, you do not need to contact the partner again to request that they deprovision the resource. Deleting it on the Scaleway side is sufficient. - + When the InterLink is fully deprovisioned on both sides, it will be deleted from the list of your InterLinks, and its Overview page will no longer be accessible. -When the InterLink is fully deprovisioned on both sides, it will be deleted from the list of your InterLinks, and its Overview page will no longer be accessible. + **Self-hosted InterLinks only**: [Contact sales](https://www.scaleway.com/en/contact-sales/) if you want to deprovision your dedicated physical connection. diff --git a/pages/interlink/how-to/order-interlink.mdx b/pages/interlink/how-to/order-interlink.mdx index f95e0d0022..279e4254b2 100644 --- a/pages/interlink/how-to/order-interlink.mdx +++ b/pages/interlink/how-to/order-interlink.mdx @@ -1,66 +1,78 @@ --- title: How to order an InterLink -description: Learn how to order a hosted InterLink connection to your Scaleway cloud infrastructure via your chosen partner. Step-by-step guide included. +description: Learn how to create an InterLink to connect your external infrastructure to your Scaleway cloud, either hosted by a partner or self-hosted with your own physical connection. Step-by-step guide included. dates: - validation: 2025-03-18 + validation: 2025-09-30 posted: 2025-03-18 -tags: interlink direct-connect order hosted partner pop location +tags: interlink direct-connect order hosted partner pop location self-hosted dedicated --- import Requirements from '@macros/iam/requirements.mdx' -import image from './assets/scaleway-interlink-diag-simple.webp' -import image2 from './assets/scaleway-order-interlink.webp' -import image3 from './assets/scaleway-interlink-ordering.webp' +import scalewayInterlinkDiagSimple from './assets/scaleway-interlink-diag-simple.webp' +import scalewayOrderInterlinkWebp from './assets/scaleway-order-interlink.webp' +import scalewayHostedInterlinkOrdering from './assets/scaleway-hosted-interlink-ordering.webp' +import scalewaySelfHostedInterlinkOrdering from './assets/scaleway-self-hosted-interlink-ordering.webp' - -InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/). - - InterLink is Scaleway's product to let you create a secure, private connection between your external infrastructure, and your Scaleway VPC. This allows you to direct your traffic safely from your Scaleway infrastructure to your on-premises infrastructure, away from the public internet. -Currently, InterLink is available in **hosted** version only. This means that you must choose a compatible [partner](/interlink/concepts/#partner) to facilitate the physical connection between the external infrastructure and the Scaleway VPC. +InterLink is available in two versions: + +- Hosted: The physical connection is provided by a [partner](/interlink/concepts/#partner) and shared between several users +- Self-hosted: The physical connection is provisioned by and dedicated to a single customer - + -This guide takes you through the process of ordering an InterLink via the Scaleway console. +This guide takes you through the process of creating an InterLink via the Scaleway console. - 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 -## How to order an InterLink +## How to create an InterLink 1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. If you have not already created an InterLink, the product ordering page is displayed. -2. Click **Order InterLink**. The order wizard displays. +2. Click **Create InterLink**. The creation wizard displays. - + -3. Select a [connection type](/interlink/concepts/#connection-type), the type of physical InterLink connection. For now, only **hosted** connections are available. +3. Choose a [region](/interlink/concepts/#region) for your InterLink. This must correspond to the Scaleway VPC you want to attach later. -4. Select a [partner](/interlink/concepts/#partner). To establish an InterLink connection via a partner, generally you must be a client of that partner, e.g. with your infrastructure in their datacenter, or on your own premises using the partner as a network provider. [Get help with choosing a partner](/interlink/reference-content/overview/#hosted-interlinks). +4. Select a [physical connection type](/interlink/concepts/#connection-type) for your InterLink, either [hosted](/interlink/reference-content/overview/#hosted-interlinks) or [self-hosted](/interlink/reference-content/overview/#hosted-interlinks). -5. Choose a [region](/interlink/concepts/#region) for your InterLink. This must correspond to the Scaleway VPC you want to attach later. +5. Select the following options, depending on your physical connection type: -6. Choose a [location](/interlink/concepts/#location) for your InterLink. This represents the physical location where the connection to Scaleway's network will be established. + + + + Select a [partner](/interlink/concepts/#partner). To establish an InterLink connection via a partner, generally you must be a client of that partner, e.g. with your infrastructure in their datacenter, or on your own premises using the partner as a network provider. [Get help with choosing a partner](/interlink/reference-content/overview/#hosted-interlinks). + -7. Choose a [bandwidth](/interlink/concepts/#bandwidth) amount. This represents the maximum bandwidth that will be available over the InterLink. + Also select the [location](/interlink/concepts/#location) for your InterLink. This represents the physical location where the connection to Scaleway's network will be established. -8. Enter a name and optional tags for your InterLink. + + Select a [dedicated connection](/interlink/concepts/#dedicated-physical-connection). The InterLink will be hosted over this connection. You must have already provisioned this connection via the Scaleway sales team. [Contact sales](https://www.scaleway.com/en/contact-sales/) if you would like to provision a dedicated connection: this cannot be done via the Scaleway console or API. + + + + +6. Choose a [bandwidth](/interlink/concepts/#bandwidth) amount. This represents the maximum bandwidth that will be available over the InterLink. -9. Check the estimated cost for your InterLink. Note that Scaleway will start billing you for the InterLInk as soon as you order it. You must then wait for your partner to provision the connection, who may charge you additional fees. +7. Attach up to two [routing policies](/interlink/concepts/#routing-policy). InterLink needs a policy for each IP traffic type it should route: all routes are blocked except those whitelisted in the policy(ies). Alternatively, skip this step and attach routing policies later. -10. Click **Order InterLink**. +8. Enter a name and optional tags for your InterLink. -Your InterLink is ordered, and its status briefly shows as `Configuring`, then `Requested`. **You must now contact your chosen partner to request they provision your InterLink from their end.** +9. Click **Create InterLink**. - +- **Hosted InterLink**: You must now contact your chosen partner to request they provision your InterLink from their end. Note that Scaleway starts billing you for the InterLink as soon as you create it, and your partner may charge you additional fees once provisioned on their end. For full details of the provisioning process, including how to contact your partner and what other steps you need to take, see the page [How to complete hosted InterLink provisioning](/interlink/how-to/complete-provisioning/). + -For full details of the provisioning process, including how to contact your partner and what other steps you need to take, see the page [How to complete InterLink provisioning](/interlink/how-to/complete-provisioning/). +- **Self-hosted InterLinks**: Your InterLink is now fully created. However, you must complete InterLink setup on the customer side by configuring your network device. For full details, see [How to complete self-hosted InterLink setup](/interlink/how-to/configure-interlink/#how-to-set-up-your-network-device-self-hosted-only) + -If you see a `Failed` status, it means there was a configuration error on the Scaleway side as we attempted to create the InterLink. Our technical team is automatically made aware of such a problem, and will intervene to resolve it. When the problem is resolved, the InterLink should automatically move to `Requested` status, and you can proceed to [completing provisioning](/interlink/how-to/complete-provisioning/). If you have any concerns, open a support ticket. +If your InterLink has a `Failed` status, it means there was a configuration error on the Scaleway side as we attempted to create the InterLink. Our technical team is automatically made aware of such a problem, and will intervene to resolve it. If you have any concerns, open a support ticket. diff --git a/pages/interlink/index.mdx b/pages/interlink/index.mdx index 39e53d18f9..1c3d379d93 100644 --- a/pages/interlink/index.mdx +++ b/pages/interlink/index.mdx @@ -5,8 +5,8 @@ description: Dive into Scaleway InterLink with our quickstart guides, how-tos, t - InterLink is now available in [Public Beta](https://www.scaleway.com/en/betas/). Check it out on the [Scaleway console](https://console.scaleway.com/interlink/) or [API](https://www.scaleway.com/en/developers/api/interlink/), and order your InterLink today. + title="Self-hosted InterLink now available"> + You can now create self-hosted InterLinks without a partner, by provisioning your own dedicated physical connection to Scaleway's router. Find out more in our [dedicated documentation](/interlink/reference-content/overview/#self-hosted-interlink). -InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/). - - InterLink is Scaleway's product to let you create a secure, private connection between your external infrastructure, and your Scaleway VPC. This allows you to direct your traffic safely from your Scaleway infrastructure to your on-premises infrastructure, away from the public internet. - + - 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 -## How to order an InterLink - - +## How to create an InterLink 1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. If you have not already created an InterLink, the product ordering page is displayed. -2. Click **Order InterLink**. The order wizard displays. +2. Click **Create InterLink**. The creation wizard displays. + + + +3. Choose a [region](/interlink/concepts/#region) for your InterLink. This must correspond to the Scaleway VPC you want to attach later. + +3. Select a [physical connection type](/interlink/concepts/#connection-type) for your InterLink, either [hosted](/interlink/reference-content/overview/#hosted-interlinks) or [self-hosted](/interlink/reference-content/overview/#self-hosted-interlink). - +4. Select the following options, depending on your physical connection type: -3. Select a [connection type](/interlink/concepts/#connection-type), the type of physical InterLink connection. For now, only **hosted** connections are available. + + + + Select a [partner](/interlink/concepts/#partner). To establish an InterLink connection via a partner, generally you must be a client of that partner, e.g. with your infrastructure in their datacenter, or on your own premises using the partner as a network provider. [Get help with choosing a partner](/interlink/reference-content/overview/#hosted-interlinks). + + + Also select the [location](/interlink/concepts/#location) for your InterLink. This represents the physical location where the connection to Scaleway's network will be established. -4. Select a [partner](/interlink/concepts/#partner) to facilitate the physical connection between the external infrastructure and the Scaleway VPC. Generally, you must be client of the chosen partner, e.g. with your infrastructure in their datacenter, or on your own premises using the partner as a network provider. [Get help with choosing a partner](/interlink/reference-content/overview/#hosted-interlinks). + + Select a [dedicated connection](/interlink/concepts/#dedicated-physical-connection). The InterLink will be hosted over this connection. You must have already provisioned this connection via the Scaleway sales team. [Contact sales](https://www.scaleway.com/en/contact-sales/) if you would like to provision a dedicated connection: this cannot be done via the Scaleway console or API. + + + -5. Choose a [region](/interlink/concepts/#region) for your InterLink. This must correspond to the Scaleway VPC you want to attach later. +5. Choose a [bandwidth](/interlink/concepts/#bandwidth) amount. This represents the maximum bandwidth that will be available over the InterLink. -6. Choose a [location](/interlink/concepts/#location) for your InterLink. This represents the physical location where the connection to Scaleway's network will be established. +6. Attach up to two [routing policies](/interlink/concepts/#routing-policy). InterLink needs a policy for each IP traffic type it should route: all routes are blocked except those whitelisted in the policy(ies). Alternatively, skip this step and attach routing policies later. -7. Choose a [bandwidth](/interlink/concepts/#bandwidth) amount. This represents the maximum bandwidth that will be available over the InterLink. +7. Enter a name and optional tags for your InterLink. -8. Enter a name and optional tags for your InterLink. +8. Click **Create InterLink**. -9. Check the estimated cost for your InterLink. Note that Scaleway will start billing you for the InterLInk as soon as you order it. You must then wait for your partner to provision the InterLink, who may charge you additional fees. +- **Hosted InterLink**: You must now contact your chosen partner to request they provision your InterLink from their end. Note that Scaleway starts billing you for the InterLink as soon as you create it, and your partner may charge you additional fees once provisioned on their end. For full details of the provisioning process, including how to contact your partner and what other steps you need to take, see the page [How to complete hosted InterLink provisioning](/interlink/how-to/complete-provisioning/). + -10. Click **Order InterLink**. +- **Self-hosted InterLinks**: Your InterLink is now fully created. However, you must complete InterLink setup on the customer side by configuring your network device. For full details, see [How to complete self-hosted InterLink setup](/interlink/how-to/configure-interlink/#how-to-set-up-your-network-device-self-hosted-only) + -Your InterLink is ordered, and its status briefly shows as `Configuring`, then `Requested`. **You must now contact your chosen partner to request they provision your InterLink from their end.** +## How to complete hosted InterLink provisioning. -## How to complete InterLink provisioning. + +**These steps apply to hosted InterLink's (via partners) only.** For self-hosted InterLinks, continue to [how to configure your InterLink](#how-to-configure-your-interlink) + 1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your InterLinks displays. 2. Click on the InterLink that you want to finish provisioning. The InterLink's **Overview** page displays. - - 3. Note down the [pairing key](/interlink/concepts/#pairing-key) for your InterLink. This is a unique identification number which the partner will need in order to provision your InterLink. 4. Contact your partner. After [creating your InterLink order](/interlink/how-to/order-interlink/), either their online portal URL, or their email address was displayed to you for this purpose. Use the relevant method to contact your partner, provide the pairing key, and request that they provision your InterLink from their side. @@ -78,8 +89,6 @@ You can also use the [Get a partner](https://www.scaleway.com/en/developers/api/ Your InterLink will remain in `Requested` status until the partner responds to your request. You can keep track of your InterLink's [status](/interlink/reference-content/statuses/) via the [InterLink listing](https://console.scaleway.com/interlink/links) in the Scaleway console. - - When the partner approves your request, the InterLink moves to `Provisioning` status. This means that the partner has agreed to facilitate your InterLink, and is now preparing the resources and configuration necessary to do so. When the partner has finished provisioning your InterLink, it moves to `Active` status. This indicates that the physical link and necessary accompanying configuration has been completed on the partner's side, and your InterLink is ready for use. @@ -92,7 +101,7 @@ If you experience any unexpected statuses, refer to our [information page on Int After your InterLink has been provisioned, a number of configuration steps are necessary to enable traffic to flow over the InterLink. - + ### How to attach a VPC @@ -102,11 +111,11 @@ Attaching an InterLink to a VPC allows you to complete the connection from your 2. Click on the InterLink that you want to configure. The InterLink's **Overview** page displays. - + 3. In the **Attached VPC** section, click **Attach VPC**. A pop-up displays: - + 4. Select one of your existing VPCs from the dropdown list. It must be in the same region as the InterLink. Alternatively, click **+ Create VPC** to create and attach a new VPC. @@ -124,7 +133,7 @@ After attaching a VPC, the next step in configuring your InterLink is to create The VPC and the external infrastructure's routers both announce their routes to each other via [BGP](/interlink/concepts/#border-gateway-protocol-bgp) when route propagation is activated, but all of these routes are blocked by default. Routing policies let you whitelist ranges of route announcements to allow, so that traffic can flow along these routes across the InterLink. -Each InterLink can have one routing policy attached to it, but a single routing policy can be attached to multiple InterLinks, if desired. +An InterLink must have a **minimum of one** and a **maximum of two** attached routing policies, one for each IP traffic type to be routed (IPv4 and/or IPv6). See the dedicated documentation on [creating a routing policy](/interlink/how-to/create-routing-policy/), then follow these instructions to attach it: @@ -134,7 +143,7 @@ See the dedicated documentation on [creating a routing policy](/interlink/how-to 3. In the **Route propagation** section, click **Attach routing policy**. A pop-up displays. - + 4. Select a routing policy from the drop-down list, and click **Attach list**. @@ -142,11 +151,28 @@ See the dedicated documentation on [creating a routing policy](/interlink/how-to Make sure that the routing policy is suitable for the incoming routes (announced by the Scaleway VPC) and outgoing routes (announced by the external infrastructure) that should be propagated on this InterLink. -The policy is attached, ad you are returned to the InterLink's **Overview** page. +Repeat the process to attach up to two routing policies in total (one for IPv4 and one for IPv6). + +## How to set up your network device (self-hosted only) + + +This step is necessary for [self-hosted InterLinks](/interlink/reference-content/overview/#self-hosted-interlink) only. If you have a hosted InterLink, provisioned via a partner, you do not need to set up a network device. + + +You must configure the real physical or software-based networking device, located on the remote network you are connecting to your Scaleway VPC via the InterLink. You will need the following information, which is available from your InterLink's **Overview** screen in the Scaleway console: + +- **Scaleway ASN** (12876) +- **VLAN ID** for the InterLink + +You also need to set up route announcements and filters on the customer side. For this, you will need the following information, also available from the InterLink's **Overview** screen. +Et j'av +- **BGP interconnection subnet(s)**: The private subnet used for the VPC and external infrastructure to establish a BGP session and exchange routing information. For InterLinks that have both IPv4 and IPv6 routing policies, one IPv4 and one IPv6 subnet will be provided. + +- **Routing policy**: Take into account the routing policy(ies) you attached to the connection, when configuring routing policy on the customer gateway device. ### How to activate route propagation -Once you have attached a VPC and attached a routing policy, you can activate route propagation. This is the final step in configuring your InterLink so that traffic can flow between the VPC and your external infrastructure: it triggers the dynamic exchange of route information between the VPC and external infrastructure. +Once you have attached a VPC, attached routing policies and (for self-hosted InterLinks) set up your network device, you can activate route propagation. This is the final step in configuring your InterLink so that traffic can flow between the VPC and your external infrastructure: it triggers the dynamic exchange of route information between the VPC and external infrastructure. 1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your InterLinks displays. @@ -154,38 +180,32 @@ Once you have attached a VPC and attached a routing policy, you can activate rou 3. In the **Route propagation** section, use the toggle to turn route propagation **ON**. - A pop-up displays, showing the attached routing policy which will define the incoming and outgoing route announcements to accept. You can change the attached routing policy if you wish. - - It is not possible to activate route propagation without attaching a routing policy, as all route announcements would be blocked, rendering the action ineffective. + A pop-up displays, confirming that the action will launch the BGP session(s) and allow traffic to flow over the InterLink, via the routes whitelisted in the attached routing policy(ies). 4. Click **Activate route propagation**. Route propagation is activated, and you are returned to your InterLink's overview page. - While route propagation remains active, traffic can flow across the routes allowed over the InterLink. The VPC and external infrastructure will dynamically exchange and update route information. You can deactivate route propagation at any time: if you do so, all routes are blocked and no traffic can flow. + While route propagation remains active, traffic can flow across the routes allowed by the routing policy(ies). The VPC and external infrastructure will dynamically exchange and update route information. You can deactivate route propagation at any time: if you do so, all routes are blocked and no traffic can flow. ## How to delete an InterLink -You can delete your InterLink at any time. Action is required on both the Scaleway side and the partner side to completely deprovision the InterLink. Follow the steps below. - 1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your InterLinks displays. 2. Click on the InterLink that you want to delete. The InterLink's **Overview** page displays. 3. [Deactivate route propagation](/interlink/how-to/configure-interlink/#how-to-deactivate-route-propagation). -4. In the **Delete InterLink** panel, click **Delete InterLink**. - - A pop-up displays, confirming that this action will permanently delete your InterLink on the Scaleway side. +4. In the **Delete InterLink** panel, click **Delete InterLink**, and confirm when prompted. -5. Type **DELETE** in the box, and click **Delete InterLink**. + Scaleway stops billing you for your InterLink at this point, and it can no longer be configured, un-deleted, or used to route traffic. - You are returned to the InterLink's **Overview** page, where its status now shows as **Deprovisioning**. Scaleway stops billing you for your InterLink at this point, and it can no longer be configured, un-deleted, or used to route traffic. +6. **Hosted InterLinks only**: Contact your partner to request that they delete the InterLink resource on their side. They may continue to bill you until you do so, and they deprovision the resource on their side. To get in touch with the partner, you can use the same contact information that you used when [requesting the InterLink from the partner](/interlink/how-to/complete-provisioning/). -6. Contact your partner to request that they delete the InterLink resource on their side. They may continue to bill you until you do so, and they deprovision the resource on their side. To get in touch with the partner, you can use the same contact information that you used when [requesting the InterLink from the partner](/interlink/how-to/complete-provisioning/). + + If the provisioning of your InterLink by the partner was never completed, e.g. you a) never contacted the partner to request provisioning of the InterLink, or b) the partner refused to provision your InterLink, you do not need to contact the partner again to request that they deprovision the resource. Deleting it on the Scaleway side is sufficient. + - -If the provisioning of your InterLink by the partner was never completed, e.g. you a) never contacted the partner to request provisioning of the InterLink, or b) the partner refused to provision your InterLink, you do not need to contact the partner again to request that they deprovision the resource. Deleting it on the Scaleway side is sufficient. - + When the InterLink is fully deprovisioned on both sides, it will be deleted from the list of your InterLinks, and its Overview page will no longer be accessible. -When the InterLink is fully deprovisioned on both sides, it will be deleted from the list of your InterLinks, and its Overview page will no longer be accessible. + **Self-hosted InterLinks only**: [Contact sales](https://www.scaleway.com/en/contact-sales/) if you want to deprovision your dedicated physical connection. \ No newline at end of file diff --git a/pages/interlink/reference-content/assets/scaleway-hosted-interlink-ordering.webp b/pages/interlink/reference-content/assets/scaleway-hosted-interlink-ordering.webp new file mode 100644 index 0000000000..e992d83020 Binary files /dev/null and b/pages/interlink/reference-content/assets/scaleway-hosted-interlink-ordering.webp differ diff --git a/pages/interlink/reference-content/assets/scaleway-interlink-config.webp b/pages/interlink/reference-content/assets/scaleway-interlink-config.webp index 6454339bc6..05ef46f4c5 100644 Binary files a/pages/interlink/reference-content/assets/scaleway-interlink-config.webp and b/pages/interlink/reference-content/assets/scaleway-interlink-config.webp differ diff --git a/pages/interlink/reference-content/assets/scaleway-interlink-ordering.webp b/pages/interlink/reference-content/assets/scaleway-interlink-ordering.webp deleted file mode 100644 index 6d06561261..0000000000 Binary files a/pages/interlink/reference-content/assets/scaleway-interlink-ordering.webp and /dev/null differ diff --git a/pages/interlink/reference-content/bgp-communities.mdx b/pages/interlink/reference-content/bgp-communities.mdx index 0edbfe51ef..a380651fcf 100644 --- a/pages/interlink/reference-content/bgp-communities.mdx +++ b/pages/interlink/reference-content/bgp-communities.mdx @@ -3,13 +3,13 @@ title: Using BGP communities with InterLink description: Learn how to use BGP communities to set local preference for incoming traffic via Scaleway InterLink. tags: interlink configuration border-gateway-protocol bgp-tags local-preference local-pref dates: - validation: 2025-03-26 + validation: 2025-09-30 posted: 2025-03-26 --- A **B**order **G**ateway **P**rotocol (BGP) community is a group of IP prefixes that share a common attribute. -Scaleway recognizes three BGP communities, and applies routing priorities based on the community applied. This lets you influence routing between the various Interlinks in a VPC, for traffic flowing from Scaleway to your external network. +Scaleway recognizes three BGP communities, and applies routing priorities based on the community applied. This lets you influence routing between the various InterLinks in a VPC, for traffic flowing from Scaleway to your external network. For each prefix that you advertise from your external/on-premises router over a BGP session, you can apply one of the following community tags to indicate the priority of the associated path for returning traffic: diff --git a/pages/interlink/reference-content/configuring.mdx b/pages/interlink/reference-content/configuring.mdx index fff55cf499..528c0a95d0 100644 --- a/pages/interlink/reference-content/configuring.mdx +++ b/pages/interlink/reference-content/configuring.mdx @@ -3,33 +3,31 @@ title: Configuring an InterLink description: Find out how to set up your Scaleway InterLink so that traffic can flow between your external infrastructure and your Scaleway resources. Understand how to attach a VPC, create a routing policy to whitelist route announcements, and activate route propagation across the connection. tags: interlink configuration attach-vpc whitelist route-range ip-prefix route-propagation dates: - validation: 2025-03-18 + validation: 2025-09-30 posted: 2024-10-24 --- -import image from './assets/scaleway-interlink-config.webp' +import scalewayInterlinkConfig from './assets/scaleway-interlink-config.webp' - -InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/). - - -Once your InterLink has been created and the [provisioning process](/interlink/reference-content/provisioning/) is complete, you must complete a number of configuration steps to enable traffic to flow across the InterLink. +Once your InterLink has been created and (for hosted InterLinks) the [partner provisioning process](/interlink/reference-content/provisioning/) is complete, you must complete a number of configuration steps to enable traffic to flow across the InterLink. This document explains the process in full, and gives tips for troubleshooting any potential issues. ## Configuration overview - + -The diagram above shows the four configuration steps necessary for an InterLink. Only when all steps have been completed can traffic flow across the InterLink, connecting the Scaleway VPC to the external (on-premises) infrastructure. +The diagram above shows the configuration steps necessary for an InterLink. Only when all steps have been completed can traffic flow across the InterLink, connecting the Scaleway VPC to the external (on-premises) infrastructure. Read more about each step, and possible errors at each stage, in the following sections. ### 1. Create the InterLink -Creating an InterLink is itself a multi-step process, that requires action on both the Scaleway side, and on the partner side. This process is explained in full in [Provisioning an InterLink](/interlink/reference-content/provisioning/). +Creating an InterLink is itself a multi-step process: +- **Hosted InterLinks**: [Order the dedicated physical connection](/concepts/#dedicated-physical-connection) from the Scaleway sales team, then [create the InterLink](/interlink/how-to/order-interlink/) via the Scaleway console or developer tools, specifying the dedicated physical connection to use. +- **Self hosted InterLink**: [Create the InterLink](/interlink/how-to/order-interlink/) via the Scaleway console or developer tools, then follow the multi-step process that requires action on both the Scaleway side, and on the partner side. This process is explained in full in [Provisioning an InterLink](/interlink/reference-content/provisioning/). -You must wait until the InterLink has reached `Active` [status](/interlink/reference-content/statuses/) before you can continue with the following configuration steps. +You must wait until the InterLink has reached `Active` or `Ready` [status](/interlink/reference-content/statuses/) before you can continue with the following configuration steps. ### 2. Attach VPC @@ -41,7 +39,7 @@ Follow the instructions for [attaching a VPC via the console](/interlink/how-to/ ### 3. Attach routing policy -InterLink uses [**B**order **G**ateway **P**rotocol](https://en.wikipedia.org/wiki/Border_Gateway_Protocol) to exchange routing information between the customer’s infrastructure and the Scaleway VPC. Each side advertises IP prefixes for its own internal subnets and resources, to allow the other side to dynamically learn and update its internal routes, facilitating efficient traffic flow. However, by default, **all routes across an InterLink are blocked**. You must create and attach a [routing policy](/interlink/concepts/#routing-policy) aka routing policy, to set IP prefix filters for the route advertisements you want to whitelist. This facilitates traffic flow across the InterLink. +InterLink uses [**B**order **G**ateway **P**rotocol](https://en.wikipedia.org/wiki/Border_Gateway_Protocol) to exchange routing information between the customer’s infrastructure and the Scaleway VPC. Each side advertises IP prefixes for its own internal subnets and resources, to allow the other side to dynamically learn and update its internal routes, facilitating efficient traffic flow. However, by default, **all routes across an InterLink are blocked**. You must create and attach a [routing policy](/interlink/concepts/#routing-policy) for each IP traffic type (IPv4 and/or IPv6), to set IP prefix filters for the route advertisements you want to whitelist. This facilitates traffic flow across the InterLink. Follow the instructions and tips for [creating a routing policy](/interlink/how-to/create-routing-policy/), via the console. Alternatively, you can [create](https://www.scaleway.com/en/developers/api/interlink/#path-routing-policies-create-a-routing-policy) and [attach](https://www.scaleway.com/en/developers/api/interlink/#path-links-attach-a-routing-policy) routing policies via the API. @@ -49,7 +47,7 @@ See our dedicated documentation on using [BGP communities](/interlink/reference- ### 4. Activate route propagation -Once you have attached a VPC and defined the routing policy, you must activate route propagation to allow traffic to flow over the InterLink. This enables all prefixes whitelisted in your routing policy to be announced in the BGP session, so that traffic can flow along these routes. See the documentation for activating route propagation via the [API](https://www.scaleway.com/en/developers/api/interlink/#path-links-enable-route-propagation) or the [console](/interlink/how-to/configure-interlink/#how-to-activate-route-propagation) +Once you have attached a VPC and attached the routing policy(ies), you must activate route propagation to allow traffic to flow over the InterLink. This launches the BGP session between the two routers, so that all prefixes whitelisted in your routing policy can be announced and traffic can flow along these routes. See the documentation for activating route propagation via the [API](https://www.scaleway.com/en/developers/api/interlink/#path-links-enable-route-propagation) or the [console](/interlink/how-to/configure-interlink/#how-to-activate-route-propagation) Even when route propagation is activated, remember that all routes are blocked by default. It is essential to attach a routing policy to the InterLink to allow traffic to flow. diff --git a/pages/interlink/reference-content/overview.mdx b/pages/interlink/reference-content/overview.mdx index 60049ef3af..27a1b9703e 100644 --- a/pages/interlink/reference-content/overview.mdx +++ b/pages/interlink/reference-content/overview.mdx @@ -3,26 +3,22 @@ title: InterLink - Technical overview description: Dive deeper into understanding Scaleway's InterLink product, with technical diagrams, explanations and more. tags: interlink pop infrastructure diagram technical overview dates: - validation: 2025-03-18 + validation: 2025-09-30 posted: 2024-10-24 --- -import image from './assets/scaleway-interlink-diag-simple.webp' -import image2 from './assets/scaleway-interlink-diag-tech.webp' +import scalewayInterlinkDiagSimple from './assets/scaleway-interlink-diag-simple.webp' +import scalewayInterlinkDiagTech from './assets/scaleway-interlink-diag-tech.webp' - -InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/). - - InterLink is Scaleway's product to let you create a secure, private connection between your external infrastructure, and your Scaleway VPC. This allows you to direct your traffic safely from your Scaleway infrastructure to your on-premises infrastructure, away from the public internet. Compared to a typical internet-based VPN, an InterLink is more reliable, more secure and offers lower latency. At its simplest level, InterLink can be understood as a configurable connection between your own infrastructure, and your Scaleway VPC. You can configure details such as available bandwidth, and the routing policy between the two peers: - + ## Types of InterLink -Scaleway plans to offer two types of InterLink, though currently only the **hosted** type is available. +Two types of InterLink are available, depending on how you want to provision the physical connection between the external infrastructure and the Scaleway VPC: **hosted** or **self-hosted**. ### Hosted InterLinks @@ -39,15 +35,29 @@ The diagram below shows the architecture of a hosted InterLink. Note that three - The partner's router connects directly to the customer's on-premises infrastructure via a last-mile connection facilitated by the partner. - The customer's infrastructure is hosted in the partner's datacenter, and connects to the partner's router directly. - + ### Self-hosted InterLink -A self-hosted InterLink is provisioned, where the customer gets sole use of a single InterLink port on Scaleway's router, with the entire bandwidth of that port. The customer can use available bandwidth of this dedicated physical connection to provision several InterLinks for themselves. This type of InterLink is not yet available at Scaleway - [contact a sales representative](https://www.scaleway.com/en/contact-sales/) to register your interest. +The customer creates an InterLink using their own dedicated physical connection, where they get sole use of a single InterLink port on Scaleway's router. This connection and its bandwidth can then be used to provision several InterLinks for themselves. + +Self-hosted InterLinks enable you to bypass third-party partners for financial, privacy or compliance reasons, or to take advantage if your router is already colocated with one of Scaleway's locations. + +To provision your own dedicated physical connection, [contact a sales representative](https://www.scaleway.com/en/contact-sales/). Connections cannot be provisioned via the Scaleway console. + +Once the dedicated physical connection is provisioned, you can [create your InterLink](#creating-an-interlink) via the Scaleway console or developer tools, specifying the dedicated connection to be used. + +You must be able to [configure your network device](/interlink/how-to/configure-interlink/#how-to-set-up-your-network-device-self-hosted-only) for InterLink. Otherwise, the configuration process is the same as for hosted InterLinks. + +## Creating an InterLink + +InterLinks can be created via the Scaleway console or our developer tools. + +For hosted InterLinks, after creation on the Scaleway side, specific action is required from the customer and the selected partner in order to successfully complete the provisioning process. -## Provisioning an InterLink +For self-hosted InterLinks, you must have already provisioned a dedicated physical connection before starting the InterLink creation process. Once the InterLink is created, you will need to [configure your network device](/interlink/how-to/configure-interlink/#how-to-set-up-your-network-device-self-hosted-only). -Provisioning an InterLink is a multi-step process. As only hosted InterLinks (via partners) are currently available, specific action is required from Scaleway, the customer, and the selected partner in order to successfully complete the provisioning process. See our dedicated page on [provisioning an InterLink](/interlink/reference-content/provisioning/) for full details. +See our dedicated page on [provisioning an InterLink](/interlink/reference-content/provisioning/) for full details. ## Attaching a VPC @@ -67,7 +77,7 @@ When both BGP sessions are up, the InterLink has `Active` status. If one BGP ses ### Routing policies -By default, **all route announcements from both sides are blocked** by InterLink. This is part of a safety-net mechanism to allow customers to efficiently and safely control traffic flow across the link. You must create and attach a [routing policy](/interlink/concepts/#routing-policy), to specify the IP prefix announcements to whitelist from each side. This is step one of two in allowing traffic to flow across the InterLink. See the [configuration](/interlink/reference-content/configuring/) page for more information on routing policies. +By default, **all route announcements from both sides are blocked** by InterLink. This is part of a safety-net mechanism to allow customers to efficiently and safely control traffic flow across the link. You must create and attach a [routing policy](/interlink/concepts/#routing-policy) for each traffic type (IPv4 and/or IPv6), to specify the IP prefix announcements to whitelist from each side. This is step one of two in allowing traffic to flow across the InterLink. See the [configuration](/interlink/reference-content/configuring/) page for more information on routing policies. ### Route propagation diff --git a/pages/interlink/reference-content/provisioning.mdx b/pages/interlink/reference-content/provisioning.mdx index 7a658bab80..8a7db7e420 100644 --- a/pages/interlink/reference-content/provisioning.mdx +++ b/pages/interlink/reference-content/provisioning.mdx @@ -1,38 +1,38 @@ --- -title: Provisioning an InterLink -description: Get help with understanding all the different stages of ordering and provisioning a Scaleway InterLink, from placing the initial order, to dealing with error messages, and deleting the resource if no longer needed. +title: Provisioning a hosted InterLink +description: Get help with understanding all the different stages of ordering and provisioning a hosted Scaleway InterLink, from placing the initial order, to dealing with error messages, and deleting the resource if no longer needed. tags: interlink provision order steps partner process error dates: - validation: 2025-03-18 + validation: 2025-09-30 posted: 2024-10-24 --- -import image from './assets/scaleway-interlink-diag-tech.webp' -import image2 from './assets/scaleway-interlink-ordering.webp' +import scalewayInterlinkDiagTech from './assets/scaleway-interlink-diag-tech.webp' +import scalewayHostedInterlinkOrdering from './assets/scaleway-hosted-interlink-ordering.webp' -InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/). +This page concerns the provisioning process for **hosted** InterLinks only. For self-hosted InterLinks, you must first [contact the sales team](https://www.scaleway.com/en/contact-sales/) to provision a dedicated physical connection, then follow the instructions [here](/interlink/how-to/order-interlink/) to create your InterLink(s) using the connection. -The process of ordering an InterLink has multiple stages: action is required both from Scaleway, the user, and from the selected [partner](/interlink/concepts/#partner). When preparing your InterLink order, you must choose appropriate location (aka **P**oint **o**f **P**resence), partner and region settings to ensure compatibility with your external and Scaleway infrastructure. +The process of ordering a hosted InterLink has multiple stages: action is required both from Scaleway, the user, and from the selected [partner](/interlink/concepts/#partner). When preparing your InterLink order, you must choose appropriate location (aka **P**oint **o**f **P**resence), partner and region settings to ensure compatibility with your external and Scaleway infrastructure. - + This document explains the provisioning process in full, so you know what to expect when ordering an InterLink, what action is required from all parties, and how to deal with any potential errors. ## Provisioning overview - + -The diagram above shows the four steps necessary to provision an InterLink. Only when all steps have been completed will the InterLink move to an **Active** status, ready for traffic to flow. Read more about each step, and possible errors at each stage, in the following sections. +The diagram above shows the four steps necessary to provision a hosted InterLink. Only when all steps have been completed will the InterLink move to an **Active** status, ready for traffic to flow. Read more about each step, and possible errors at each stage, in the following sections. For full information about different statuses an InterLink might flow through, see our [dedicated documentation on InterLink statuses](/interlink/reference-content/statuses/). -### 1. User orders InterLink via Scaleway +### 1. User creates InterLink via Scaleway -The order process begins when you order an InterLink via the Scaleway [InterLink API](https://www.scaleway.com/en/developers/api/interlink/) or the [Scaleway console](/interlink/how-to/order-interlink/), or one of our other [developer tools](https://www.scaleway.com/en/developers/). When ordering, you set the following parameters: +The process begins when you create an InterLink via the Scaleway [InterLink API](https://www.scaleway.com/en/developers/api/interlink/) or 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**: In the long term, both hosted and self-hosted InterLinks will be available. For now, only **hosted** connections (facilitated via a partner) are available. +- **Connection type**: Hosted (via a partner). - **Partner**: The third-party service provider to facilitate the InterLink. A list of available partners is shown in the console, or for the API you can Use the [List available partners](https://www.scaleway.com/en/developers/api/interlink/#path-partners-list-available-partners) call. - **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. - **Location**: The physical **P**oint **o**f **P**resence (PoP) where the connection to Scaleway's network will be established, via the partner. @@ -40,14 +40,14 @@ The order process begins when you order an InterLink via the Scaleway [InterLink - **Name**: A name (and, optionally, tags) for the InterLink. -Scaleway starts charging for the InterLink as soon as your order is placed. You must then wait for the partner to provision the connection, and they may charge you additional fees. +Scaleway starts charging for the InterLink as soon as you create the InterLink on our side. You must then wait for the partner to provision the connection, and they may charge you additional fees. -Immediately after ordering, it is expected that your InterLink will briefly be in `Configuring` status, before moving to `Requested` status. See the [statuses documentation](/interlink/reference-content/statuses/) for help with resolving any error statuses. +Immediately after creation, it is expected that your InterLink will briefly be in `Configuring` status, before moving to `Requested` status. See the [statuses documentation](/interlink/reference-content/statuses/) for help with resolving any error statuses. ### 2. User requests InterLink from partner -After ordering the InterLink from Scaleway, you **must** contact your chosen partner to request that they provision the connection on their side. Scaleway is not able to automatically do this step for you. +After creating the InterLink with Scaleway, you **must** contact your chosen partner to request that they provision the connection on their side. Scaleway is not able to automatically do this step for you. See [how to contact partner](/interlink/how-to/complete-provisioning/#contact-partner-to-request-interlink) for full details. diff --git a/pages/interlink/reference-content/statuses.mdx b/pages/interlink/reference-content/statuses.mdx index 323531219c..a495a74108 100644 --- a/pages/interlink/reference-content/statuses.mdx +++ b/pages/interlink/reference-content/statuses.mdx @@ -3,13 +3,10 @@ title: Understanding InterLink statuses description: Find out what the different possible statuses of your InterLink mean, and how to take action based on these statuses when necessary. tags: interlink status dates: - validation: 2025-03-18 + validation: 2025-09-30 posted: 2024-10-24 --- - -InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/). - An InterLink always has a **status**, which can be retrieved via the API using the [Get a link](https://www.scaleway.com/en/developers/api/interlink/#path-links-get-a-link) call. @@ -18,14 +15,15 @@ This document explains the different statuses possible for an InterLink, and how | **Status** | **Description** | |-------------------|-----------------------------------------| | **Configuring** | InterLink is configuring and is in a transient state. No user actions can be carried out.

This status could occur immediately after creating your InterLink order, while Scaleway processes the order and configures the InterLink, or at any time when a new configuration is being applied. | -| **Requesting** | InterLink has been created successfully on the Scaleway side, provisioning must now be requested from the chosen partner.

You must contact your partner to request that they provision your InterLink. Either a contact email address, or a link to the partner’s portal is provided via the Scaleway API. Scaleway does not make the request to the partner, this is the responsibility of the user.

The InterLink will remain in `Requesting` status until the partner accepts the request, at which point it moves into `Provisioning` status. Alternatively, the partner may refuse the request, or the request may time out. | +| **Requesting** | The hosted InterLink has been created successfully on the Scaleway side, provisioning must now be requested from the chosen partner.

You must contact your partner to request that they provision your InterLink. Either a contact email address, or a link to the partner’s portal is provided via the Scaleway API. Scaleway does not make the request to the partner, this is the responsibility of the user.

The InterLink will remain in `Requesting` status until the partner accepts the request, at which point it moves into `Provisioning` status. Alternatively, the partner may refuse the request, or the request may time out. | | **Failed** | Scaleway was unable to create the InterLink.

This usually occurs when there is a configuration error on the Scaleway side while attempting to create the InterLink. Our technical team is automatically made aware of such a problem, and will intervene to resolve it. When the problem is resolved, the InterLink should move to `Requesting` status. Wait for technical intervention, or open a support ticket if you require further help. -| **Provisioning** | The partner has accepted the InterLink request, and is now provisioning it at their end.

The InterLink is not yet operational: traffic cannot yet flow. You must wait for the partner to finish provisioning. When provisioning is complete, the InterLink should move to `Active` status. | -| **Expired** | No response was received from the selected partner in the 10 days following the creation of the InterLink on the Scaleway side.

If Scaleway does not receive a response from the selected partner after 10 days, the InterLink moves to `Expired` status. It is not possible to take action to move this InterLink to a different status: you must delete the InterLink, and create a new order if you wish to try again. | -| **Refused** | The partner refused the request to provision the InterLink.

It is not possible to take action to move this InterLink to a different status: you must delete the InterLink, and create a new order if you wish to try again with a different partner or configuration. | -| **Active** | The InterLink is in a ready state, and traffic can flow.

The InterLink has been provisioned on both the Scaleway side and the partner side, and is now in an active state. Traffic can flow across the InterLink (presuming that routing policies, route propagation, and an attached VPC are correctly configured). | +| **Provisioning** | The partner has accepted the hosted InterLink request, and is now provisioning it at their end.

The InterLink is not yet operational: traffic cannot yet flow. You must wait for the partner to finish provisioning. When provisioning is complete, the InterLink should move to `Active` status. | +| **Expired** | No response was received from the selected partner in the 10 days following the creation of the hosted InterLink on the Scaleway side.

If Scaleway does not receive a response from the selected partner after 10 days, the InterLink moves to `Expired` status. It is not possible to take action to move this InterLink to a different status: you must delete the InterLink, and create a new order if you wish to try again. | +| **Refused** | The partner refused the request to provision the hosted InterLink.

It is not possible to take action to move this InterLink to a different status: you must delete the InterLink, and create a new order if you wish to try again with a different partner or configuration. | +| **Ready** | The self-hosted InterLink has been created and is ready to connect.

The tunnel(s) cannot be established because the customer network device is not yet successfully configured. | +| **Active** | The InterLink is in a ready state, and traffic can flow.

The InterLink has been provisioned on both the Scaleway side and (for hosted InterLinks) the partner side, and is now in an active state. Traffic can flow across the InterLink (presuming that routing policies, route propagation, and an attached VPC are correctly configured). | | **Limited Connectivity** | The InterLink is provisioned, but IP connectivity is limited.

This may be the case if either, but not both of, the BGP, IPv4, or IPv6 sessions are down. | -| **Down / All down** | The InterLink is provisioned, but there is no IP connectivity.

The InterLink has been provisioned successfully on both sides, but both BGP sessions (IPv4 and IPv6) are down and traffic cannot flow. Open a support ticket with Scaleway, or contact your partner. | +| **Down / All down** | The InterLink is provisioned, but there is no IP connectivity.

The InterLink has been provisioned and configured successfully on both sides, but both BGP sessions (IPv4 and IPv6) are down and traffic cannot flow. Open a support ticket with Scaleway, or contact your partner. | | **Locked** | The InterLink has been locked by the Trust and Safety team

You cannot carry out any actions on the InterLink. Open a support ticket. | -| **Deprovisioning** | Deletion of the InterLink has been initiated on either the partner side or the Scaleway side, but has not been finalized.

An InterLink must be deleted by both Scaleway and the partner in order to move to `Deleted` status. If you have deleted an InterLink on the Scaleway side, ensure you contact the partner separately to request that they delete the resource on their side. If you have deleted an InterLink on the partner side, ensure that you delete the resource on the Scaleway side. | -| **Deleted** | The InterLink has been deprovisioned by both Scaleway and the partner, and is now deleted. | \ No newline at end of file +| **Deprovisioning** | Deletion of the hosted InterLink has been initiated on either the partner side or the Scaleway side, but has not been finalized.

A hosted InterLink must be deleted by both Scaleway and the partner in order to move to `Deleted` status. If you have deleted a hosted InterLink on the Scaleway side, ensure you contact the partner separately to request that they delete the resource on their side. If you have deleted an InterLink on the partner side, ensure that you delete the resource on the Scaleway side. | +| **Deleted** | The InterLink has been deprovisioned (for hosted InterLinks, by both Scaleway and the partner), and is now deleted. | \ No newline at end of file