diff --git a/macros/audit-trail/serverless-containers-endpoints.mdx b/macros/audit-trail/serverless-containers-endpoints.mdx index 7c1c43b8ed..9dd8f6b173 100644 --- a/macros/audit-trail/serverless-containers-endpoints.mdx +++ b/macros/audit-trail/serverless-containers-endpoints.mdx @@ -7,7 +7,7 @@ macro: adt-serverless-containers-endpoints ### Serverless Containers supported endpoints - The following [Serverless Containers](/serverless/containers/) endpoints are supported and will be logged in Audit Trail: + The following [Serverless Containers](/serverless-containers/) endpoints are supported and will be logged in Audit Trail: - CreateContainer (`POST /containers/v1/regions/{region}/containers`) - UpdateContainer (`PATCH /containers/v1/regions/{region}/containers/{container_id}`) diff --git a/macros/audit-trail/serverless-functions-endpoints.mdx b/macros/audit-trail/serverless-functions-endpoints.mdx index ec97beaeb8..56f5426a2b 100644 --- a/macros/audit-trail/serverless-functions-endpoints.mdx +++ b/macros/audit-trail/serverless-functions-endpoints.mdx @@ -7,7 +7,7 @@ macro: adt-serverless-functions-endpoints ### Serverless Functions supported endpoints - The following [Serverless Functions](/serverless/functions/) endpoints are supported and will be logged in Audit Trail: + The following [Serverless Functions](/serverless-functions/) endpoints are supported and will be logged in Audit Trail: - CreateCron (`POST /functions/v1beta1/regions/{region}/crons`) - UpdateCron (`PATCH /functions/v1beta1/regions/{region}/crons/{cron_id}`) diff --git a/macros/cockpit/alert-billing.mdx b/macros/cockpit/alert-billing.mdx deleted file mode 100644 index 176570c549..0000000000 --- a/macros/cockpit/alert-billing.mdx +++ /dev/null @@ -1,8 +0,0 @@ ---- -macro: alert-billing ---- - - - **Review your alerts**

