InterLink API

v1beta1

Introduction

Partners

A partner is a third-party service provider who facilitates the connection between the a customer's infrastructure and their Scaleway VPC, via an InterLink connection.

GET/interlink/v1beta1/regions/{region}/partners

GET/interlink/v1beta1/regions/{region}/partners/{partner_id}

Points Of Presence

A Point Of Presence (also known as a "PoP", or "location"), is a datacenter location where a InterLink connection is available. They are facilitated by partners, providing the means for a customer to create an InterLink session.

GET/interlink/v1beta1/regions/{region}/pops

GET/interlink/v1beta1/regions/{region}/pops/{pop_id}

Connections

A connection represents the physical InterLink resource. This is a physical connection of Scaleway's network equipment with that of a self-hosted user or partner located in the same datacenter. Once created, a partner's connection will then typically be shared, facilitating many logical InterLinks for different hosted users. A self-hosted user's connection is their own dedicated connection, which they can use to create one or many logical InterLinks (links) for themselves.

GET/interlink/v1beta1/regions/{region}/dedicated-connections

GET/interlink/v1beta1/regions/{region}/dedicated-connections/{connection_id}

Links

A link represents the logical InterLink resource. This is a BGP peering session established between peer router (either partners or end customer's) and a Scaleway InterLink switch. Self-hosted links are facilitated by end users' own dedicated physical connections, while hosted links are facilitated via a partner's shared physical connection.

GET/interlink/v1beta1/regions/{region}/links

POST/interlink/v1beta1/regions/{region}/links

GET/interlink/v1beta1/regions/{region}/links/{link_id}

PATCH/interlink/v1beta1/regions/{region}/links/{link_id}

DELETE/interlink/v1beta1/regions/{region}/links/{link_id}

POST/interlink/v1beta1/regions/{region}/links/{link_id}/attach-routing-policy

POST/interlink/v1beta1/regions/{region}/links/{link_id}/attach-vpc

POST/interlink/v1beta1/regions/{region}/links/{link_id}/detach-routing-policy

POST/interlink/v1beta1/regions/{region}/links/{link_id}/detach-vpc

POST/interlink/v1beta1/regions/{region}/links/{link_id}/disable-route-propagation

POST/interlink/v1beta1/regions/{region}/links/{link_id}/enable-route-propagation

POST/interlink/v1beta1/regions/{region}/links/{link_id}/set-routing-policy

Routing Policies

By default, all routes across the InterLink (between peer and attached VPC) are blocked. Routing policies allow you to set filters to define the IP prefixes to allow.

GET/interlink/v1beta1/regions/{region}/routing-policies

POST/interlink/v1beta1/regions/{region}/routing-policies

GET/interlink/v1beta1/regions/{region}/routing-policies/{routing_policy_id}

PATCH/interlink/v1beta1/regions/{region}/routing-policies/{routing_policy_id}

DELETE/interlink/v1beta1/regions/{region}/routing-policies/{routing_policy_id}