Skip to content

Commit 2800133

Browse files
committed
fix(interlink): add info
1 parent a34433f commit 2800133

File tree

2 files changed

+4
-6
lines changed

2 files changed

+4
-6
lines changed

network/interlink/reference-content/overview.mdx

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ At its simplest level, InterLink can be understood as a configurable connection
2828

2929
## Types of InterLink
3030

31-
Scaleway plans to offer three types of InterLink, though currently only the **hosted** type is available.
31+
Scaleway plans to offer two types of InterLink, though currently only the **hosted** type is available.
3232

3333
### Hosted InterLinks
3434

@@ -47,10 +47,6 @@ The diagram below shows the architecture of a hosted InterLink. Note that three
4747

4848
A dedicated 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. 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.
4949

50-
### Shared InterLink
51-
52-
A shared InterLink is provisioned, where the customer's port is one of multiple InterLinks using a certain port on Scaleway's router, sharing its bandwidth. 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.
53-
5450
## Provisioning an InterLink
5551

5652
Provisioning an InterLink is a multi-step process. As only hosted InterLinks (via partners) are currently available, specific action is required from both from Scaleway, the customer, and from the selected partner in order to successfully complete the provisioning process. See our dedicated page on [provisioning an InterLink](/network/interlink/reference-content/provisioning/) for full details.
@@ -59,6 +55,8 @@ Provisioning an InterLink is a multi-step process. As only hosted InterLinks (vi
5955

6056
When you initially create the InterLink, it is not associated with a specific VPC, only with given a Scaleway region. Attaching it to a VPC within the specified region is essential to complete the connection on the Scaleway side. You can only attach a VPC once the provisioning process is complete, and the InterLink has `Active` status. See the [configuration](/network/interlink/reference-content/configuring/) page for more information.
6157

58+
While each InterLink can only be attached to a single Scaleway VPC, it is possible to attach two InterLinks to the same VPC to ensure redundancy and high availability. In this case, each InterLink must be provisioned and configured separately, and will be billed separately. Note that you can reuse the same [allowed routes lists](#allowed-routes-list) across multiple InterLinks.
59+
6260
## Routing across an InterLink
6361

6462
InterLink uses [**B**order **G**ateway **P**rotocol](https://en.wikipedia.org/wiki/Border_Gateway_Protocol) to exchange routing information between the customer’s network and the Scaleway VPC.

network/interlink/reference-content/provisioning.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ When you no longer want your InterLink connection, you can delete it. The proces
9595

9696
1. Deactivate route propagation.
9797
2. [Delete your InterLink on the Scaleway side](https://www.scaleway.com/en/developers/api/interlink/#path-links-delete-a-link). InterLink status moves to `Deprovisioning`.
98-
3. Contact your partner to request they provision the InterLink resource on their side.
98+
3. Contact your partner to request they deprovision the InterLink resource on their side.
9999
4. InterLink moves to `Deleted` status once the partner has completed deprovisioning.
100100

101101
Scaleway stops billing you for your InterLink immediately after step 2. Your partner may continue to bill you until they deprovision the resource on their side.

0 commit comments

Comments
 (0)