fix(interlink): add links

Author: RoRoJ

network/interlink/concepts.mdx

@@ -14,6 +14,10 @@ categories:
   - networks
 ---
 
+<Message type="important">
+InterLink is currently in [Private Beta](https://www.scaleway.com/en/betas/), and only available to selected testers.
+</Message>
+
 ## Allowed routes list
 
 The default rule blocks any and all routes from being propagated over InterLink. Attaching an allowed routes list (aka **routing policy**) allows you to define the ranges of routes that should be whitelisted. When creating an allowed routes list, 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. 
@@ -34,7 +38,7 @@ Every InterLink has a defined bandwidth, representing the maximum data transfer
 
 ## 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.
+InterLink, currently in Private 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.
 

network/interlink/how-to/index.mdx

@@ -5,6 +5,13 @@ meta:
   noindex: true
 ---
 
+<Alert
+  sentiment="info"
+  title="InterLink is now in Private Beta"
+>
+  InterLink is currently available in [Private Beta](https://www.scaleway.com/en/betas/) only, for selected testers.
+</Alert>
+
 <ProductHeader 
    productName="InterLink"
    productLogo="interlink"
@@ -16,31 +23,17 @@ meta:
 ## Getting Started
 
 <Grid>
-    <SummaryCard
-        title="Quickstart"
-        icon="rocket"
-        description="Learn how to get started with InterLink."
-        label="View Quickstart"
-        url="/network/interlink/quickstart/"
-    />
     <SummaryCard
         title="Concepts"
         icon="info"
         description="Core concepts that give you a better understanding of InterLink."
         label="View Concepts"
         url="/network/interlink/concepts/"
-    />
-    <SummaryCard
-        title="How-tos"
-        icon="help-circle-outline"
-        description="Check our guides to creating and configuring an InterLink."
-        label="View How-tos"
-        url="/network/interlink/how-to/"
     />
         <SummaryCard
         title="Additional Content"
         icon="book-open-outline"
-        description="Go beyond the basics with detailed, in-depth guides to configuring InterLink."
+        description="Read our in-depth guides to provisioning and configuring your InterLink."
         label="Read more"
         url="/network/interlink/reference-content/"
     />

network/interlink/how-to/order-interlink.mdx

@@ -0,0 +1,66 @@
+---
+meta:
+  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 an allowed routes list to whitelist route announcements, and activate route propagation across the connection.
+  noindex: true
+content:
+  h1: Configuring an InterLink
+  paragraph: 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 an allowed routes list to whitelist route announcements, and activate route propagation across the connection.
+tags: interlink configuration attach-vpc whitelist route-range ip-prefix route-propagation
+categories: 
+  - interlink
+  - network
+dates:
+  validation: 2024-10-24
+  posted: 2024-10-24
+---
+
+<Message type="important">
+InterLink is currently in [Private Beta](https://www.scaleway.com/en/betas/), and only available to selected testers.
+</Message>
+
+Once your InterLink has been created and the [provisioning process](/network/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
+
+<Lightbox src="scaleway-interlink-config.webp" alt="A four step flow chart shows the following steps: 1. Create InterLink, 2. Attach VPC, 3. Attach allowed routes list, 4. Activate route propagation. After these steps are complete, traffic can flow across the InterLink" />
+
+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.
+
+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](/network/interlink/reference-content/provisioning/).
+
+You must wait until the InterLink has reached `Active` [status](/network/interlink/reference-content/statuses/) before you can continue with the following configuration steps.
+
+### 2. Attach VPC
+
+Attaching an InterLink to a VPC allows you to complete the connection from your external infrastructure, across the InterLink, to the Scaleway resources in the selected VPC.
+z
+The VPC must be in the same region region as the InterLink. An InterLink can only be attached to one VPC at a time, but you are free to detach the VPC and attach a different one whenever you like.
+
+You can use the [Attach a VPC](https://www.scaleway.com/en/developers/api/interlink/v1beta1/#path-links-attach-a-vpc) endpoint to attach a VPC to a given InterLink.
+
+### 3. Attach allowed routes list (routing policy)
+
+By default, all routes across an InterLink are blocked by default. You must create and attach an [allowed routes list](/network/interlink/concepts/#allowed-routes-list) aka routing policy, to set IP prefix filters for the routes you want to whitelist. This facilitates traffic flow across the InterLink.
+
+You can [create](https://www.scaleway.com/en/developers/api/interlink/v1beta1/#path-routing-policies-create-a-routing-policy) and [attach](https://www.scaleway.com/en/developers/api/interlink/v1beta1/#path-links-attach-a-routing-policy) allowed routes lists via the API.
+
+When setting the route ranges to whitelist, you must separately define the IP prefixes to accept from the external infrastructure (incoming ranges of route announcements to accept), and the IP prefix filters to advertise from the Scaleway VPC to the peer (outgoing ranges of routes to advertise). 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`.
+
+Only one allowed routes list (routing policy) can be attached to an InterLink at a given time. However, you can reuse the same list by attaching it to multiple InterLinks, for example if you have a second InterLink attached to the same VPC/external infrastructure for redundance purposes. You can update, delete or reattach a list at any time.
+
+### 4. Activate route propagation.
+
+Once you have attached a VPC and defined the routing policy/allowed routes, you must [activate route propagation](https://www.scaleway.com/en/developers/api/interlink/v1beta1/#path-links-enable-route-propagation) to allow traffic to flow over the InterLink. This enables all prefixes whitelisted in your allowed routes list / routing policy to be announced in the BGP session, so that traffic can flow along these routes. 
+
+<Message type="important">
+Even when route propagation is activated, remember that all routes are blocked by default. It is essential to attach a routing policy (aka allowed routes list) to the InterLink to allow traffic to flow.
+</Message>
+
+You can deactivate route propagation via the dedicated endpoint at any time. When you do this, all routes are blocked and removed from the VPC's route table. No traffic can flow across the InterLink until route propagation is reactivated.