feat(interlink): continue

Author: RoRoJ

pages/interlink/concepts.mdx

@@ -4,7 +4,7 @@ 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-07-09
 ---
 import image from './assets/scaleway-interlink-diag-simple.webp'
 
@@ -27,30 +27,28 @@ 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 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
 
 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.
 
-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.
-
 <Lightbox image={image} alt="A diagram shows how a Scaleway VPC, to the left, can be attached to an InterLink, which then connects to external customer infrastructure." />
 
 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 +66,10 @@ 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)
+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 polic(ies) 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)

pages/interlink/faq.mdx

@@ -14,21 +14,21 @@ 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** 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).
 
 You can see available partners in the Scaleway console by opening the [InterLink order form](https://console.scaleway.com/interlink/links/order). More partners will be added to Scaleway InterLink as time goes on.
 
 ## 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** 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 [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?
 

pages/interlink/how-to/complete-provisioning.mdx

@@ -2,7 +2,7 @@
 title: How to complete 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-07-09
   posted: 2025-03-18
 tags: interlink direct-connect provision hosted partner contact error
 ---

pages/interlink/how-to/configure-interlink.mdx

@@ -2,7 +2,7 @@
 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-07-09
   posted: 2025-03-18
 tags: interlink direct-connect configure attach-vpc route-propagation allowed-routes routing-policy
 ---
@@ -102,14 +102,14 @@ This step is necessary for [self-hosted InterLinks](TODO) only. If you have a ho
 
 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
+- **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. 
 
-- 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.
+- **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
 

pages/interlink/how-to/create-routing-policy.mdx

@@ -2,7 +2,7 @@
 title: How to create a routing policy
 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: 2027-07-09
   posted: 2025-03-18
 tags: interlink direct-connect allowed-routes route-propagation whitelist range IP announcements BGP
 ---
@@ -13,7 +13,9 @@ import image from './assets/scaleway-create-routing-policy.webp'
 InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/).
 </Message>
 
-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.
+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.
+
+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,29 +29,29 @@ Learn more about routing across an InterLink in our [detailed overview](/interli
 
 3. Click **+Create routing policy**. The **Create a routing policy** wizard displays.
 
-        <Lightbox image={image} alt="In the Scaleway console, the create a routing policy wizard is displayed. There are 3 steps: 1. Choose a name and region, 2. Whitelist outgoing routes and 3. Whitelist incoming routes" />
+        <Lightbox image={image} alt="In the Scaleway console, the create a routing policy wizard is displayed. There are 3 steps: 1. Choose a name and region, 2. Whitelist outgoing routes and 3. Whitelist incoming routes" /> TODO UPDATE FROM CONSOLE
 
-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.
 
         <Message type="tip">
         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.
         </Message>
 
 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.
 
+4. Enter a name for the policy, or leave the randomly-generated name in place. Optionally, you can also add tags.
+
 8. 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-routing-policies) 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.
 
 <Message type="tip">
 See our dedicated documentation on using [BGP communities](/interlink/reference-content/bgp-communities/) to influence route priority for InterLink traffic.