NavigationContentFooter
Jump toSuggest an edit

InterLink - Technical overview

Reviewed on 24 October 2024Published on 24 October 2024
Important

InterLink is currently in Private Beta, and only available to selected testers.

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 routes allowed between the two peers:

Scaleway plans to offer two types of InterLink, though currently only the hosted type is available.

A hosted InterLink is provisioned via a partner. Partners are telecom operators or network providers that have been pre-selected by Scaleway. They provide a shareable port on their router, with a certain amount of bandwidth, at a PoP (location) where both Scaleway and the partner’s networks are present. The available bandwidth is shared between multiple customers: each gets a specified amount when creating their InterLink.

By choosing a hosted InterLink, you can re-use existing connectivity between a PoP where both you and the partner are present, and the Scaleway network. Layer 2 isolation to your Scaleway VPC is preserved, with guaranteed bandwidth (100Mbps - 25Gbps) across the InterLink.

The diagram below shows the architecture of a hosted InterLink. Note that three possibilities are available on the customer side:

  • The partner’s router connects to the customer’s router (itself connected to the customer’s on-premises infrastructure) via a Meet Me Room at a PoP where both networks are present.
  • 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.

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 to register your interest.

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 for full details.

Attaching a VPC

When you initially create the InterLink, it is not associated with a specific VPC, only with a given 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 page for more information.

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 across multiple InterLinks.

InterLink uses Border Gateway Protocol to exchange routing information between the customer’s network 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. This facilitates efficient traffic flow across the link towards these destinations, providing that allowed routes and route propagation have been correctly set up.

In fact, each InterLink has two BGP sessions: one for IPv4 and one for IPv6. Each session handles the exchange of IP prefixes for its respective IP version. The separation of these sessions ensures that IPv4 and IPv6 traffic can be managed independently, and provides compatibility with networks that may only support one of the IP versions.

When both BGP sessions are up, the InterLink has Active status. If one BGP session is up, and the other down, the status moves to Limited Connectivity. If both BGP sessions are down, the status is marked as Down. See the page on InterLink statuses for full information.

Allowed routes list

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 an allowed routes list (aka 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 page for more information on allowed routes lists.

Route propagation

Even after attaching an allowed route list, traffic cannot flow across your InterLink until you activate route propagation. This is the second part of the safety-net mechanism enabling you to fine-tune the traffic that flows across your InterLink. Route propagation can be activated or deactivated whenever you want. See the configuration page for more information on route propagation.

Was this page helpful?
API DocsScaleway consoleDedibox consoleScaleway LearningScaleway.comPricingBlogCareers
© 2023-2024 – Scaleway