diff --git a/pages/dedibox-domains/concepts.mdx b/pages/dedibox-domains/concepts.mdx index 338eec2e0c..4e2db3176e 100644 --- a/pages/dedibox-domains/concepts.mdx +++ b/pages/dedibox-domains/concepts.mdx @@ -3,7 +3,7 @@ title: Scaleway Dedibox Domains - Concepts description: This page explains all the concepts related to Scaleway Dedibox Domains tags: dedibox domain-name dns-server dns tld dnssec waps authcode dates: - validation: 2025-03-03 + validation: 2025-09-11 --- ## Domain name diff --git a/pages/dedibox-domains/quickstart.mdx b/pages/dedibox-domains/quickstart.mdx index 36b2137a7c..9823bc3158 100644 --- a/pages/dedibox-domains/quickstart.mdx +++ b/pages/dedibox-domains/quickstart.mdx @@ -3,7 +3,7 @@ title: Domains - Quickstart description: This page shows you how to get started with Scaleway Dedibox Domains. tags: dedibox domains domain waps whois dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' @@ -17,7 +17,7 @@ A domain name is the equivalent of your postal address on the web, and allows yo -- A Dedibox account logged into the [console](https://console.online.net) +- A Dedibox account logged into the [Online console](https://console.online.net) ## How to buy a domain @@ -38,7 +38,7 @@ A domain name is the equivalent of your postal address on the web, and allows yo 6. Scroll down to the bottom of the page and click **Order**. 7. If you did not select hosting backup, a pop-up may display asking you to confirm your choice. Click **Continue without backup** or **Add backup**. The **Contact information** page displays. 8. Select the domain owner from your existing contacts, or choose to create a new contact. - + You must always keep the contact details regarding the owner of your domain name accurate and up-to-date. Once created, if you wish to change details about the owner’s identity, such as full name(s) or corporate name, you must complete the [change of owner/applicant](/dedibox-domains/how-to/change-ownership/) process via the [console](https://console.online.net/fr/domain/trade). 9. Scroll down to the bottom of the page and click **Confirm**. @@ -60,7 +60,7 @@ WAPS, or **W**hois **A**ccuracy **P**rogram **S**pecification, is a system intro domain names. As part of a mandatory process that is required by ICANN, - we need to verify if your e-mail address is still being used as a domain name holder once a year and for each modification. + we need to verify if your e-mail address is still being used as a domain name holder once a year and for each modification. of your e-mail validity use as a domain name holder. WARNING: Without a response from your end within 15 days the verification fails and your domain names may get suspended. diff --git a/pages/dedibox-hardware/how-to/configure-dell-perc-h200.mdx b/pages/dedibox-hardware/how-to/configure-dell-perc-h200.mdx index 0bf70ab849..5a6e7416b2 100644 --- a/pages/dedibox-hardware/how-to/configure-dell-perc-h200.mdx +++ b/pages/dedibox-hardware/how-to/configure-dell-perc-h200.mdx @@ -3,7 +3,7 @@ title: How to configure the DELL PERC H200 RAID controller description: This page explains how to configure the DELL PERC H200 RAID controller on a Scaleway Dedibox tags: dedibox h200 raid dell perc controller dates: - validation: 2025-03-05 + validation: 2025-09-11 posted: 2021-07-16 --- import Requirements from '@macros/iam/requirements.mdx' @@ -13,7 +13,7 @@ This documentation explains how to configure the DELL PERC H200 RAID controller -- A Dedibox account logged into the [console](https://console.online.net) +- A Dedibox account logged into the Online [console](https://console.online.net) - A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox/) with a [DELL PERC H200](https://www.dell.com/support/kbdoc/en-us/000134280/perc-dell-perc-h200-and-6gbps-sas-hba-features) RAID controller ## Checking the RAID controller status @@ -72,7 +72,7 @@ For maximum performance, you can activate the cache of your SATA disks. After cr ## Advanced operations ### Creating a RAID volume -To create a virtual drive in controller 0, including disks 0 and 1: +Run the following command to create a virtual drive in controller 0, including disks 0 and 1: ```bash # to create a RAID0 sas2ircu 0 create raid0 max 1:0 1:1 @@ -83,7 +83,7 @@ To create a virtual drive in controller 0, including disks 0 and 1: ``` ### Creating a hot spare drive -To create a hot spare drive: +Run the following command to create a hot spare drive: ```bash # example with drive 1:1 sas2ircu 0 HOTSPARE 1:1 @@ -94,13 +94,13 @@ To create a hot spare drive: Deleting the configuration is **DANGEROUS** and should be done with caution. -To delete controller 0 configuration: +Run the following command to delete controller 0 configuration: ```bash sas2ircu 0 delete ``` ### Enabling an inactive volume -To enable an inactive volume: +Run the following command to enable an inactive volume: ```bash sas2ircu 0 ACTIVATE $the-volume-id ``` diff --git a/pages/dedibox-hardware/how-to/configure-dell-perc-h310-h700-h710-h730p-lsi9361.mdx b/pages/dedibox-hardware/how-to/configure-dell-perc-h310-h700-h710-h730p-lsi9361.mdx index db8b8bf351..2c785f9e68 100644 --- a/pages/dedibox-hardware/how-to/configure-dell-perc-h310-h700-h710-h730p-lsi9361.mdx +++ b/pages/dedibox-hardware/how-to/configure-dell-perc-h310-h700-h710-h730p-lsi9361.mdx @@ -3,7 +3,7 @@ title: How to configure the DELL PERC H310 / H700 / H710 / H730-P / LSI9361 RAID description: This page explains how to configure the DELL PERC H310 / H700 / H710 / H730-P / LSI9361 RAID controller on a Scaleway Dedibox tags: dell perc h310 raid controller dedibox dates: - validation: 2025-03-05 + validation: 2025-09-11 posted: 2021-07-16 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/dedibox-hardware/how-to/configure-hardware-raid-console.mdx b/pages/dedibox-hardware/how-to/configure-hardware-raid-console.mdx index 5914da4a5d..a8fd009c58 100644 --- a/pages/dedibox-hardware/how-to/configure-hardware-raid-console.mdx +++ b/pages/dedibox-hardware/how-to/configure-hardware-raid-console.mdx @@ -3,7 +3,7 @@ title: How to configure your Scaleway Dedibox hardware RAID from the console description: This page explains how to configure your Scaleway Dedibox hardware RAID from the console tags: dedibox raid dates: - validation: 2025-03-05 + validation: 2025-09-11 posted: 2021-07-16 --- import Requirements from '@macros/iam/requirements.mdx' @@ -18,7 +18,7 @@ The logical disks of the RAID array are managed by a physical controller, sittin - A [Dedibox account](https://console.online.net) - A Dedibox server with hardware RAID controller -1. Log in to the [Scaleway Dedibox console](https://console.online.net/en/login). +1. Log in to the [Online console](https://console.online.net/en/login). 2. Click **Server** > **Server list** to view a list of available servers in your account. 3. Select the server to install and click **Manage**. 4. Click **RAID configuration** in the menu. diff --git a/pages/dedibox-hardware/how-to/configure-raid-kvm-h200.mdx b/pages/dedibox-hardware/how-to/configure-raid-kvm-h200.mdx index 94656eb291..e8d9efab6e 100644 --- a/pages/dedibox-hardware/how-to/configure-raid-kvm-h200.mdx +++ b/pages/dedibox-hardware/how-to/configure-raid-kvm-h200.mdx @@ -3,7 +3,7 @@ title: How to configure the DELL PERC H200 RAID controller from the KVM description: This page explains how to configure the DELL PERC H200 RAID controller on a Scaleway Dedibox from the KVM tags: dedibox dell perc h200 raid kvm dates: - validation: 2025-03-05 + validation: 2025-09-11 posted: 2021-07-16 --- import Requirements from '@macros/iam/requirements.mdx' @@ -17,7 +17,7 @@ import image5 from './assets/scaleway_h200_06.webp' -- A Dedibox account logged into the [console](https://console.online.net) +- A Dedibox account logged into the [Online console](https://console.online.net) - A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox/) with a [DELL PERC H200](https://www.dell.com/support/kbdoc/en-us/000134280/perc-dell-perc-h200-and-6gbps-sas-hba-features) RAID controller 1. Click **Server** > **Server list** to display the list of your servers. Click the identifier of the server you want to configure. The server information page displays. @@ -44,6 +44,6 @@ import image5 from './assets/scaleway_h200_06.webp' Select a disk using the arrow keys on your keyboard. You can change **NO** to **YES** by pressing the spacebar. -9. Press **C** to validate your edits. Then select **Save changes** and then **Exit menu** to finalize the RAID configuration and reboot your server. +9. Press **C** to validate your edits. Then select **Save changes**, and **Exit menu** to finalize the RAID configuration and reboot your server. diff --git a/pages/dedibox-kvm-over-ip/how-to/disable-boot-errors-idrac.mdx b/pages/dedibox-kvm-over-ip/how-to/disable-boot-errors-idrac.mdx index e1d00a1da5..b63b498ac6 100644 --- a/pages/dedibox-kvm-over-ip/how-to/disable-boot-errors-idrac.mdx +++ b/pages/dedibox-kvm-over-ip/how-to/disable-boot-errors-idrac.mdx @@ -1,9 +1,9 @@ --- title: How to disable boot errors using iDRAC description: This page explains how to disable boot errors using iDRAC on a Scaleway Dedibox -tags: boot error idrac +tags: boot error idrac dates: - validation: 2025-03-05 + validation: 2025-09-11 posted: 2021-06-11 --- import Requirements from '@macros/iam/requirements.mdx' @@ -13,11 +13,11 @@ import image2 from './assets/scaleway-bootstuck2.webp' import image3 from './assets/scaleway-bootstuck3.webp' -This document shows you how to disable boot errors, where your server gets "stuck" showing the line `“trike the F1 key to continue, F2 to run the system setup program`. +This document shows you how to disable boot errors, where your server is stuck and displays the following message: `“trike the F1 key to continue, F2 to run the system setup program`. -- A Dedibox account logged into the [console](https://console.online.net) +- A Dedibox account logged into the [Online console](https://console.online.net) - [Created](/dedibox/how-to/order-a-server/) and [installed](/dedibox/how-to/install-a-server/) a dedicated server with a Dell iDRAC controller 1. [Connect to your server's iDRAC](/dedibox/how-to/use-ipmi-on-server/#how-to-use-ipmi-via-dell-idrac). diff --git a/pages/dedibox-kvm-over-ip/how-to/quantaplex.mdx b/pages/dedibox-kvm-over-ip/how-to/quantaplex.mdx index 286982d980..be1f4cd1de 100644 --- a/pages/dedibox-kvm-over-ip/how-to/quantaplex.mdx +++ b/pages/dedibox-kvm-over-ip/how-to/quantaplex.mdx @@ -3,7 +3,7 @@ title: How to use the QuantaPlex KVM description: This page explains how to use the KVM device of QuantaPlex servers on Scaleway Dedibox. tags: kvm quantaplex dates: - validation: 2025-03-05 + validation: 2025-09-11 posted: 2021-07-16 --- import Requirements from '@macros/iam/requirements.mdx' @@ -21,7 +21,7 @@ This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) -- A Dedibox account logged into the [console](https://console.online.net) +- A Dedibox account logged into the [Online console](https://console.online.net) - A [Dedibox server](/dedibox/how-to/install-a-server/) with a [Quanta Computer QuantaPlex](https://www.qct.io) KVM-over-IP device ## Creating a KVM session @@ -31,12 +31,13 @@ This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) 3. Click **KVM OVER IP** on the right-hand menu. A pop-up window displays. 4. Confirm your acceptance of the terms for KVM access by clicking **I Accept**. -5. Provide the authorized IPv4 address for the KVM connection. The form will autofill with the IP address of your current internet connection. Proceed by clicking **Create** to generate your credentials. +5. Provide the authorized IPv4 address for the KVM connection. The form will autofill with the IP address of your current internet connection. Click **Create** to generate your credentials. Currently, only IPv4 addresses are supported. -Upon completion, the connection URL and your credentials will be displayed. Click on the provided link to access the KVM interface. + Upon completion, the connection URL and your credentials will be displayed. +6. Click the provided link to access the KVM interface. ## Accessing the KVM-over-IP device @@ -51,11 +52,10 @@ Upon completion, the connection URL and your credentials will be displayed. Clic 6. During the boot process, press **F11** to enter the boot menu: +7. Select the boot device **AMI Virtual CDROM0** to boot from the ISO file. The server will boot into installation mode. -Select the boot device **AMI Virtual CDROM0** to boot from the ISO file: + - - -The server will boot into installation mode. Follow the operating system's installation wizard to complete the installation. +8. Follow the operating system's installation wizard to complete the installation. diff --git a/pages/dedibox-kvm-over-ip/how-to/supermicro.mdx b/pages/dedibox-kvm-over-ip/how-to/supermicro.mdx index cb4efdec9a..61921a24e6 100644 --- a/pages/dedibox-kvm-over-ip/how-to/supermicro.mdx +++ b/pages/dedibox-kvm-over-ip/how-to/supermicro.mdx @@ -3,7 +3,7 @@ title: How to use the Supermicro KVM description: This page explains how to use the KVM device of SuperMicro servers on Scaleway Dedibox. tags: kvm supermicro dates: - validation: 2025-03-05 + validation: 2025-09-11 posted: 2021-07-16 --- import Requirements from '@macros/iam/requirements.mdx' @@ -24,7 +24,7 @@ This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) -- A Dedibox account logged into the [console](https://console.online.net) +- A Dedibox account logged into the [Online console](https://console.online.net) - Installed [Java](https://www.java.com/en/download/help/download_options.html) on your local computer - A Dedibox server with a [Supermicro](https://www.supermicro.com/en/solutions/management-software/bmc-resources) KVM-over-IP device @@ -35,17 +35,18 @@ This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) 3. Click **KVM OVER IP** on the right-hand menu. A pop-up window displays. 4. Confirm your acceptance of the terms for KVM access by clicking **I Accept**. -5. Provide the authorized IPv4 address for the KVM connection. The form will autofill with the IP address of your current internet connection. Then click **Create** to generate your credentials. +5. Provide the authorized IPv4 address for the KVM connection. The form will autofill with the IP address of your current internet connection. Click **Create** to generate your credentials. Currently, only IPv4 addresses are accepted. -Once completed, the connection URL and your credentials will be displayed. Click on the provided link to access the KVM interface. + Once completed, the connection URL and your credentials will be displayed. +6. Click the provided link to access the KVM interface. ## Accessing the KVM-over-IP device 1. Open the connection URL of your KVM in your web browser and log in using the credentials provided during access creation. -2. In the KVM menu, click on **Virtual Media** > **CD-ROM Image**: +2. In the KVM menu, click **Virtual Media**, then **CD-ROM Image**: 3. Enter the image file path of your OS image: @@ -60,10 +61,9 @@ Once completed, the connection URL and your credentials will be displayed. Click 5. Reboot the server and press **F11** to enter the boot menu: -6. Select the boot device **ATEN Virtual CDROM** to boot from the ISO file: +6. Select the boot device **ATEN Virtual CDROM** to boot from the ISO file. Your server will boot into installation mode. - -Your server will boot into installation mode. Follow the operating system's installation wizard to complete the installation. +7. Follow the operating system's installation wizard to complete the installation. @@ -78,9 +78,9 @@ Microsoft Windows Server does not support the network adapter used in Supermicro You can also download a local copy of the file directly onto your server using Scaleway's NAS: [https://virtualmedia.online.net/supermicro/CDR-A1-UP_1.00_for_Intel_A1_UP_platform.iso](https://virtualmedia.online.net/supermicro/CDR-A1-UP_1.00_for_Intel_A1_UP_platform.iso). 4. Access the KVM-over-IP device by clicking **Remote Console Preview**. -5. Click **Virtual Media** > **Virtual Storage**. A pop-up will appear: +5. Click **Virtual Media**, then **Virtual Storage**. A pop-up will appear: -6. Select **ISO file** and choose the downloaded ISO image. Then click **Plug in** > **OK**. +6. Select **ISO file** and choose the downloaded ISO image. Then click **Plug in**, and **OK**. 7. Double-click on the CD-ROM drive in your Windows installation and launch the setup tool. Accept the terms and conditions and click **Intel PRO Network Connections Drivers**: 8. Complete the installation of the network drivers using the setup wizard: @@ -88,4 +88,3 @@ Microsoft Windows Server does not support the network adapter used in Supermicro 9. Test the network connection of your Dedibox using the `ping` command: - diff --git a/pages/edge-services/concepts.mdx b/pages/edge-services/concepts.mdx index 76587b59f6..2252fcc81e 100644 --- a/pages/edge-services/concepts.mdx +++ b/pages/edge-services/concepts.mdx @@ -3,7 +3,7 @@ title: Edge Services - Concepts description: Understand Scaleway Edge Services terminology with our glossary of the core concepts underpinning this product. Learn about key features, architecture, and best practices. tags: edge-services edge services pipeline custom-domain cache dates: - creation: 2025-05-14 + creation: 2025-09-11 validation: 2025-03-03 --- import image from './assets/scaleway-edge-services-pipeline.webp' @@ -49,7 +49,7 @@ The primary source from which a Scaleway Edge Services pipeline retrieves and ca ## Origin host -In the case of a Load Balancer origin, the specific host for which Edge Services requests and caches data. This is an optional setting: when specified, this host (e.g. `mydomain.com`) is used in the HTTP Host Header when Edge Services requests data from the Load Balancer. If no origin host is specified, the Load Balancer's IP address is used in the Host Header. +In the case of a Load Balancer origin, the specific host for which Edge Services requests and caches data. This is an optional setting: when specified, this host (e.g. `mydomain.com`) is used in the HTTP Host Header when Edge Services requests data from the Load Balancer. If no origin host is specified, the Load Balancer's IP address is used in the Host Header. The origin host must be associated with the origin Load Balancer / its backend servers, and only one host may be set per pipeline. If your Load Balancer is in front of multiple hosts, you can create a separate Edge Services pipeline for each. Each host will therefore get its own Edge Services endpoint and cache. diff --git a/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx b/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx index eb9f780cfb..018a28d751 100644 --- a/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx +++ b/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx @@ -3,7 +3,7 @@ title: Creating and managing an Instance with CLI (v2) description: This page explains how to create and manage a Scaleway Instance with CLI (v2) tags: instance create manage cli cli-v2 scw dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2021-08-05 --- import Requirements from '@macros/iam/requirements.mdx' @@ -19,7 +19,7 @@ Scaleway Instances provide you with resources to develop, test code and deploy y - 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 -- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- Created an [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - A valid [API key](/iam/how-to/create-api-keys/) - Downloaded and installed the [Scaleway CLI v2](https://github.com/scaleway/scaleway-cli#scaleway-cli-v2) @@ -42,7 +42,7 @@ Scaleway Instances provide you with resources to develop, test code and deploy y Do you want to override the current config? (Y/n): ``` -2. Unless you want to change your configuration, you can type `n` and go directly to the [Creating an Instance](#creating-an-instance) step of this tutorial. +2. Unless you want to change your configuration, type `n` and go directly to the [Creating an Instance](#creating-an-instance) step of this tutorial. If you have not yet configured the CLI, you will be guided through the configuration process via a series of questions: @@ -68,7 +68,7 @@ Scaleway Instances provide you with resources to develop, test code and deploy y To enable autocomplete, scw needs to update your shell configuration. What type of shell are you using (default: zsh): ``` -4. Hit enter if the default shell type is already correct for you. Otherwise, enter your shell type and hit enter. +4. Enter your shell type and hit enter. ``` To enable autocomplete we need to append to /Users/yourusername/.zshrc the following lines: # Scaleway CLI autocomplete initialization. @@ -118,7 +118,7 @@ Scaleway Instances provide you with resources to develop, test code and deploy y Replace `xx-xxx-x` with the Availability Zone you want to create your Instance in. If you want your Availability Zone to be France, Paris 1, for example, use `fr-par-1`. Refer to our [documentation](/instances/concepts/#availability-zone) for more information about Availability Zones. - You will see an output like the following: + An output similar to the following should display: ``` ID 12345678-1234-1234-4321-123456789123 @@ -182,7 +182,7 @@ Scaleway Instances provide you with resources to develop, test code and deploy y State available Zone fr-par-1 ``` -2. Write down the ID of your Instance. You will need it in the next steps. +2. Write down the ID of your Instance, as you will need it in the next steps. ## Creating and attaching a block volume to an Instance @@ -205,7 +205,7 @@ Scaleway Instances provide you with resources to develop, test code and deploy y State available ``` 2. Write down your block volume's ID. You will need it in the next steps. -3. Type the following command in your terminal to attach your block volume to your Instance. Make sure you replace `n4m3-0f-y0Ur-s3rv3r-id` by your server ID and `n4m3-0f-y0Ur-volume-id` by your volume ID. +3. Type the following command in your terminal to attach your block volume to your Instance. Make sure you replace `n4m3-0f-y0Ur-s3rv3r-id` with your server ID and `n4m3-0f-y0Ur-volume-id` with your volume ID. `scw instance server attach-volume server-id=n4m3-0f-y0Ur-s3rv3r-id volume-id=n4m3-0f-y0Ur-volume-id` @@ -272,7 +272,7 @@ Your Instance has been powered off. ## Deleting an Instance - This action will delete all your volumes and data located on your storage server. To avoid losing data, it is recommended to perform regular snapshots. + This action will delete all your volumes and data located on your Instance. To avoid losing data, it is recommended to perform regular snapshots. Ensure your Instance is powered off and then run the following command, replacing "your-server" with the ID of your server. diff --git a/pages/instances/api-cli/migrating-instances.mdx b/pages/instances/api-cli/migrating-instances.mdx index 12b24aa00d..42e3596242 100644 --- a/pages/instances/api-cli/migrating-instances.mdx +++ b/pages/instances/api-cli/migrating-instances.mdx @@ -3,13 +3,13 @@ title: Changing the commercial type of an Instance with the API or CLI description: This page explains how to change the commercial type of a Scaleway Instance with the API or CLI tags: upgrade instance api dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' -It is possible to change the commercial type of an Instance by using the [Scaleway CLI tool](/scaleway-cli/quickstart/) or the [Instances API](https://www.scaleway.com/en/developers/api/instance/). +It is possible to change the commercial type of an Instance using the [Scaleway CLI](/scaleway-cli/quickstart/) or the [Instances API](https://www.scaleway.com/en/developers/api/instance/). To do so, you need the Instance’s ID and a valid API key. diff --git a/pages/instances/how-to/configure-reverse-dns.mdx b/pages/instances/how-to/configure-reverse-dns.mdx index 5718202705..8d638b8b32 100644 --- a/pages/instances/how-to/configure-reverse-dns.mdx +++ b/pages/instances/how-to/configure-reverse-dns.mdx @@ -3,7 +3,7 @@ title: How to configure reverse DNS of an Instance description: This page explains how to configure the reverse DNS record of a Scaleway Instance. tags: configure reverse-dns dns instance dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/instances/how-to/delete-instance.mdx b/pages/instances/how-to/delete-instance.mdx index ecce3deb6a..2b35e303b9 100644 --- a/pages/instances/how-to/delete-instance.mdx +++ b/pages/instances/how-to/delete-instance.mdx @@ -3,13 +3,13 @@ title: How to delete an Instance description: This page explains how to delete a Scaleway Instance. tags: delete instance dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' -This page shows you how to delete an Instance. +This page shows you how to delete an Instance using the Scaleway console. Deleting an Instance is an **irreversible action**. Any data stored on your Instance will be lost. diff --git a/pages/instances/how-to/migrate-instances.mdx b/pages/instances/how-to/migrate-instances.mdx index 92481bdfc2..52e51ab4f2 100644 --- a/pages/instances/how-to/migrate-instances.mdx +++ b/pages/instances/how-to/migrate-instances.mdx @@ -3,13 +3,13 @@ title: How to migrate Instances description: This page explains how migrate from one Scaleway Instance to another tags: instance migration migrate dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' -The Scaleway platform makes it very easy to migrate your data from one Instance to another or upgrade your Instance to a more powerful one if your requirements grow. +The Scaleway console makes it very easy to migrate your data from one Instance to another or upgrade your Instance to a more powerful one if your requirements grow. For more information about choosing the best Instance type to migrate to for your use case, see our [dedicated documentation](/instances/reference-content/choosing-instance-type/). @@ -31,10 +31,10 @@ Follow the instructions to [create an image](/instances/how-to/create-a-backup/# 3. Click the **Images** tab. 4. Click next to the Instance's image. 5. Select **Create Instance from image** on the drop-down list. You are redirected to the Instance creation wizard, where the image has been preselected for you at step 2. -6. Finish configuring the Instance according to your requirements. Notably: +6. Finish configuring the Instance according to your requirements: - You are free to choose your Instance type as long it uses the same CPU architecture (e.g. ARM to ARM or x86 to x86) - Click **Advanced options** and use the toggle to deselect **flexible IP**. This creates a the new Instance without a flexible IP, as we are going to attach the one from the existing Instance in the next step. -7. Click **Create Instance** to finish. The Instance is created and shows in your Instances list. +7. Click **Create Instance** to finish. The Instance is created and displays in your Instances list. ## How to move a flexible IP to a new Instance diff --git a/pages/instances/how-to/use-boot-modes.mdx b/pages/instances/how-to/use-boot-modes.mdx index 92d9b012a0..29564b7e14 100644 --- a/pages/instances/how-to/use-boot-modes.mdx +++ b/pages/instances/how-to/use-boot-modes.mdx @@ -3,7 +3,7 @@ title: How to use boot modes on Instances description: This page explains how to use boot modes for Scaleway Instances. tags: boot-mode boot mode boot instance bootscript dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' @@ -43,14 +43,14 @@ Local boot allows you to start your Instance with a local configuration and a sp Rescue mode restarts your Instance via the network on a minimal operating system. You can use rescue mode to debug your Instance and recover your system data. 1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. -2. Click the Instance you wish to boot into Rescue Mode. +2. Click the Instance you wish to boot into rescue mode. 3. Use the toggle in the top right corner of the screen to **power off** your Instance. 4. Click the **Advanced settings** tab. 5. In the **Boot mode** section, select **Use rescue image**. 6. Click **Save**. 7. Use the toggle in the top right corner of the screen to **power on** your Instance. - Your Instance starts in Rescue mode. + Your Instance starts in rescue mode. ## How to use cloud-init diff --git a/pages/instances/how-to/use-flexips.mdx b/pages/instances/how-to/use-flexips.mdx index a4e115fffd..8ee940af8f 100644 --- a/pages/instances/how-to/use-flexips.mdx +++ b/pages/instances/how-to/use-flexips.mdx @@ -3,7 +3,7 @@ title: How to use flexible IP addresses with Instances description: This page explains how to use flexible IP addresses with Scaleway Instances. tags: flexible-ip Instance flexible ip detach delete attach ipv6 dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' @@ -89,9 +89,9 @@ Before routed IPs, IPv6 addresses were statically routed to the hypervisors, whi ### IPv6 prefix and SLAAC -Now, let's dive into the routed IPv6. Whenever you book a `routed_ipv6` IP type, you get assigned a full IPv6 prefix of 64 bits in length. According to [section 2.4](https://datatracker.ietf.org/doc/html/rfc4291#section-2.4) of the RFC4291, except for a few prefixes, anything is a Global Unicast address type. Today's [best practice](https://www.ripe.net/publications/docs/ripe-690/#4-1-1---64-prefix-from-a-dedicated-pool-of-ipv6-prefixes) is to provide a /64 prefix. +Now, let's dive into the routed IPv6. Whenever you book a `routed_ipv6` IP type, you get assigned a full IPv6 prefix of 64 bits in length. According to [section 2.4](https://datatracker.ietf.org/doc/html/rfc4291#section-2.4) of the RFC4291, except for a few prefixes, anything is a Global Unicast address type. Today's [best practice](https://www.ripe.net/publications/docs/ripe-690/#4-1-1---64-prefix-from-a-dedicated-pool-of-ipv6-prefixes) is to provide a `/64` prefix. -Another reason we decided to provide you with a /64 prefix is to be able to use [SLAAC](https://datatracker.ietf.org/doc/html/rfc4862) as the configuration mechanism. But SLAAC has been designed to work [exclusively with /64 prefixes](https://notes.networklessons.com/ipv6-prefix-length-used-for-slaac). +Another reason we decided to provide you with a `/64` prefix is to be able to use [SLAAC](https://datatracker.ietf.org/doc/html/rfc4862) as the configuration mechanism. But SLAAC has been designed to work [exclusively with /64 prefixes](https://notes.networklessons.com/ipv6-prefix-length-used-for-slaac). We chose SLAAC over DHCPv6 because it doesn't require any client-side configuration in most cases, allowing the feature to work with old Instances too. @@ -143,13 +143,13 @@ One consequence is that, if you move your `routed_ipv6` **prefix** to another In ## Workaround -Since the whole /64 prefix is routed to your Instance, it is possible to define a second IPv6 address within the prefix that may be used to reach your Instance. However, this requires some custom settings. +Since the whole `/64` prefix is routed to your Instance, it is possible to define a second IPv6 address within the prefix that may be used to reach your Instance. However, this requires some custom settings. In order to do that, we will use the **cloud-init** mechanism to define the second IPv6 address. Let's say your prefix is: `2025:bd8:911::/64` -We will use the following /128 address within this range: `2025:bd8:911:a7f1::1/128`. +We will use the following `/128` address within this range: `2025:bd8:911:a7f1::1/128`. The cloud-init configuration can be uploaded with the Scaleway CLI: diff --git a/pages/instances/how-to/use-placement-groups.mdx b/pages/instances/how-to/use-placement-groups.mdx index 31815436ef..4b7cdc43c9 100644 --- a/pages/instances/how-to/use-placement-groups.mdx +++ b/pages/instances/how-to/use-placement-groups.mdx @@ -3,7 +3,7 @@ title: How to use placement groups description: This page explains how to use placement groups with Scaleway Instances. tags: placement-group instance dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' @@ -23,15 +23,15 @@ import Requirements from '@macros/iam/requirements.mdx' 2. Click the **Placement groups** tab. 3. Click **Create placement group**. The creation wizard displays. 4. Complete the following steps in the wizard: - - Enter a **name** for your placement group, or leave the randomly-generated name in place. - - Choose an **Availability Zone**, which is the geographical region where your placement group will be created. You can only add Instances from this same Availability Zone to the placement group. + - Enter a **name** for your placement group, or leave the randomly-generated name in place + - Choose an **Availability Zone**, which is the geographical region where your placement group will be created. You can only add Instances from this same Availability Zone to the placement group - Choose the **type** of placement group: - **Low Latency** groups ensure that Instances are located as close as possible to each other - **Maximum Availability** groups ensure that Instances do not run on the same physical hypervisor - Choose the **policy** for your placement group: - - **Enforced**: if the group cannot be applied, only Instances on hypervisors matching the group settings will boot. - - **Optional**: ensures the application of the placement group's settings wherever possible, but lets Instances boot on hypervisors that do not match the group policy. - - Add **CPU & GPU Instances** to the placement group. + - **Enforced**: if the group cannot be applied, only Instances on hypervisors matching the group settings will boot + - **Optional**: ensures the application of the placement group's settings wherever possible, but lets Instances boot on hypervisors that do not match the group policy + - Add **CPU & GPU Instances** to the placement group You can only add powered off Instances to a placement group. @@ -47,7 +47,7 @@ import Requirements from '@macros/iam/requirements.mdx' 1. Go to the **Placement groups** tab, accessible from the **CPU & GPU Instances** page under the **Compute** section of the side menu. A list of your placement groups displays. 2. Click the placement group you want to add Instances to. You are taken to the **Overview** for that placement group. 3. Click the **CPU & GPU Instances** tab. -4. Use the drop-down menu to select the Instance you want to add, then click **Add Instance** +4. Use the drop-down menu to select the Instance you want to add, then click **Add Instance**. You can add up to 20 Instances to each of your placement groups. @@ -64,13 +64,12 @@ You are returned to the list of Instances attached to your placement group, wher 2. Click the placement group you wish to remove Instances from. You are taken to the **Overview** for that placement group. 3. Click the **CPU & GPU Instances** tab. 4. Click next to the Instance you want to remove, then click **Remove**. - A pop-up displays. 5. Confirm that you want to remove the Instance by clicking the **Remove from placement group** button. You are returned to the list of Instances attached to your placement group, where the Instance you removed no longer displays. - You can also remove an Instance from a placement group from the Instances page (accessible by clicking **CPU & GPU Instances** in the **Compute** section of the console side menu). From there, click the name of the Instance in question, then scroll down to the **Placement group** section of the Instance Overview tab. Click next to the placement group you want to manage, and select **Remove** from the drop-down menu, confirming your choice when prompted. + You can also remove an Instance from a placement group from the Instances page (accessible by clicking **CPU & GPU Instances** in the **Compute** section of the console side menu). From there, click the name of the Instance, then scroll down to the **Placement group** section of the Instance Overview tab. Click next to the placement group you want to manage, and select **Remove** from the drop-down menu, confirming your choice when prompted. ## How to change an Instance's placement group diff --git a/pages/instances/how-to/use-private-networks.mdx b/pages/instances/how-to/use-private-networks.mdx index ec60d9afa6..36a28a41e1 100644 --- a/pages/instances/how-to/use-private-networks.mdx +++ b/pages/instances/how-to/use-private-networks.mdx @@ -3,7 +3,7 @@ title: How to use Private Networks with your Instances description: This page explains how to use Private Networks for Scaleway Instances tags: private-networks private networks instance dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' @@ -21,7 +21,7 @@ Private Networks are LAN-like layer 2 ethernet networks. A new network interface ## How to create a new Private Network -The procedure below shows you how to create a new Private Network to attach to an existing Instance. The Private Network will have default settings, with an auto-generated [CIDR block](/vpc/concepts/#cidr-block)). This CIDR block will be used to allocate private IP addresses to Instances attached to the network. Each Instance will get an IPv4 and an IPv6 address on the Private Network. +The procedure below shows you how to create a new Private Network to attach to an existing Instance. The Private Network will have default settings, with an auto-generated [CIDR block](/vpc/concepts/#cidr-block). This CIDR block will be used to allocate private IP addresses to Instances attached to the network. Each Instance will get an IPv4 and an IPv6 address on the Private Network. If you want to create a Private Network without immediately attaching any resources or create it in a specific VPC or with a custom CIDR block, follow [this procedure instead](/vpc/how-to/create-private-network/). diff --git a/pages/instances/how-to/use-security-groups.mdx b/pages/instances/how-to/use-security-groups.mdx index 193314e8ba..786c8bcc9b 100644 --- a/pages/instances/how-to/use-security-groups.mdx +++ b/pages/instances/how-to/use-security-groups.mdx @@ -3,7 +3,7 @@ title: How to use security groups description: Learn how to create, edit, and configure security groups on Scaleway Instances to control traffic and enhance security. tags: security create instance traffic security-group dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/instances/how-to/use-serial-console.mdx b/pages/instances/how-to/use-serial-console.mdx index 34e26bd011..b63fa4799f 100644 --- a/pages/instances/how-to/use-serial-console.mdx +++ b/pages/instances/how-to/use-serial-console.mdx @@ -3,7 +3,7 @@ title: How to use the serial console to connect to an Instance description: This page explains how to use the serial console to connect to a Scaleway Instance. tags: serial console serial-console instance connection dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2022-02-25 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/instances/reference-content/general-purpose.mdx b/pages/instances/reference-content/general-purpose.mdx index b8cce0f849..55c7522d1b 100644 --- a/pages/instances/reference-content/general-purpose.mdx +++ b/pages/instances/reference-content/general-purpose.mdx @@ -2,7 +2,7 @@ title: The right Instance for production purposes description: Find out more about Instances from Scaleway's General Purpose range. dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2023-02-22 tags: instance type production general purpose range POP --- @@ -11,7 +11,7 @@ An Instance is a virtual machine in the cloud. Scaleway supports several [types ## POP2 Instances -Scaleway's **General Purpose** range includes POP2 Instances. POP2 Instances are high-end, dedicated cloud Instances for demanding workloads. They offer the highest consistent performance per core to support real-time applications. In addition, their computing power makes them generally more robust for compute-intensive workloads. +Scaleway's **General Purpose** range includes POP2 Instances, which are high-end, dedicated cloud Instances for demanding workloads. They offer the highest consistent performance per core to support real-time applications. In addition, their computing power makes them generally more robust for compute-intensive workloads. They are best suited for production websites, demanding applications, high-traffic databases, and any application that requires 100% sustained CPU usage such as monitoring and analytics software. This includes Prometheus and Grafana, gaming sessions, and ad serving. @@ -30,7 +30,7 @@ See below the technical specifications of General Purpose Instances: ## PLAY2 Instances and PRO2 Instances -In the same **General Purpose** range, you will also find PLAY2 and PRO2 Instances. These are the next generation of General Purpose and General Purpose Instances. They offer the best price-performance ratio with the most flexible vCPU to RAM ratio, and provide features that target most standard and cloud-native workloads. In other words, these Instances keep costs down while still supporting a wide variety of cloud applications, such as medium-to-high-traffic web servers, medium-sized databases, and e-commerce websites. +In the same **General Purpose** range, you will also find PLAY2 and PRO2 Instances. These are the next generation of General Purpose Instances. They offer the best price-performance ratio with the most flexible vCPU to RAM ratio, and provide features that target most standard and cloud-native workloads. In other words, these Instances keep costs down while still supporting a wide variety of cloud applications, such as medium-to-high-traffic web servers, medium-sized databases, and e-commerce websites. See below the technical specifications of PLAY2 and PRO2 Instances: @@ -60,7 +60,7 @@ The table below displays the technical specifications of COP-ARM Instances: | CPU type | ARM (Ampere Altra Max M128-30) | | Resources | Shared vCPUs | | Sizing | From 2 to 128 vCPUs
From 8 to 128 GiB RAM | -| vCPU:RAM ratio | 1:4 +| vCPU:RAM ratio | 1:4 | ## Complementary services To help build and manage your applications, consider complementing your General Purpose Instances with the following compatible services: diff --git a/pages/instances/reference-content/instances-datasheet.mdx b/pages/instances/reference-content/instances-datasheet.mdx index 235834d293..7b6b871b1c 100644 --- a/pages/instances/reference-content/instances-datasheet.mdx +++ b/pages/instances/reference-content/instances-datasheet.mdx @@ -3,7 +3,7 @@ title: Scaleway Instances datasheet description: This page shows the technical characteristics of the different Scaleway Instance offers. tags: dedibox server dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2023-12-18 --- diff --git a/pages/instances/troubleshooting/bootscript-eol.mdx b/pages/instances/troubleshooting/bootscript-eol.mdx index c431710e74..dbd3df649a 100644 --- a/pages/instances/troubleshooting/bootscript-eol.mdx +++ b/pages/instances/troubleshooting/bootscript-eol.mdx @@ -3,18 +3,17 @@ title: Dealing with the end of life of the bootscript feature description: This page helps you migrating your Scaleway Instance following the EOL of the bootscript feature tags: bootscript boot-script instance boot script dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2023-02-20 --- import Requirements from '@macros/iam/requirements.mdx' -Some legacy Instance types (e.g. **VC1-x**, **X64-x**, **Start1-x**) supported the option to use a bootscript (a preconfigured boot configuration) to start your Instance. This boot method was also available on **DEV1-x**, **GP1-x**, and **STARDUST1** Instances. This feature is now deprecated and will no longer be supported. +Some legacy Instance types (e.g. **VC1-x**, **X64-x**, **Start1-x**) supported the option to use a bootscript (a preconfigured boot configuration) to start your Instance. This boot method was also available on **DEV1-x**, **GP1-x**, and **STARDUST1** Instances. This feature is now deprecated and no longer supported. If you are still using one of these Instance types with a bootscript, you have to change your boot configuration in order to keep your Instance operational. -You can find information about the Instances quotas allocated to your account at the following link: [Understanding Organization quotas](/organizations-and-projects/additional-content/organization-quotas/). - +You can find information about the Instances quotas allocated to your account in the [Understanding Organization quotas](/organizations-and-projects/additional-content/organization-quotas/) documentation page. If you want to keep using legacy Instance types, you will not be able to create them through the console interface. However, you can still create them using the [Scaleway CLI](/instances/api-cli/creating-managing-instances-with-cliv2/) as you normally would or through the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instances-create-an-instance), as long as you stay within your allocated quotas. [Check your Organization's quota usage in the Scaleway console](https://console.scaleway.com/organization/settings). diff --git a/pages/instances/troubleshooting/change-rescue-mode.mdx b/pages/instances/troubleshooting/change-rescue-mode.mdx index 4ee43ca7fa..37ff6eb273 100644 --- a/pages/instances/troubleshooting/change-rescue-mode.mdx +++ b/pages/instances/troubleshooting/change-rescue-mode.mdx @@ -3,7 +3,7 @@ title: Changing the rescue mode of your Instance description: This page helps you switch your Scaleway Instance to the new rescue mode tags: rescue rescuemode bootscript boot-script instance boot script dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2023-05-04 --- import Requirements from '@macros/iam/requirements.mdx' @@ -16,7 +16,7 @@ This is particularly useful when your Instance is not booting properly due to co - 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 -- An [Instance](/instances/how-to/create-an-instance/) +- Created an [Instance](/instances/how-to/create-an-instance/) - A valid [API key](/iam/how-to/create-api-keys/) ## Updating rescue mode from the Scaleway console @@ -33,10 +33,10 @@ This is particularly useful when your Instance is not booting properly due to co ## Updating rescue mode using the Scaleway API -1. [List the Instances](https://www.scaleway.com/en/developers/api/instance/#path-instances-list-all-instances) of your Project(s). +1. [List the Instances](https://www.scaleway.com/en/developers/api/instance/#path-instances-list-all-instances) located in your Project(s). 2. Filter the returned Instances to keep only the ones with `boot_type: "rescue"`. -3. [Stop the Instances](https://www.scaleway.com/en/developers/api/instance/#path-instances-perform-action) -4. [Update the Instances](https://www.scaleway.com/en/developers/api/instance/#path-instances-update-an-instance) and set `boot_type: "local"` +3. [Stop the Instances](https://www.scaleway.com/en/developers/api/instance/#path-instances-perform-action). +4. [Update the Instances](https://www.scaleway.com/en/developers/api/instance/#path-instances-update-an-instance) and set `boot_type: "local"`. If you still want to use rescue mode for your Instance(s), update these Instances again and switch back the `boot_type` to “rescue”. They will then use the updated rescue system. diff --git a/pages/load-balancer/how-to/create-manage-routes.mdx b/pages/load-balancer/how-to/create-manage-routes.mdx index ab2ff9a170..020907dda6 100644 --- a/pages/load-balancer/how-to/create-manage-routes.mdx +++ b/pages/load-balancer/how-to/create-manage-routes.mdx @@ -1,9 +1,9 @@ --- title: How to create and manage routes -description: Learn how to efficiently create and manage routes with Scaleway's Load Balancer, ensuring seamless traffic distribution and enhanced network performance. +description: Learn how to efficiently create and manage routes with Scaleway's Load Balancer, ensuring seamless traffic distribution and enhanced network performance. tags: route rules load-balancer sni host-header target-backend dates: - validation: 2025-03-05 + validation: 2025-09-11 posted: 2023-02-08 --- import Requirements from '@macros/iam/requirements.mdx' @@ -87,4 +87,3 @@ Routes allow you to specify, for a given frontend, which backends it should dire 7. Confirm the action by clicking **Delete route**. - diff --git a/pages/load-balancer/how-to/use-edge-services.mdx b/pages/load-balancer/how-to/use-edge-services.mdx index e0af986bda..ef163c2bbb 100644 --- a/pages/load-balancer/how-to/use-edge-services.mdx +++ b/pages/load-balancer/how-to/use-edge-services.mdx @@ -2,7 +2,7 @@ title: How to create an Edge Services pipeline for a Load Balancer description: This page explains how to configure an Edge Services pipeline on your Load Balancer, enabling a caching service for faster and more efficient delivery. dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2024-10-15 tags: load-balancer edge-services cdn network cache domain https --- diff --git a/pages/load-balancer/troubleshooting/configuration.mdx b/pages/load-balancer/troubleshooting/configuration.mdx index e22be1fb81..24863480be 100644 --- a/pages/load-balancer/troubleshooting/configuration.mdx +++ b/pages/load-balancer/troubleshooting/configuration.mdx @@ -3,7 +3,7 @@ title: I am having problems configuring my Load Balancer description: Troubleshoot problems that you may experience when configuring your Load Balancer, such as adding backend servers, setting up Private Networks and dealing with security concerns. tags: load-balancer configuration backend server error security ip dates: - validation: 2025-03-06 + validation: 2025-09-11 posted: 2025-03-06 --- @@ -61,7 +61,7 @@ Proxy Protocol has not been activated on your Load Balancer, meaning that inform Activate [Proxy Protocol](/load-balancer/reference-content/configuring-backends/#proxy-protocol) on your Load Balancer, and ensure that your backend server is [correctly configured](/tutorials/proxy-protocol-v2-load-balancer/) to handle this protocol. -## Security rules are not being applied as expected, and I am having difficulties in filtering incoming traffic through my Load Balancer +## Security rules are not being applied as expected, and I am having difficulties in filtering incoming traffic through my Load Balancer You may find that traffic is not being filtered as expected via your Load Balancer, and that Instances in your backend are not dropping unauthorized traffic as expected. diff --git a/pages/load-balancer/troubleshooting/http-connection-errors.mdx b/pages/load-balancer/troubleshooting/http-connection-errors.mdx index 194f720441..70d22a7f97 100644 --- a/pages/load-balancer/troubleshooting/http-connection-errors.mdx +++ b/pages/load-balancer/troubleshooting/http-connection-errors.mdx @@ -3,11 +3,11 @@ title: I am experiencing connection problems and HTTP errors with my Load Balanc description: Troubleshoot connection problems and HTTP errors that you may experience when accessing applications served via your Load Balancer. Learn how to resolve common problems and get your application back up and running. tags: load-balancer http-errors bad-request dates: - validation: 2025-03-06 + validation: 2025-09-11 posted: 2025-03-06 --- -You may experience connection problems and HTTP errors when attempting to connect to an application served via your Load Balancer. +You may experience connection problems and HTTP errors when attempting to connect to an application served via your Load Balancer. This page helps you find solutions to some of these most common errors. @@ -26,7 +26,7 @@ You may find that when attempting to connect to the domain linked to your Load B - Verify your certificate and [SSL bridging/offloading/passthrough](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) settings. For example, if SSL is terminated at the Load Balancer, but the backend expects HTTPS, requests may be rejected. - Check if [Proxy Protocol](/load-balancer/reference-content/configuring-backends/#proxy-protocol) is enabled on your Load Balancer. If your backend server is not configured to handle Proxy Protocol headers correctly, it may reject the requests. Try [disabling Proxy Protocol](/load-balancer/how-to/manage-frontends-and-backends/#how-to-edit-backends-and-health-checks) on your Load Balancer to see if it resolves the issue. If the issue is resolved when Proxy Protocol is disabled, [ensure your backend server is correctly configured for Proxy Protocol](/tutorials/proxy-protocol-v2-load-balancer/) before re-enabling. -## I am getting a 503 Service Unavailable error when trying to access my application through my Load Balancer +## I am getting a 503 Service Unavailable error when trying to access my application through my Load Balancer You may find that when attempting to connect to the domain linked to your Load Balancer / the application being served by your backend servers, you receive a `503 Service Unavailable` error. @@ -41,7 +41,7 @@ You may find that when attempting to connect to the domain linked to your Load B - Check your Load Balancer's [backend protection settings](/load-balancer/reference-content/configuring-backends/#backend-protection), and compare with [Cockpit data](/load-balancer/how-to/monitor-lb-cockpit/). If backend protection compared to request/connection volume is set in such a way that all backend servers are becoming overloaded, you may need to add additional backend servers or adjust your backend protection settings. -## I am getting SSL protocol errors when trying to access my application through my Load Balancer +## I am getting SSL protocol errors when trying to access my application through my Load Balancer You may find that when attempting to connect to the domain linked to your Load Balancer / the application being served by your backend servers, you receive an error similar to one of the following @@ -65,5 +65,5 @@ There is a mismatch between the SSL/TLS protocol versions or configurations betw ### Solution - Check that the client or backend servers are not using older SSL protocols such as SSLv2 or SSLv3, which are considered insecure. -- Ensure that you have correctly configured [SSL bridging, offloading or passthrough](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) on your Load Balancer, depending on your use case. +- Ensure that you have correctly configured [SSL bridging, offloading or passthrough](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) on your Load Balancer, depending on your use case. - Ensure that you have not confused activation of the [Proxy Protocol](/load-balancer/reference-content/configuring-backends/#proxy-protocol) setting as anything to do with SSL bridging, offloading or passthrough, as it is unrelated. \ No newline at end of file diff --git a/pages/load-balancer/troubleshooting/k8s-errors.mdx b/pages/load-balancer/troubleshooting/k8s-errors.mdx index 894acf63f4..b2da54022a 100644 --- a/pages/load-balancer/troubleshooting/k8s-errors.mdx +++ b/pages/load-balancer/troubleshooting/k8s-errors.mdx @@ -3,7 +3,7 @@ title: I am experiencing problems with my Kubernetes Load Balancer description: Troubleshoot problems with your Kubernetes Load Balancer. Discover the solutions to common errors, and get your Load Balancer service back up and running. tags: load-balancer kubernetes annotations dates: - validation: 2025-03-06 + validation: 2025-09-11 posted: 2025-03-06 --- @@ -19,7 +19,7 @@ Always provision and modify Kubernetes Load Balancers via the [CCM](/kubernetes/ ## I'm experiencing connectivity issues with my Kubernetes Load Balancer -You may find that your Load Balancer is not connecting to nodes in your Kapsule cluster, meaning that health checks are failing and your application is inaccessible from the internet +You may find that your Load Balancer is not connecting to nodes in your Kapsule cluster, meaning that health checks are failing and your application is inaccessible from the internet. ### Cause @@ -47,13 +47,13 @@ The Load Balancer is not properly configured to handle requests from within the ## Solution: -Add an [annotation](/kubernetes/reference-content/kubernetes-load-balancer/#defining-your-load-balancers-configuration-via-annotations) to the Load Balancer configuration, to use the hostname to route requests: +Add an [annotation](/kubernetes/reference-content/kubernetes-load-balancer/#defining-your-load-balancers-configuration-via-annotations) to the Load Balancer configuration, to use the hostname to route requests: ``` -service.beta.kubernetes.io/scw-loadbalancer-use-hostname: "true" +service.beta.kubernetes.io/scw-loadbalancer-use-hostname: "true" ``` -By adding this annotation, the Load Balancer will use the hostname to route requests from within the cluster. +By adding this annotation, the Load Balancer will use the hostname to route requests from within the cluster. ## I am experiencing a different problem diff --git a/pages/secret-manager/api-cli/create-secret-with-type.mdx b/pages/secret-manager/api-cli/create-secret-with-type.mdx index 558f818463..54e5a38972 100644 --- a/pages/secret-manager/api-cli/create-secret-with-type.mdx +++ b/pages/secret-manager/api-cli/create-secret-with-type.mdx @@ -3,7 +3,7 @@ title: Creating a database credentials secret type description: Explore how to create a database credentials secret type using the API. Learn about the expected JSON formats for every secret type. tags: secret-management type secret-manager api create dates: - validation: 2025-03-03 + validation: 2025-09-11 posted: 2024-04-05 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/transactional-email/how-to/monitor-transactional-email-cockpit.mdx b/pages/transactional-email/how-to/monitor-transactional-email-cockpit.mdx index 377bfe62d9..e08fd8c4d5 100644 --- a/pages/transactional-email/how-to/monitor-transactional-email-cockpit.mdx +++ b/pages/transactional-email/how-to/monitor-transactional-email-cockpit.mdx @@ -3,7 +3,7 @@ title: How to monitor your Transactional Emails with Scaleway Cockpit description: Learn how to effectively monitor your Transactional Email using Scaleway Cockpit for optimal deliverability and performance. tags: transactional-email email-deliverability cockpit observability dashboard metrics logs alerts dates: - validation: 2025-03-05 + validation: 2025-09-11 posted: 2025-03-05 --- import Requirements from '@macros/iam/requirements.mdx' @@ -15,24 +15,21 @@ This page explains how to get started with Scaleway Cockpit for viewing your Tra -- A Scaleway account logged into the [console](https://console.scaleway.com) +- A Scaleway account logged into the Scaleway [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 - [Configured your domain(s) with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/) - Added [SPF, DKIM](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), [MX](/transactional-email/how-to/add-mx-record-to-your-domain/) and [DMARC](/transactional-email/how-to/add-dmarc-record/) records to your domain(s) -## How to activate your Cockpit - -Scaleway Cockpit is activated by default if you have created any [Scaleway resources integrated with Cockpit](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). - ## How to access the Grafana dashboard To view your TEM metrics, use the Grafana preconfigured dashboard which is accessible from the Scaleway console: + - First, you must create a user and their associated credentials (a username and password) for Grafana - Then, you can use these credentials to access Grafana from the Scaleway console, and visualize preconfigured dashboards for all your Scaleway products. 1. Create a Grafana user and retrieve their username and password by [following this procedure](/cockpit/how-to/retrieve-grafana-credentials/). -2. From the Scaleway console [Cockpit overview page](https://console.scaleway.com/cockpit/overview), click **Open dashboards** in the top right corner. +2. From the Scaleway console [Cockpit overview page](https://console.scaleway.com/cockpit/overview), click **Open dashboards** in the top right corner. The Grafana login screen displays. 3. Enter your Grafana username and password to log in. diff --git a/pages/vpc/reference-content/getting-most-private-networks.mdx b/pages/vpc/reference-content/getting-most-private-networks.mdx index b40ff96c99..e472e6684e 100644 --- a/pages/vpc/reference-content/getting-most-private-networks.mdx +++ b/pages/vpc/reference-content/getting-most-private-networks.mdx @@ -3,7 +3,7 @@ title: Getting the most from Private Networks description: Optimize your Scaleway VPCs, Private Networks and resource connectivity with this guide which details tips and best practices. tags: vpc private-network connectivity best-practice dates: - validation: 2025-03-05 + validation: 2025-09-11 posted: 2024-08-28 --- import image from './assets/scaleway-vpc-schema.webp' @@ -37,6 +37,7 @@ The [**VPC routing**](/vpc/concepts/#routing) feature allows for managed and cus When you start creating resources and building your infrastructure with Scaleway, take some time to consider and plan your network topology. We recommend that you build your VPC infrastructure with **separation of concerns** in mind. Separation of concerns is a fundamental design principle aimed at breaking down large complex systems into smaller, distinct components each with clear responsibilities and interfaces. This kind of design will future-proof your VPC and come into its own when Scaleway introduces further features such as ACLs for VPC. Separating resources into different Private Networks according to function and usage can: + - **Improve network performance** by reducing broadcast traffic and congestion - **Enhance manageability** via a logical organization of resources - **Enable easier troubleshooting, monitoring and maintenance** @@ -47,12 +48,12 @@ For example, you may use one Private Network for frontend resources and another When [creating a Private Network](/vpc/how-to/create-private-network/), you can let Scaleway automatically generate a CIDR block for it that is guaranteed to be unique in this VPC. All resources attached to the Private Network get a private IP address from this block. However, you also have the option to define your own CIDR block for the network. Ensure you choose a prefix and network size that is appropriate for your needs, does not overlap with that of any other Private Network in the VPC, and contains enough IP addresses for all resources that will be attached to the Private Network. -See our [Basic VPC use case](/vpc/reference-content/use-case-basic/) documentation for full details of how to create a simple infrastructure that leverages the advantages of Private Networks, including accompanying Terraform/OpenTofu templates. +See our [Basic VPC use case](/vpc/reference-content/use-case-basic/) documentation for full details on how to create a simple infrastructure that leverages the advantages of Private Networks, including accompanying Terraform/OpenTofu templates. ## Attaching resources to Private Networks -When you attach a resource (e.g. an Instance, an Elastic Metal server) to a Private Network, you can either: +When you attach a resource (e.g. an Instance, or an Elastic Metal server) to a Private Network, you can either: - Let Scaleway automatically assign any IP address from the Private Network's CIDR block to use for the attachment, or - Define a specific, reserved IP address from the CIDR block to use for the attachment.