- You are responsible for your active alerting rules in Cockpit. We recommend that you review your alerting and recording rules configuration **before March 1st 2026**. Disable unused or unnecessary rules to avoid unexpected charges. - \ No newline at end of file diff --git a/macros/compute/instances-block-bandwidth-overview.mdx b/macros/compute/instances-block-bandwidth-overview.mdx deleted file mode 100644 index 2d651d717f..0000000000 --- a/macros/compute/instances-block-bandwidth-overview.mdx +++ /dev/null @@ -1,130 +0,0 @@ ---- -macros: instances-block-bandwidth-overview ---- - -This guide provides a complete overview of internet and Block Storage bandwidth for Scaleway Instances. -Understanding these specifications is crucial for optimizing your infrastructure for performance and compatibility. - -### Why bandwidth matters - -Bandwidth impacts how your applications perform and interact with other systems. -- **Internet bandwidth**: Affects how fast your Instance can send or receive data over the internet. -- **Block bandwidth**: Determines the read/write speed to Block Storage, essential for storage-heavy workloads like databases and analytics. - - - Bandwidth specifications listed here are for informational purposes. To validate the exact bandwidth capacity of your Instance type, refer to the `block_bandwidth` field in the [Instances API](https://www.scaleway.com/en/developers/api/instances/#path-instance-types-list-instance-types). Use the endpoint `/instance/v1/zones/{zone}/products/servers` to retrieve Instance type specifications. - - - - To maximize compatibility with [Block Storage Low Latency 15k](/block-storage/), select an Instance with **at least 3 GiB/s** of Block bandwidth. - - -## BASIC2-A range -| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | -|-----------------------|-------------------------|---------------------| -| BASIC2-A2C-4G | 200 Mbit/s | 80 MiB/s | -| BASIC2-A2C-8G | 200 Mbit/s | 80 MiB/s | -| BASIC2-A4C-8G | 400 Mbit/s | 120 MiB/s | -| BASIC2-A4C-16G | 400 Mbit/s | 120 MiB/s | -| BASIC2-A8C-16G | 800 Mbit/s | 240 MiB/s | -| BASIC2-A8C-32G | 800 Mbit/s | 240 MiB/s | -| BASIC2-A16C-32G | 1.6 Gbit/s | 480 MiB/s | -| BASIC2-A16C-64G | 1.6 Gbit/s | 480 MiB/s | - -## COPARM1 range - -| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | -|-----------------------|-------------------------|---------------------| -| COPARM1-2C-8G | 200 Mbit/s | 80 MiB/s | -| COPARM1-4C-16G | 400 Mbit/s | 160 MiB/s | -| COPARM1-8C-32G | 800 Mbit/s | 320 MiB/s | -| COPARM1-16C-64G | 1.6 Gbit/s | 640 MiB/s | -| COPARM1-32C-128G | 3.2 Gbit/s | 1.25 GiB/s | - -## DEV1 range - -| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | -|-----------------------|-------------------------|---------------------| -| DEV1-S | 200 Mbit/s | 100 MiB/s | -| DEV1-M | 300 Mbit/s | 150 MiB/s | -| DEV1-L | 400 Mbit/s | 200 MiB/s | -| DEV1-XL | 500 Mbit/s | 250 MiB/s | - -## GP1 range - -| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | -|-----------------------|-------------------------|---------------------| -| GP1-XS | 500 Mbit/s | 300 MiB/s | -| GP1-S | 800 Mbit/s | 500 MiB/s | -| GP1-M | 1.5 Gbit/s | 800 MiB/s | -| GP1-L | 5 Gbit/s | 1 GiB/s | -| GP1-XL | 10 Gbit/s | 2 GiB/s | - -## PLAY2 range - -| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | -|-----------------------|-------------------------|---------------------| -| PLAY2-PICO | 100 Mbit/s | 40 MiB/s | -| PLAY2-NANO | 200 Mbit/s | 80 MiB/s | -| PLAY2-MICRO | 400 Mbit/s | 160 MiB/s | - -## PRO2 range - -| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | -|-----------------------|-------------------------|---------------------| -| PRO2-XXS | 350 Mbit/s | 125 MiB/s | -| PRO2-XS | 700 Mbit/s | 250 MiB/s | -| PRO2-S | 1.5 Gbit/s | 500 MiB/s | -| PRO2-M | 3 Gbit/s | 1 GiB/s | -| PRO2-L | 6 Gbit/s | 2 GiB/s | - -## POP2 range - -| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | -|-----------------------|-------------------------|---------------------| -| POP2-2C-8G | 400 Mbit/s | 400 MiB/s | -| POP2-4C-16G | 800 Mbit/s | 800 MiB/s | -| POP2-8C-32G | 1.6 Gbit/s | 1.56 GiB/s | -| POP2-16C-64G | 3.2 Gbit/s | 3.12 GiB/s | -| POP2-32C-128G | 6.4 Gbit/s | 5.5 GiB/s | -| POP2-64C-256G | 12.8 Gbit/s | 5.5 GiB/s | - -## POP2-WIN range (Windows Server OS) - -| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | -|-----------------------|-------------------------|---------------------| -| POP2-2C-8G-WIN | 400 Mbit/s | 400 MiB/s | -| POP2-4C-16G-WIN | 800 Mbit/s | 800 MiB/s | -| POP2-8C-32G-WIN | 1.6 Gbit/s | 1.56 GiB/s | -| POP2-16C-64G-WIN | 3.2 Gbit/s | 3.12 GiB/s | -| POP2-32C-128G-WIN | 6.4 Gbit/s | 5.5 GiB/s | - -## POP2-HC range (High Compute) - -| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | -|-----------------------|-------------------------|---------------------| -| POP2-HC-2C-4G | 400 Mbit/s | 400 MiB/s | -| POP2-HC-4C-8G | 800 Mbit/s | 800 MiB/s | -| POP2-HC-8C-16G | 1.6 Gbit/s | 1.56 GiB/s | -| POP2-HC-16C-32G | 3.2 Gbit/s | 3.12 GiB/s | -| POP2-HC-32C-64G | 6.4 Gbit/s | 5.5 GiB/s | -| POP2-HC-64C-128G | 12.8 Gbit/s | 5.5 GiB/s | - -## POP2-HM range (High Memory) - -| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | -|-----------------------|-------------------------|---------------------| -| POP2-HM-2C-16G | 400 Mbit/s | 400 MiB/s | -| POP2-HM-4C-32G | 800 Mbit/s | 800 MiB/s | -| POP2-HM-8C-64G | 1.6 Gbit/s | 1.56 GiB/s | -| POP2-HM-16C-128G | 3.2 Gbit/s | 3.12 GiB/s | -| POP2-HM-32C-256G | 6.4 Gbit/s | 5.5 GiB/s | -| POP2-HM-64C-512G | 12.8 Gbit/s | 5.5 GiB/s | - -## POP2-HN range (High Network) - -| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | -|-----------------------|-------------------------|---------------------| -| POP2-HN-3 | 3 Gbit/s | 400 MiB/s | -| POP2-HN-5 | 5 Gbit/s | 800 MiB/s | -| POP2-HN-10 | 10 Gbit/s | 800 MiB/s | \ No newline at end of file diff --git a/macros/compute/public-ip.mdx b/macros/compute/public-ip.mdx deleted file mode 100644 index 2a16989818..0000000000 --- a/macros/compute/public-ip.mdx +++ /dev/null @@ -1,7 +0,0 @@ ---- -macro: compute-public-ip -title: Implementing a DNS server using BIND -description: In this tutorial you will learn How to implement a DNS server using BIND. ---- - -Public IP addresses are routed on the internet. You can enter the public IP address of your Instance into any browser connected to the Internet, and access content being served from that instance. You can think of public IP addresses like postal addresses for buildings - they are unique, and tell the routers directing traffic through the internet where to find a particular server. diff --git a/macros/concepts/block-snapshot.mdx b/macros/concepts/block-snapshot.mdx index d3b6dec35b..c13c7802a3 100644 --- a/macros/concepts/block-snapshot.mdx +++ b/macros/concepts/block-snapshot.mdx @@ -2,6 +2,6 @@ macro: block-snapshot --- -A snapshot takes a picture of a specific volume at one point in time. For example, you may have a server with one volume containing the OS and another containing the application data, and you want to use different snapshot strategies on both volumes. [Creating snapshots of your volumes](/block-storage/how-to/create-a-snapshot/) gives you total freedom of which volumes you want to back up, while [images](#image) are more convenient for full backups of your Instance. +A snapshot takes a picture of a specific volume at one point in time. For example, you may have a server with one volume containing the OS and another containing the application data, and you want to use different snapshot strategies on both volumes. [Creating snapshots of your volumes](/block-storage/how-to/create-a-snapshot/) gives you total freedom of which volumes you want to back up, while images are more convenient for full backups of your Instance. You can create a snapshot directly from a volume, or generate it automatically when you create an Instance image. In both cases, the snapshot exists as an independent, billed resource and is not deleted when its source volume, Instance, or image is deleted. \ No newline at end of file diff --git a/macros/developer-tools/scaleway-configuration-file.mdx b/macros/developer-tools/scaleway-configuration-file.mdx index 48a98ef814..25f65e48c2 100644 --- a/macros/developer-tools/scaleway-configuration-file.mdx +++ b/macros/developer-tools/scaleway-configuration-file.mdx @@ -21,10 +21,10 @@ The configuration file contains the following elements: : The ID of the Scaleway Project to use by default **default_zone** -: The [availability zone](/account/products-availability/) to use by default +: The [availability zone](https://www.scaleway.com/en/product-availability-by-region/) to use by default **default_region** -: The [region](/account/products-availability/) to use by default +: The [region](https://www.scaleway.com/en/product-availability-by-region/) to use by default **api_url** : The API URL to use (`https://api.scaleway.com` by default) diff --git a/macros/general/troubleshooting-ticket.mdx b/macros/general/troubleshooting-ticket.mdx deleted file mode 100644 index 041cddc94d..0000000000 --- a/macros/general/troubleshooting-ticket.mdx +++ /dev/null @@ -1,29 +0,0 @@ ---- -macro: troubleshooting-ticket ---- - -If you still cannot solve your problem, [open a support ticket](/account/support/open-a-support-ticket/#writing-an-effective-subject-and-description), providing as many details as possible including the information below: - - Resource ID - - Resource name - - Date and time (timestamp) - - User-agent (SDK, client, console, etc.) - - Transaction ID (if possible) - - Log / trace of the error (if possible) - - Screenshots (using our secure [pastebin tool](https://privatebin.iliad.fr/)) - - HTTP status code (if applicable) - - Request type (PUT, GET, etc., if applicable) - - - - - diff --git a/macros/iam/login-member.mdx b/macros/iam/login-member.mdx index 5adada9558..e5c622e9a2 100644 --- a/macros/iam/login-member.mdx +++ b/macros/iam/login-member.mdx @@ -23,7 +23,7 @@ macro: login-member - Make sure you check your spam folder - Click **Resend email** - Contact an Organization administrator to make sure your information was correctly registered - - If none of the actions above work, ask an administrator to [contact the support](/account/support/open-a-support-ticket/#writing-an-effective-subject-and-description) + - If none of the actions above work, ask an administrator to [contact the Support team](/account/support/open-a-support-ticket/) 4. Click **Continue**. diff --git a/macros/storage/block-storage-no-migration-for-k8s.mdx b/macros/storage/block-storage-no-migration-for-k8s.mdx deleted file mode 100644 index 1fb655b649..0000000000 --- a/macros/storage/block-storage-no-migration-for-k8s.mdx +++ /dev/null @@ -1,8 +0,0 @@ ---- -macro: block-storage-no-migration-for-k8s ---- - - -

- **Kubernetes customers must not migrate their block volumes to the Block Storage API to prevent major disruptions to their Kubernetes service and block volume unavailability.** You can identify your volumes by [listing them](/block-storage/api-cli/identifying-volume-snapshot-api/#listing-volumes-created-with-the-block-storage-api) and referring to the `name` field, next to which you should see an output similar to `k8s_base_node_2024-07-26`. - \ No newline at end of file diff --git a/macros/storage/boot-on-block.mdx b/macros/storage/boot-on-block.mdx index e58ff180d4..4b4d5eb45e 100644 --- a/macros/storage/boot-on-block.mdx +++ b/macros/storage/boot-on-block.mdx @@ -2,4 +2,4 @@ macro: storage-boot-on-block --- -Boot-on-block is a feature that allows booting Instances from attached [Block Storage](#block-volumes) volumes instead of local volumes. It is available for all Instance types. \ No newline at end of file +Boot-on-block is a feature that allows booting Instances from attached Block Storage volumes instead of local volumes. It is available for all Instance types. \ No newline at end of file diff --git a/pages/account/login-credentials/log-in-to-the-console.mdx b/pages/account/login-credentials/log-in-to-the-console.mdx index 5f8f10c21a..936e290aa6 100644 --- a/pages/account/login-credentials/log-in-to-the-console.mdx +++ b/pages/account/login-credentials/log-in-to-the-console.mdx @@ -6,7 +6,7 @@ dates: validation: 2026-06-26 posted: 2024-06-11 --- -import LoginMember from '@macros/iam/login-member.mdx' + import Requirements from '@macros/iam/requirements.mdx' import image from './assets/scaleway-auth-code.webp' diff --git a/pages/audit-trail/reference-content/splunk-integration.mdx b/pages/audit-trail/reference-content/splunk-integration.mdx index ffb848fb90..c00be2cd60 100644 --- a/pages/audit-trail/reference-content/splunk-integration.mdx +++ b/pages/audit-trail/reference-content/splunk-integration.mdx @@ -9,8 +9,6 @@ categories: - monitoring --- -import Requirements from '@macros/iam/requirements.mdx' - import image1 from './assets/scaleway-audit-trail-splunk-add-account.png' import image2 from './assets/scaleway-audit-trail-splunk-create-new-input.png' diff --git a/pages/block-storage/how-to/mount-a-volume.mdx b/pages/block-storage/how-to/mount-a-volume.mdx index 14a2bf62fe..17824da4e6 100644 --- a/pages/block-storage/how-to/mount-a-volume.mdx +++ b/pages/block-storage/how-to/mount-a-volume.mdx @@ -8,6 +8,11 @@ dates: --- import Requirements from '@macros/iam/requirements.mdx' + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#permission) allowing you to perform actions in the intended Organization - An [Instance](/instances/concepts/#instance) diff --git a/pages/cockpit/faq.mdx b/pages/cockpit/faq.mdx index 3068c86afd..2561918f0e 100644 --- a/pages/cockpit/faq.mdx +++ b/pages/cockpit/faq.mdx @@ -6,8 +6,6 @@ dates: productIcon: CockpitProductIcon --- -import AlertBilling from '@macros/cockpit/alert-billing.mdx' - ## Overview ### What is Cockpit? diff --git a/pages/data-orchestrator/how-to/monitor-workflow.mdx b/pages/data-orchestrator/how-to/monitor-workflow.mdx index a44c117df3..9e3e5ed47a 100644 --- a/pages/data-orchestrator/how-to/monitor-workflow.mdx +++ b/pages/data-orchestrator/how-to/monitor-workflow.mdx @@ -7,7 +7,6 @@ dates: posted: 2026-04-20 --- import Requirements from '@macros/iam/requirements.mdx' -import RunWorkflow from '@macros/data-orchestrator/run-workflow.mdx' import BetaNoteDataOrc from '@macros/data-orchestrator/beta-note.mdx' diff --git a/pages/data-orchestrator/quickstart.mdx b/pages/data-orchestrator/quickstart.mdx index 244cbbc910..ce4464ba0d 100644 --- a/pages/data-orchestrator/quickstart.mdx +++ b/pages/data-orchestrator/quickstart.mdx @@ -7,7 +7,6 @@ dates: posted: 2025-04-20 --- import Requirements from '@macros/iam/requirements.mdx' -import UploadWorkflow from '@macros/data-orchestrator/upload-workflow.mdx' import RunWorkflow from '@macros/data-orchestrator/run-workflow.mdx' import BetaNoteDataOrc from '@macros/data-orchestrator/beta-note.mdx' diff --git a/pages/file-storage/concepts.mdx b/pages/file-storage/concepts.mdx index 97d8ad63ed..bb207b6140 100644 --- a/pages/file-storage/concepts.mdx +++ b/pages/file-storage/concepts.mdx @@ -24,6 +24,10 @@ Refer to the [dedicated documentation](/file-storage/how-to/attach-file-system/) +## Block Volumes + + + ## File Storage Scaleway File Storage allows you to keep data in an organized hierarchy of files and folders. This hierarchy can be shared across a network, so multiple compute instances can work on the same collection of files. diff --git a/pages/instances/api-cli/getting-started-autoscaling-groups.mdx b/pages/instances/api-cli/getting-started-autoscaling-groups.mdx index ca0ec3a564..f5106d41bb 100644 --- a/pages/instances/api-cli/getting-started-autoscaling-groups.mdx +++ b/pages/instances/api-cli/getting-started-autoscaling-groups.mdx @@ -14,9 +14,10 @@ Autoscaling Groups help you maintain application performance and control costs: This guide takes you from setup to your first working Autoscaling Group. You create an Instance template, launch an Autoscaling Group, and verify that scale-out, scale-in, and auto-healing behave as expected. -## Before you start + -- A Scaleway account logged into the [console](https://console.scaleway.com/) +- A Scaleway account logged in to the [console](https://console.scaleway.com) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Beta access to the Autoscaling Groups Private Beta - A Scaleway Project to work in - A terminal with [curl](https://curl.se/) and/or [CLI](https://www.scaleway.com/fr/cli/) installed diff --git a/pages/instances/reference-content/instance-lifecycle.mdx b/pages/instances/reference-content/instance-lifecycle.mdx index 26eee12a32..fe948e0a24 100644 --- a/pages/instances/reference-content/instance-lifecycle.mdx +++ b/pages/instances/reference-content/instance-lifecycle.mdx @@ -7,8 +7,6 @@ dates: posted: 2026-03-12 --- -import Requirements from '@macros/iam/requirements.mdx' - import alert from './assets/alert.webp' import healthy from './assets/healthy.webp' import restriction from './assets/restriction.webp' diff --git a/pages/load-balancer/how-to/assets/scaleway-create-es-pipeline-lb.webp b/pages/load-balancer/how-to/assets/scaleway-create-es-pipeline-lb.webp deleted file mode 100644 index 75d89eb2b6..0000000000 Binary files a/pages/load-balancer/how-to/assets/scaleway-create-es-pipeline-lb.webp and /dev/null differ diff --git a/pages/load-balancer/how-to/use-edge-services.mdx b/pages/load-balancer/how-to/use-edge-services.mdx index fbaaf14275..a3f4d47f8d 100644 --- a/pages/load-balancer/how-to/use-edge-services.mdx +++ b/pages/load-balancer/how-to/use-edge-services.mdx @@ -7,10 +7,6 @@ dates: tags: load-balancer edge-services cdn network cache domain https --- import EdgeServicesLbBenefits from '@macros/edge-services/edge-services-lb-benefits.mdx' -import Requirements from '@macros/iam/requirements.mdx' - -import image from './assets/scaleway-create-es-pipeline-lb.webp' - Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. diff --git a/pages/serverless-containers/troubleshooting/custom-domain-in-error-status.mdx b/pages/serverless-containers/troubleshooting/custom-domain-in-error-status.mdx index c574280667..c74ac1dc49 100644 --- a/pages/serverless-containers/troubleshooting/custom-domain-in-error-status.mdx +++ b/pages/serverless-containers/troubleshooting/custom-domain-in-error-status.mdx @@ -6,7 +6,6 @@ dates: validation: 2026-03-02 posted: 2026-03-02 --- -import Requirements from '@macros/iam/requirements.mdx' import image from '../assets/cloudflare-bypass-cache-well-known-acme-challenge.webp' diff --git a/pages/serverless-functions/troubleshooting/custom-domain-in-error-status.mdx b/pages/serverless-functions/troubleshooting/custom-domain-in-error-status.mdx index a5a892bd96..93a61d12f1 100644 --- a/pages/serverless-functions/troubleshooting/custom-domain-in-error-status.mdx +++ b/pages/serverless-functions/troubleshooting/custom-domain-in-error-status.mdx @@ -6,7 +6,6 @@ dates: validation: 2026-03-02 posted: 2026-03-02 --- -import Requirements from '@macros/iam/requirements.mdx' import image from '../assets/cloudflare-bypass-cache-well-known-acme-challenge.webp' diff --git a/pages/site-to-site-vpn/how-to/create-manage-routing-policy.mdx b/pages/site-to-site-vpn/how-to/create-manage-routing-policy.mdx index 1a1c87f4ee..34be7ddfd1 100644 --- a/pages/site-to-site-vpn/how-to/create-manage-routing-policy.mdx +++ b/pages/site-to-site-vpn/how-to/create-manage-routing-policy.mdx @@ -22,6 +22,11 @@ A VPN connection must have a **minimum of one** and a **maximum of two** attache When creating a routing policy, you specify one or many IP ranges representing the outgoing routes to announce from the Scaleway VPN gateway, and one or many IP ranges representing the incoming route announcements to accept from the customer gateway. When [route propagation](/site-to-site-vpn/concepts/#route-propagation) is activated, the route ranges defined in the routing policy are whitelisted, and traffic can flow through the tunnel along these routes. + + +- A Scaleway account logged in to the [console](https://console.scaleway.com) +- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#permission) allowing you to perform actions in the intended Organization + ## How to create a routing policy 1. Click **Site-to-Site VPN** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your VPN connections displays. diff --git a/pages/vpc-peering/reference-content/understanding-vpc-peering.mdx b/pages/vpc-peering/reference-content/understanding-vpc-peering.mdx index 7f1f83e568..c5a5cebcb3 100644 --- a/pages/vpc-peering/reference-content/understanding-vpc-peering.mdx +++ b/pages/vpc-peering/reference-content/understanding-vpc-peering.mdx @@ -8,7 +8,6 @@ dates: --- import UnsupportedRoutingProducts from '@macros/vpc/unsupported-routing-products.mdx' import peeringDiag from './assets/scaleway-vpc-peering-diag.webp' -import VPCRoutingCompatibility from '@macros/vpc/vpc-routing-compatibility.mdx' This document covers the features, use cases, pricing, and technical details of VPC Peering.