diff --git a/pages/container-registry/how-to/connect-docker-cli.mdx b/pages/container-registry/how-to/connect-docker-cli.mdx index dcc58a7ff8..a318a158d9 100644 --- a/pages/container-registry/how-to/connect-docker-cli.mdx +++ b/pages/container-registry/how-to/connect-docker-cli.mdx @@ -3,7 +3,7 @@ title: How to connect your namespace to the Docker CLI description: Instructions for connecting Docker CLI to Scaleway's Container Registry. tags: namespace docker-cli container-registry dates: - validation: 2025-01-06 + validation: 2025-07-15 posted: 2019-02-25 categories: - container-registry diff --git a/pages/container-registry/how-to/pull-images.mdx b/pages/container-registry/how-to/pull-images.mdx index 8436bc641e..975717bc1c 100644 --- a/pages/container-registry/how-to/pull-images.mdx +++ b/pages/container-registry/how-to/pull-images.mdx @@ -3,7 +3,7 @@ title: How to pull images from your namespace description: Learn how to pull container images from Scaleway's Container Registry. tags: container-registry namespace dates: - validation: 2025-01-06 + validation: 2025-07-15 posted: 2019-02-25 categories: - container-registry diff --git a/pages/dedibox-scaleway/reference-content/dedibox-datasheet.mdx b/pages/dedibox-scaleway/reference-content/dedibox-datasheet.mdx index 29beec6e2e..fe26ad71a2 100644 --- a/pages/dedibox-scaleway/reference-content/dedibox-datasheet.mdx +++ b/pages/dedibox-scaleway/reference-content/dedibox-datasheet.mdx @@ -3,8 +3,7 @@ title: Dedibox datasheet description: This page shows the technical characteristics of the different Dedibox offers. tags: dedibox server dates: - validation: 2025-01-06 - posted: 2023-12-18 + validation: 2025-07-15 categories: - compute --- diff --git a/pages/dedibox/quickstart.mdx b/pages/dedibox/quickstart.mdx index 3c49cd1a0d..36c079e7cb 100644 --- a/pages/dedibox/quickstart.mdx +++ b/pages/dedibox/quickstart.mdx @@ -139,7 +139,7 @@ To connect to your Instance from Windows, you will need to use a small applicati 3. Enter your Instance's IP address in the **Hostname** field. To find the IP address of your Instance, log into the Scaleway console and - click **Instances** in the Compute section of the side menu. A list of your + click **CPU & GPU Instances** in the Compute section of the side menu. A list of your Instances and their associated IP addresses will display. diff --git a/pages/elastic-metal/api-cli/elastic-metal-with-api.mdx b/pages/elastic-metal/api-cli/elastic-metal-with-api.mdx index 5d59d978d2..14dfcd0a5d 100644 --- a/pages/elastic-metal/api-cli/elastic-metal-with-api.mdx +++ b/pages/elastic-metal/api-cli/elastic-metal-with-api.mdx @@ -3,7 +3,7 @@ title: Deploying an Elastic Metal server with one API call description: Learn how to deploy a Scaleway Elastic Metal server on your favorite OS with a single API command. tags: baremetal elastic metal cloud server dedicated elastic-metal api-call dates: - validation: 2025-01-02 + validation: 2025-07-15 posted: 2021-05-26 categories: - bare-metal @@ -34,13 +34,13 @@ Besides creating your Elastic Metal servers from the graphical [Scaleway console 1. Open a terminal on your computer and set your secret API key, your SSH key ID, and your Project ID as variables. - ``` + ```sh export SCW_SECRET_KEY="" export SCW_SSH_KEY="" export SCW_PROJECT_ID="" ``` 2. Retrieve a list of all operating systems available in the desired Availability Zone. - ``` + ```sh curl https://api.scaleway.com/baremetal/v1/zones/fr-par-2/offers -H "X-Auth-Token: $SCW_SECRET_KEY" | jq . | grep "EM-" ``` @@ -67,7 +67,7 @@ Besides creating your Elastic Metal servers from the graphical [Scaleway console You will receive a JSON-formatted list of all operating systems available, and their associated ID. Take note of the ID of the image you want to install: - ``` + ```json { "total_count": 8, "os": [ @@ -88,7 +88,7 @@ Besides creating your Elastic Metal servers from the graphical [Scaleway console 4. Create the Elastic Metal server from the API using cURL and the `POST` command on the endpoint `/baremetal/v1/zones/fr-par-2/servers`: The syntax to [create the server](https://www.scaleway.com/en/developers/api/elastic-metal/#path-servers-create-an-elastic-metal-server) is as follows: - ``` + ```json { "offer_id": "", "project_id": "$SCW_SECRET_KEY", @@ -109,14 +109,28 @@ Besides creating your Elastic Metal servers from the graphical [Scaleway console In the following example, we create a server running on Ubuntu 20.04 LTS: - ``` - curl -X POST -H "X-Auth-Token: $SCW_KEY" -H "Content-Type: application/json" -d "{ \"offer_id\": \"7fde3890-9787-488c-ac89-c4e00a4e5f83\", \"project_id\": \"$SCW_PROJECT\", \"name\": \"my-bmaas\", \"description\": \"my server running on ubuntu\", \"tags\": [ - \"bmaas, tutorial\" ], \"install\": { \"os_id\": \"03b7f4ba-a6a1-4305-984e-b54fafbf1681\", \"hostname\": \"my-bmaas-api\", \"ssh_key_ids\": [ \"$SSH_KEY_ID\" ] }}" https://api.scaleway.com/baremetal/v1/zones/fr-par-2/servers | jq . + ```json + curl -X POST \ + -H "X-Auth-Token: $SCW_KEY" \ + -H "Content-Type: application/json" \ + -d '{ + "offer_id": "7fde3890-9787-488c-ac89-c4e00a4e5f83", + "project_id": "$SCW_PROJECT", + "name": "my-bmaas", + "description": "my server running on ubuntu", + "tags": ["bmaas", "tutorial"], + "install": { + "os_id": "03b7f4ba-a6a1-4305-984e-b54fafbf1681", + "hostname": "my-bmaas-api", + "ssh_key_ids": ["$SSH_KEY_ID"] + } + }' \ + https://api.scaleway.com/baremetal/v1/zones/fr-par-2/servers | jq . ``` Again, the API returns a JSON output informing you about the server creation: - ``` + ```json { "id": "", "organization_id": "", @@ -146,7 +160,7 @@ Besides creating your Elastic Metal servers from the graphical [Scaleway console } ``` 5. The server is being delivered to your account and is automatically being installed on the operating system chosen. You can retrieve the status of the installation using the following API call: - ``` + ```sh curl https://api.scaleway.com/baremetal/v1/zones/fr-par-2/servers/{server_id} -H "X-Auth-Token: $SCW_SECRET_KEY" | jq . ``` diff --git a/pages/elastic-metal/api-cli/elastic-metal-with-cli.mdx b/pages/elastic-metal/api-cli/elastic-metal-with-cli.mdx index 492d3f6b6e..80f972e6fd 100644 --- a/pages/elastic-metal/api-cli/elastic-metal-with-cli.mdx +++ b/pages/elastic-metal/api-cli/elastic-metal-with-cli.mdx @@ -3,7 +3,7 @@ title: Create and manage Elastic Metal servers with the Scaleway CLI description: Learn to create and manage Elastic Metal servers using the Scaleway CLI in this comprehensive guide. tags: elastic-metal command-line-interface cli scw dates: - validation: 2025-01-02 + validation: 2025-07-15 posted: 2021-05-26 categories: - bare-metal @@ -35,7 +35,7 @@ The [Scaleway Command Line Interface (CLI)](https://github.com/scaleway/scaleway 1. Type the following command in your terminal to create your Elastic Metal server: - ``` + ```sh scw baremetal server create name=name-of-your-server type=EM-A210R-SATA zone=fr-par-2 ``` @@ -77,7 +77,9 @@ The [Scaleway Command Line Interface (CLI)](https://github.com/scaleway/scaleway 1. Type the following command in your terminal to see a list of available OSes: - `scw baremetal os list zone=fr-par-2` + ```sh + scw baremetal os list zone=fr-par-2 + ``` An output with available OSes and their associated IDs displays: @@ -94,7 +96,7 @@ The [Scaleway Command Line Interface (CLI)](https://github.com/scaleway/scaleway ``` 2. Write down the ID of the OS you want to install. 3. Type the following command to display the list of your SSH key's ID: - ``` + ```sh scw iam ssh-key list ``` @@ -106,7 +108,7 @@ The [Scaleway Command Line Interface (CLI)](https://github.com/scaleway/scaleway ``` 4. Write down your SSH key ID, as you will need it in the next steps. 5. Type the following command to install an OS on your Elastic Metal server: - ``` + ```sh scw baremetal server install ID-of-your-elastic-metal-server os-id=ID-of-OS-you-want-to-install hostname=hostname-for-your-server ssh-key-ids.0=your-ssh-key-ID zone=fr-par-2 ``` @@ -164,7 +166,7 @@ There are many other functionalities you can access for your Elastic Metal serve Type the following command in your terminal: -``` +```sh scw baremetal server start your-elastic-metal-server-ID zone=fr-par-2 ``` The following output displays, and you will see "starting" next to the `Status` field: @@ -216,7 +218,7 @@ PingStatus up Type the following command in your terminal: -``` +```sh scw baremetal server stop your-elastic-metal-server-ID zone=fr-par-2 ``` @@ -264,7 +266,7 @@ PingStatus up Type the following command: -``` +```sh scw baremetal server reboot your-elastic-metal-server-ID zone=fr-par-2 ``` @@ -316,7 +318,7 @@ PingStatus down Type the following command in your terminal: -``` +```sh scw baremetal server delete your-elastic-metal-server-ID zone=fr-par-2 ``` @@ -352,7 +354,7 @@ PingStatus down Enter the following command to make sure that your server has been deleted: -``` +```sh scw baremetal server list zone=fr-par-2 ``` diff --git a/pages/elastic-metal/how-to/activate-remote-access.mdx b/pages/elastic-metal/how-to/activate-remote-access.mdx index fd32cc59be..6106c5fd38 100644 --- a/pages/elastic-metal/how-to/activate-remote-access.mdx +++ b/pages/elastic-metal/how-to/activate-remote-access.mdx @@ -3,7 +3,7 @@ title: How to activate remote access on an Elastic Metal server description: Learn how to activate remote access on a Scaleway Elastic Metal server with this step-by-step guide. tags: remote-access elastic-metal dates: - validation: 2025-01-02 + validation: 2025-07-16 posted: 2022-03-30 categories: - bare-metal diff --git a/pages/elastic-metal/how-to/adjust-available-bandwidth.mdx b/pages/elastic-metal/how-to/adjust-available-bandwidth.mdx index 14f3d23d35..cdf561a8ce 100644 --- a/pages/elastic-metal/how-to/adjust-available-bandwidth.mdx +++ b/pages/elastic-metal/how-to/adjust-available-bandwidth.mdx @@ -3,7 +3,7 @@ title: How to adjust the available bandwidth for an Elastic Metal server description: Discover step-by-step instructions for adjusting (upgrading or downgrading) the available bandwidth for your Elastic Metal server. tags: elastic-metal bandwidth putty dates: - validation: 2025-01-06 + validation: 2025-07-16 posted: 2024-06-11 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/elastic-metal/how-to/get-use-loyalty-reward.mdx b/pages/elastic-metal/how-to/get-use-loyalty-reward.mdx index ed42d3a3d3..975848fef7 100644 --- a/pages/elastic-metal/how-to/get-use-loyalty-reward.mdx +++ b/pages/elastic-metal/how-to/get-use-loyalty-reward.mdx @@ -3,7 +3,7 @@ title: How to get and use a loyalty reward description: This page explains how to use the loyalty reward for Scaleway Elastic Metal servers tags: elastic-metal payback commitment fee dates: - validation: 2025-01-02 + validation: 2025-07-16 posted: 2022-12-01 categories: - bare-metal diff --git a/pages/elastic-metal/how-to/shutdown-server.mdx b/pages/elastic-metal/how-to/shutdown-server.mdx index e1d99a8d27..747b4baf6c 100644 --- a/pages/elastic-metal/how-to/shutdown-server.mdx +++ b/pages/elastic-metal/how-to/shutdown-server.mdx @@ -3,7 +3,7 @@ title: How to shut down an Elastic Metal server description: This page explains how to shut down a Scaleway Elastic Metal server tags: shut-down elastic-metal dates: - validation: 2025-01-02 + validation: 2025-07-16 posted: 2021-05-26 categories: - bare-metal diff --git a/pages/elastic-metal/troubleshooting/replace-failed-drive-software-raid.mdx b/pages/elastic-metal/troubleshooting/replace-failed-drive-software-raid.mdx index 9cca632ba8..522726d45c 100644 --- a/pages/elastic-metal/troubleshooting/replace-failed-drive-software-raid.mdx +++ b/pages/elastic-metal/troubleshooting/replace-failed-drive-software-raid.mdx @@ -6,7 +6,7 @@ categories: - bare-metal - elastic-metal dates: - validation: 2025-01-02 + validation: 2025-07-15 posted: 2022-08-26 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/elastic-metal/troubleshooting/reset-admin-password-windows-server.mdx b/pages/elastic-metal/troubleshooting/reset-admin-password-windows-server.mdx index bea6cc3941..0d8db67c58 100644 --- a/pages/elastic-metal/troubleshooting/reset-admin-password-windows-server.mdx +++ b/pages/elastic-metal/troubleshooting/reset-admin-password-windows-server.mdx @@ -6,7 +6,7 @@ categories: - bare-metal - elastic-metal dates: - validation: 2025-01-02 + validation: 2025-07-15 posted: 2023-12-14 --- import Requirements from '@macros/iam/requirements.mdx' @@ -31,15 +31,15 @@ If you have lost this password, you can reset it via rescue mode. This guide exp 1. Reboot your Elastic Metal server into [rescue mode](/elastic-metal/how-to/use-rescue-mode/). 2. Log into rescue mode. 3. Install the packages `ntfs-3g` and `chntpw` using the APT package manager. - ``` + ```sh sudo apt install ntfs-3g chntpw ``` 4. Mount the Windows system partition. - ``` + ```sh sudo ntfsfix /dev/sda2 ``` 5. List the user accounts configured in Windows: - ``` + ```sh sudo chntpw -l /mnt/Windows/System32/config/SAM ``` An output similar to the following displays: @@ -60,7 +60,7 @@ If you have lost this password, you can reset it via rescue mode. This guide exp The administrator account of your server can either be `Administrator` or `Administrateur` depending on the installation. 6. Edit the `Administrator` account by running the following command: - ``` + ```sh sudo chntpw -u Administrator /mnt/Windows/System32/config/SAM ``` A menu displays as follows: diff --git a/pages/gpu/how-to/use-preinstalled-env.mdx b/pages/gpu/how-to/use-preinstalled-env.mdx index f827b1a91e..9cfc71fa8c 100644 --- a/pages/gpu/how-to/use-preinstalled-env.mdx +++ b/pages/gpu/how-to/use-preinstalled-env.mdx @@ -85,7 +85,7 @@ Some applications, such as [Jupyter Lab](https://jupyter.org/), [Tensorboard](ht ``` - You can find the IP address of your Instance in the Scaleway console. In the side menu, click **Instances** to see a list of your Instances. The IP address of each of them is shown in the list that displays. + You can find the IP address of your Instance in the Scaleway console. In the side menu, click **CPU & GPU Instances** to see a list of your Instances. The IP address of each of them is shown in the list that displays. Jupyter Lab now displays in your browser. You can use the Notebook, Console, or other features as required: diff --git a/pages/gpu/quickstart.mdx b/pages/gpu/quickstart.mdx index b611c0ff83..dc08dac435 100644 --- a/pages/gpu/quickstart.mdx +++ b/pages/gpu/quickstart.mdx @@ -21,7 +21,7 @@ In addition to this, GPU Instances have all the features of our regular Instance ## How to create a GPU Instance -1. Navigate to **Instances** under the **Compute** section in the side menu of the [Scaleway console](https://console.scaleway.com/). This action will direct you to the [Instance dashboard](https://console.scaleway.com/instance/servers). +1. Navigate to **CPU & GPU Instances** under the **Compute** section in the side menu of the [Scaleway console](https://console.scaleway.com/). This action will direct you to the [Instance dashboard](https://console.scaleway.com/instance/servers). 2. Click **+ Create Instance** to proceed to the [Instance creation page](https://console.scaleway.com/instance/servers). 3. Follow these steps to configure your GPU Instance: - **Availability Zone**: Choose the geographical region, represented by the Availability Zone, where your Instance will be deployed. @@ -96,7 +96,7 @@ Some applications, such as [Jupyter Lab](https://jupyter.org/), [Tensorboard](ht ``` - You can find the IP address of your Instance in the Scaleway console. In the side menu, click **Instances** to see a list of your Instances. The IP address of each of them is shown in the list that displays. + You can find the IP address of your Instance in the Scaleway console. In the side menu, click **CPU & GPU Instances** to see a list of your Instances. The IP address of each of them is shown in the list that displays. Jupyter Lab now displays in your browser. You can use the Notebook, Console, or other features as required: diff --git a/pages/gpu/troubleshooting/fix-driver-issues.mdx b/pages/gpu/troubleshooting/fix-driver-issues.mdx index eaebd6835e..0ede7a6d87 100644 --- a/pages/gpu/troubleshooting/fix-driver-issues.mdx +++ b/pages/gpu/troubleshooting/fix-driver-issues.mdx @@ -3,7 +3,7 @@ title: Fixing GPU issues after installing nvidia-driver packages description: Resolve GPU issues on Scaleway GPU Instances after installing Nvidia drivers with our troubleshooting guide. tags: gpu issue error driver nvidia-driver sleep gpu-instance dates: - validation: 2025-01-02 + validation: 2025-07-15 posted: 2022-12-01 categories: - compute diff --git a/pages/guidelines.mdx b/pages/guidelines.mdx index 31343492ba..66b08b6935 100644 --- a/pages/guidelines.mdx +++ b/pages/guidelines.mdx @@ -134,13 +134,13 @@ If you are including an image, code block, or any "new line" element as part of ✅ **GOOD** -1. Click **Instances** in the **Compute** section of the Scaleway console. The **Instances dashboard** displays. +1. Click **CPU & GPU Instances** in the **Compute** section of the Scaleway console. The **Instances dashboard** displays. 2. Click the Instance whose flexible IP address you want to detach. The **Overview page** for that Instance displays. 3. Click **Detach** next to the flexible IP address you want to detach. ❌ **BAD** -1. Start by clicking **Instances** in the **Compute** section of the Scaleway console. +1. Start by clicking **CPU & GPU Instances** in the **Compute** section of the Scaleway console. 2. You will see the **Instances dashboard**. 3. Next, you need to find the Instance whose flexible IP address you want to detach, and click on it. You'll see the **Overview page** for the Instance. To finish the process, click **Detach** next to the flexible IP address you want to detach. diff --git a/pages/instances/api-cli/attaching-a-volume.mdx b/pages/instances/api-cli/attaching-a-volume.mdx index 62e5a03e4f..ae35af33df 100644 --- a/pages/instances/api-cli/attaching-a-volume.mdx +++ b/pages/instances/api-cli/attaching-a-volume.mdx @@ -6,7 +6,7 @@ categories: - block-storage - storage dates: - validation: 2025-01-02 + validation: 2025-07-16 posted: 2020-01-10 --- import Requirements from '@macros/iam/requirements.mdx' @@ -21,14 +21,14 @@ import Requirements from '@macros/iam/requirements.mdx' 1. Query the current volumes of the Instance. - ``` + ```sh curl -X GET \ -H "X-Auth-Token: $SCW_SECRET_KEY" \ "https://api.scaleway.com/instance/v1/zones/{zone}/servers/{server_id}" ``` The output displays as follows: - ``` + ```json { "server": { "id": "de0f4d6a-3289-4716-97a8-d24b2a58dcd9", @@ -50,7 +50,7 @@ import Requirements from '@macros/iam/requirements.mdx' As displayed, our current volumes are only constituted of the root volume. 2. Hot-plug the volume created earlier: - ```bash + ```json curl -q \ -H "X-Auth-Token: $SCW_SECRET_KEY" \ -H 'Content-Type: application/json' \ @@ -70,7 +70,7 @@ import Requirements from '@macros/iam/requirements.mdx' https://api.scaleway.com/instance/v1/zones/{zone}/servers/{server_id} ``` The output looks like the following example: - ``` + ```json { "server": { "id": "1de0f4d6a-3289-4716-97a8-d24b2a58dcd9", @@ -109,7 +109,7 @@ import Requirements from '@macros/iam/requirements.mdx' automate things, a symlink is also present in `/dev/disk/by-id/` with the `id` of the volume in it: - ``` + ```sh ls /dev/disk/by-id/ scsi-0SCW_b_ssd_volume-b3a42fb1-e85c-46e9-b0a6-9adb62278295 ``` @@ -117,7 +117,7 @@ import Requirements from '@macros/iam/requirements.mdx' If you query information about the block volume from the API, the `server_id` on which it is plugged in is displayed: - ``` + ```json curl -q \ -H "X-Auth-Token: $SCW_SECRET_KEY" \ -H 'Content-Type: application/json' \ diff --git a/pages/instances/api-cli/increasing-volume-size.mdx b/pages/instances/api-cli/increasing-volume-size.mdx index 875ed8e762..7653ba1239 100644 --- a/pages/instances/api-cli/increasing-volume-size.mdx +++ b/pages/instances/api-cli/increasing-volume-size.mdx @@ -32,7 +32,7 @@ The Instances API allows you to interact with Block Storage volumes programmatic ``` - Replace `REGION` with the geographical region of the Instance. This value can either be `fr-par-1`, `fr-par-2`, or `fr-par-3` for Instances located in Paris, `nl-ams-1`, `nl-ams-2` or `nl-ams-3` for Instances located in Amsterdam, or `pl-waw-1`, `pl-waw-2`, or `pl-waw-3` for Instances located in Warsaw. Replace `VOLUME_ID` with the unique identifier of the volume, which can be found on the Scaleway console under **CPU Instances** > **Volumes** > **More info** (for the selected volume). + Replace `REGION` with the geographical region of the Instance. This value can either be `fr-par-1`, `fr-par-2`, or `fr-par-3` for Instances located in Paris, `nl-ams-1`, `nl-ams-2` or `nl-ams-3` for Instances located in Amsterdam, or `pl-waw-1`, `pl-waw-2`, or `pl-waw-3` for Instances located in Warsaw. Replace `VOLUME_ID` with the unique identifier of the volume, which can be found on the Scaleway console under **CPU & GPU Instances** > **Volumes** > **More info** (for the selected volume). The following response should appear as an output: diff --git a/pages/instances/api-cli/using-cloud-init.mdx b/pages/instances/api-cli/using-cloud-init.mdx index 6760b7db62..f90741f9c7 100644 --- a/pages/instances/api-cli/using-cloud-init.mdx +++ b/pages/instances/api-cli/using-cloud-init.mdx @@ -3,7 +3,7 @@ title: Using cloud-init with Scaleway API and CLI description: Learn how to effectively use cloud-init with Scaleway API and CLI for seamless cloud infrastructure deployment. tags: cloud-init cloud init scaleway-api cli dates: - validation: 2025-01-02 + validation: 2025-07-15 posted: 2021-05-26 categories: - compute @@ -13,7 +13,7 @@ import Requirements from '@macros/iam/requirements.mdx' Cloud-init is a package that contains utilities for early initialization of cloud Instances. It enables automatic configuration of cloud Instances as it boots into the cloud, turning it from a generic Ubuntu image into a configured server in a few seconds, quickly and easily. -The cloud-init program is available on recent distributions (Ubuntu, Fedora, Debian) and can consume and execute data from the `user-data` field of the Scaleway service. This process behaves differently depending on the format of the information it finds. One of the most popular formats for scripts within `user-data` is the cloud-config file format. +The `cloud-init` program is available on recent distributions (Ubuntu, Fedora, Debian) and can consume and execute data from the `user-data` field of the Scaleway service. This process behaves differently depending on the format of the information it finds. One of the most popular formats for scripts within `user-data` is the cloud-config file format. Cloud-config files are special scripts designed to be run by the cloud-init process. These are generally used for initial configuration on the very first boot of a server. @@ -24,7 +24,7 @@ Cloud-config files are special scripts designed to be run by the cloud-init proc - A valid [API key](/iam/how-to/create-api-keys/) - Downloaded the [latest version of the Scaleway CLI](https://github.com/scaleway/scaleway-cli) -## Provisioning your Instance with Cloud-Init +## Provisioning your Instance with cloud-init You can give provisioning instructions to cloud-init using the `cloud-init` key of the `user_data` facility. @@ -40,21 +40,21 @@ For `user_data` to be effective, it has to be added prior to the creation of the `@/path/to/cloud-config-file` is the path of your [Cloud-Init](/instances/how-to/use-boot-modes/#how-to-use-cloud-init) configuration file. Edit it as you wish. 2. Start your Instance - ``` + ```sh scw start {server Id} ``` Since [version 2.3.1](https://github.com/scaleway/scaleway-cli/releases/tag/v2.3.1) of the Scaleway CLI a shorter command is available: - ``` + ```sh scw instance server create image=ubuntu_focal name=myinstance cloud-init=@/path/to/cloud-config-file ``` -## Cloud-Init CLI (Command Line Interface) +## Cloud-init CLI (Command Line Interface) The command line documentation is accessible on any cloud-init installed system. -```` +```sh % cloud-init --help usage: cloud-init [-h] [--version] [--file FILES] @@ -84,6 +84,6 @@ Subcommands: clean Remove logs and artifacts so cloud-init can re-run. status Report cloud-init status or wait on completion. -```` +``` For detailed information on cloud-init, refer to the official cloud-init [documentation](http://cloudinit.readthedocs.io/en/latest/index.html). \ No newline at end of file diff --git a/pages/instances/api-cli/using-routed-ips.mdx b/pages/instances/api-cli/using-routed-ips.mdx index b17d77f85c..cba8a3e2a0 100644 --- a/pages/instances/api-cli/using-routed-ips.mdx +++ b/pages/instances/api-cli/using-routed-ips.mdx @@ -3,7 +3,7 @@ title: Routing public IPs to Instances using the Scaleway CLI/API description: This page explains how to route public IPs to Instances using the Scaleway CLI/API tags: routed ip cloud scaleway-api transition dates: - validation: 2025-01-02 + validation: 2025-07-15 posted: 2023-05-17 categories: - compute diff --git a/pages/instances/how-to/configure-reverse-dns.mdx b/pages/instances/how-to/configure-reverse-dns.mdx index 4f47525dc4..cb28b9ec1b 100644 --- a/pages/instances/how-to/configure-reverse-dns.mdx +++ b/pages/instances/how-to/configure-reverse-dns.mdx @@ -26,7 +26,7 @@ Reverse DNS is the opposite of classic "forward" DNS and maps an IP address to a ## How to set up a reverse DNS record -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 **Flexible IPs** tab. 3. Click the icon next to the IP address you wish to configure reverse DNS for and select **Edit reverse** from the drop-down menu. 4. Enter the reverse DNS you want to associate with the IP address. Generally this corresponds to your hostname. diff --git a/pages/instances/how-to/connect-to-instance.mdx b/pages/instances/how-to/connect-to-instance.mdx index 7869ad5b2b..fdfca807ed 100644 --- a/pages/instances/how-to/connect-to-instance.mdx +++ b/pages/instances/how-to/connect-to-instance.mdx @@ -38,7 +38,7 @@ This page shows how to connect to your Scaleway Instance via SSH. Thanks to the ``` To find the IP address of your Instance, log into the Scaleway console and - click **CPU Instances** in the Compute section of the side menu. A list of your + click **CPU & GPU Instances** in the Compute section of the side menu. A list of your Instances and their associated IP addresses will display. 3. If / when prompted, allow connection to the host by typing `yes`, then press **Enter**. @@ -64,7 +64,7 @@ This page shows how to connect to your Scaleway Instance via SSH. Thanks to the 3. Enter your Instance's IP address in the **Hostname** field. To find the IP address of your Instance, log into the Scaleway console and - click **CPU Instances** in the Compute section of the side menu. A list of your + click **CPU & GPU Instances** in the Compute section of the side menu. A list of your Instances and their associated IP addresses will display. 4. In the side menu, expand the **Connection**, **SSH** and **Auth** submenus, then click **Credentials**: @@ -90,7 +90,7 @@ This page shows how to connect to your Scaleway Instance via SSH. Thanks to the * The steps below are valid only for Instances running Microsoft Windows as operating system. * You must have the [Scaleway CLI](https://github.com/scaleway/scaleway-cli) installed and configured on your local machine to be able to retrieve your Windows administrator password. - 1. Click **CPU Instances** in the **Compute** section of the left side menu. The Instances dashboard displays. + 1. Click **CPU & GPU Instances** in the **Compute** section of the left side menu. The Instances dashboard displays. 2. Select the name of the Instance you wish to connect to. 3. Click **Get password** to retrieve the password for your Instance. A popup will display a command for retrieving your initial password using the Scaleway CLI: ```bash diff --git a/pages/instances/how-to/create-a-backup.mdx b/pages/instances/how-to/create-a-backup.mdx index 3141782f7e..d21568806b 100644 --- a/pages/instances/how-to/create-a-backup.mdx +++ b/pages/instances/how-to/create-a-backup.mdx @@ -28,7 +28,7 @@ This feature is available on Instance types. Creating images of your Instance is ## How to create an image -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 want to back up. 3. Go to the **Images** section of the Instace's overview page. 4. Click **Create image from Instance**. A pop-up displays asking you to confirm the action. @@ -52,7 +52,7 @@ A new Instance is created from your image. ### Restoring the image -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 created an image of. 3. Click the **Storage** tab and scroll down to the **Images** section of the page. 4. Click next to the Instance's image. @@ -63,7 +63,7 @@ A new Instance is created from your image. ## How to manage your images -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 **Storage** tab. A list of your storage resources displays. 3. Scroll to the **Images** section of the page. 3. Click next to the relevant image. diff --git a/pages/instances/how-to/create-an-instance.mdx b/pages/instances/how-to/create-an-instance.mdx index f4769c89b9..7c61fbf27a 100644 --- a/pages/instances/how-to/create-an-instance.mdx +++ b/pages/instances/how-to/create-an-instance.mdx @@ -26,7 +26,7 @@ Select a tab below for instructions on how to create an Instance via either our - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - An [Instance](/instances/how-to/create-an-instance/) - 1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instance dashboard](https://console.scaleway.com/instance/servers) displays. + 1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instance dashboard](https://console.scaleway.com/instance/servers) displays. 2. Click **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers) displays. 3. Complete the following steps: - **Choose an Availability Zone**, which represents the geographical region where your Instance will be deployed. @@ -65,7 +65,7 @@ Select a tab below for instructions on how to create an Instance via either our - An [RSA key pair](/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-a-rsa-ssh-key-pair) - An [Instance](/instances/how-to/create-an-instance/) - 1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instance dashboard](https://console.scaleway.com/instance/servers) displays. + 1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instance dashboard](https://console.scaleway.com/instance/servers) displays. 2. Click **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers) displays. 3. Complete the following steps: - Choose an **Availability Zone**, which represents the geographical region where your Instance will be deployed. diff --git a/pages/instances/how-to/delete-instance.mdx b/pages/instances/how-to/delete-instance.mdx index 2d17772631..719f213cbf 100644 --- a/pages/instances/how-to/delete-instance.mdx +++ b/pages/instances/how-to/delete-instance.mdx @@ -25,7 +25,7 @@ This page shows you how to delete an Instance. ## How to delete an Instance -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 icon next to the Instance you want to delete, and select **Delete** from the drop-down menu. A pop-up asks you to confirm the action. 3. Type **DELETE** to confirm your choice. diff --git a/pages/instances/how-to/manage-storage.mdx b/pages/instances/how-to/manage-storage.mdx index 2b47a8125d..282c1bb11b 100644 --- a/pages/instances/how-to/manage-storage.mdx +++ b/pages/instances/how-to/manage-storage.mdx @@ -31,7 +31,7 @@ Volumes are the primary storage solution for your Instances. Scaleway Instances ### Viewing and managing volumes -1. Click **CPU Instances** in the left menu. +1. Click **CPU & GPU Instances** in the left menu. 2. Select the Instance you want to manage. 3. Go to the **Storage** tab. 4. Scroll to the **Volumes** section to view attached volumes. @@ -43,7 +43,7 @@ Volumes are the primary storage solution for your Instances. Scaleway Instances - [Delete volume](/block-storage/how-to/delete-a-volume/) ### Adding a volume -1. Navigate to **CPU Instances** in the left menu. +1. Navigate to **CPU & GPU Instances** in the left menu. 2. Select the Instance you want to configure. 3. Open the **Storage** tab. 4. Click **+ Create volume** in the **Volumes** section. @@ -57,7 +57,7 @@ Volumes are the primary storage solution for your Instances. Scaleway Instances Snapshots preserve the state of a volume at a specific time, allowing for data recovery. ### Viewing and managing snapshots -1. Click **CPU Instances** in the left menu. +1. Click **CPU & GPU Instances** in the left menu. 2. Select the Instance you want to configure. 3. Go to the **Storage** tab. 4. Scroll to the **Snapshots** section. @@ -69,7 +69,7 @@ Snapshots preserve the state of a volume at a specific time, allowing for data r - [Delete snapshot](/block-storage/how-to/delete-a-snapshot/) ### Creating a snapshot -1. Click **CPU Instances** in the left menu. +1. Click **CPU & GPU Instances** in the left menu. 2. Select the Instance you want to configure. 3. Open the **Storage** tab. 4. Click **+ Create snapshot** in the **Snapshots** section. @@ -81,7 +81,7 @@ Snapshots preserve the state of a volume at a specific time, allowing for data r Images are full backups of Instances, useful for restoring data or deploying multiple Instances. ### Viewing and managing images -1. Click **CPU Instances** in the left menu. +1. Click **CPU & GPU Instances** in the left menu. 2. Select the Instance you want to configure. 3. Open the **Storage** tab. 4. Scroll to the **Images** section. @@ -91,7 +91,7 @@ Images are full backups of Instances, useful for restoring data or deploying mul - Delete the image ### Creating an image -1. Click **CPU Instances** in the left menu. +1. Click **CPU & GPU Instances** in the left menu. 2. Select the Instance you want to configure. 3. Open the **Storage** tab. 4. Click **+ Create image** in the **Images** section. diff --git a/pages/instances/how-to/migrate-instances.mdx b/pages/instances/how-to/migrate-instances.mdx index 2f217c00b5..613ebc11ad 100644 --- a/pages/instances/how-to/migrate-instances.mdx +++ b/pages/instances/how-to/migrate-instances.mdx @@ -28,7 +28,7 @@ Follow the instructions to [create an image](/instances/how-to/create-a-backup/# ## How to create a new Instance from an image -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 created an image of. 3. Click the **Images** tab. 4. Click next to the Instance's image. @@ -42,7 +42,7 @@ Follow the instructions to [create an image](/instances/how-to/create-a-backup/# Next, we will move the original DEV1-S Instance's [flexible IP address](/instances/concepts/#flexible-ip) to the new GP1-XS Instance. -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 **Flexible IPs** tab. 3. Click next to the DEV1-S's flexible IP. In the pop-up menu that then displays, click **Switch Instance**. 4. Select the GP1-XS Instance from the drop-down list, and click **Attach flexible IP to Instance**. diff --git a/pages/instances/how-to/migrate-local-storage-to-sbs.mdx b/pages/instances/how-to/migrate-local-storage-to-sbs.mdx index 8cfdc90a96..f8e04e51e7 100644 --- a/pages/instances/how-to/migrate-local-storage-to-sbs.mdx +++ b/pages/instances/how-to/migrate-local-storage-to-sbs.mdx @@ -24,7 +24,7 @@ By following these steps, you will be able to export your local storage and rest To begin the migration process, you need to create a snapshot of your Local Storage volume. This will allow you to export the snapshot and import it into a new SBS volume. -1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 want to snapshot. 3. Click the **Storage** tab to display the storage options of your Instance. 4. Click > **Snapshot** next to the volume you want to snapsot. @@ -75,7 +75,7 @@ Once the new SBS volume is created, you need to attach it to your instance. This After attaching the new SBS volume, you need to restart your instance. This will ensure that your Instance is using the new SBS volume as its primary storage. -1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 want to reboot. 3. Click **Actions** > **Reboot** in the top right corner of the Instance overview page. 4. A pop-up displays to confirm the Instance reboot. Click **Reboot Instance**. diff --git a/pages/instances/how-to/migrate-routed-ips.mdx b/pages/instances/how-to/migrate-routed-ips.mdx index 9792af5e5a..df30b12895 100644 --- a/pages/instances/how-to/migrate-routed-ips.mdx +++ b/pages/instances/how-to/migrate-routed-ips.mdx @@ -67,7 +67,7 @@ If `scaleway-ecosystem` is not installed, no additional steps are needed for thi ## Moving the Instance to routed IPs -1. Select **CPU Instances** from the **Compute** category in the sidebar menu. This will show a list of your Instances. Those eligible to transition to routed IPs are identified with an exclamation mark icon. +1. Select **CPU & GPU Instances** from the **Compute** category in the sidebar menu. This will show a list of your Instances. Those eligible to transition to routed IPs are identified with an exclamation mark icon. 2. Click **Move IP** next to the Instance you wish to move to routed flexible IPs. A pop-up displays. diff --git a/pages/instances/how-to/power-off-instance.mdx b/pages/instances/how-to/power-off-instance.mdx index 035a2bb10c..bcf8be853f 100644 --- a/pages/instances/how-to/power-off-instance.mdx +++ b/pages/instances/how-to/power-off-instance.mdx @@ -26,7 +26,7 @@ Powering off your Instance shuts it down by transferring all the data on the Ins ## How to power off an Instance -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 want to power off. The **Overview** page for that Instance displays. 3. Use the toggle in the top right corner of the screen to **power off** your Instance. @@ -39,7 +39,7 @@ Powering off your Instance shuts it down by transferring all the data on the Ins ## How to power on an Instance -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 want to power on again. The **Overview** page for that Instance displays. 3. Use the toggle in the top right corner of the screen to switch your Instance to **ON**. A pop-up displays asking you to confirm the action. diff --git a/pages/instances/how-to/resize-instances.mdx b/pages/instances/how-to/resize-instances.mdx index 779b8e43b7..f972eca432 100644 --- a/pages/instances/how-to/resize-instances.mdx +++ b/pages/instances/how-to/resize-instances.mdx @@ -25,7 +25,7 @@ Alternatively, you can also resize your Instance using the command line by follo - [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/) using Block Storage volumes -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 want to resize. The **Overview** page for that Instance displays. 3. Click **Change offer** in the **Instance information** section of the overview page. The change offer page displays. diff --git a/pages/instances/how-to/send-emails-from-your-instance.mdx b/pages/instances/how-to/send-emails-from-your-instance.mdx index 04f5e0bd77..a04e590f81 100644 --- a/pages/instances/how-to/send-emails-from-your-instance.mdx +++ b/pages/instances/how-to/send-emails-from-your-instance.mdx @@ -25,7 +25,7 @@ By default, remote SMTP ports (25, 465, and 587) are blocked and cannot be acces - Completed the [identity verification process (KYC)](/account/how-to/verify-identity/) -1. Click **CPU Instances** on the side menu of the [Scaleway console](https://console.scaleway.com). +1. Click **CPU & GPU Instances** on the side menu of the [Scaleway console](https://console.scaleway.com). 2. Click the **Security groups** tab. 3. Select the security group for which you want to enable SMTP ports. diff --git a/pages/instances/how-to/use-boot-modes.mdx b/pages/instances/how-to/use-boot-modes.mdx index d3388de73e..b7ae2f69cf 100644 --- a/pages/instances/how-to/use-boot-modes.mdx +++ b/pages/instances/how-to/use-boot-modes.mdx @@ -30,7 +30,7 @@ You can boot your Instances using local boot or a rescue image. This page explai Local boot allows you to start your Instance with a local configuration and a specific kernel version. This is the default option. You only need to follow these instructions to revert to local boot after using a different boot mode. -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 start with a local boot. 3. Use the toggle in the top right corner of the screen to **power off** your Instance. 4. Click the **Advanced settings** tab. @@ -44,7 +44,7 @@ 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 Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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. 3. Use the toggle in the top right corner of the screen to **power off** your Instance. 4. Click the **Advanced settings** tab. @@ -63,7 +63,7 @@ These are generally used for initial configuration on the very first boot of a s Follow the instructions below to reboot an existing Instance using cloud-init. -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 use with cloud-init. 3. Click the **Advanced settings** tab. 4. In the **Cloud-init** section, use the toggle icon to activate **Use cloud-init**. @@ -95,7 +95,7 @@ The [boot-on-block](/instances/concepts/#boot-on-block) feature allows Instances Once the Instance is created, you can select a different volume to boot from. -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 change the boot volume for. 3. Click the **Advanced settings** tab. 4. Go to the **Boot volume** section. diff --git a/pages/instances/how-to/use-flexips.mdx b/pages/instances/how-to/use-flexips.mdx index 8a754ff039..21bd1d8e2e 100644 --- a/pages/instances/how-to/use-flexips.mdx +++ b/pages/instances/how-to/use-flexips.mdx @@ -39,7 +39,7 @@ You can assign up to five (5) flexible routed IP addresses to each Instance. Detaching your Instance's flexible (public) IP address cuts any ongoing public connection to the Instance. This feature gives you a lot of control if, for example, you want to put your Instances into a Private Network so that they can communicate between themselves without being exposed to the internet. This is particularly useful for Instances hosting databases, backups, or sensitive content. It also allows you to optimize your costs and fight the global IPv4 shortage. -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 whose IP address you want to detach. The Overview page for that Instance displays. 3. Click **Detach** next to **Public IP**. 4. Click **Detach IP** on the pop-up that asks you to confirm the action. @@ -49,7 +49,7 @@ Detaching your Instance's flexible (public) IP address cuts any ongoing public c ## How to create a new flexible IP address -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. 2. Navigate to the **Flexible IPs** tab. 3. Click **Create flexible IP**. The flexible IP creation wizard displays. 4. Complete the following information in the wizard: @@ -62,7 +62,7 @@ Detaching your Instance's flexible (public) IP address cuts any ongoing public c ## How to attach an existing flexible IP address to an Instance -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. 2. Navigate to the **Flexible IPs** tab. 3. Click next to the flexible IP that you want to attach to an Instance. In the drop-down menu that opens, click **Switch Instance**. @@ -74,7 +74,7 @@ Detaching your Instance's flexible (public) IP address cuts any ongoing public c When you no longer want one of your existing flexible IP addresses, you can delete it from your account, which releases it to be used by other users. -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. 2. Navigate to the **Flexible IPs** tab. 3. Click next to the flexible IP that you want to delete. In the drop-down menu which opens, click **Delete**. 4. Confirm that you want to delete the flexible IP in the pop-up window which opens, by clicking **Delete flexible IP**. diff --git a/pages/instances/how-to/use-placement-groups.mdx b/pages/instances/how-to/use-placement-groups.mdx index 82f484943e..550504ec2d 100644 --- a/pages/instances/how-to/use-placement-groups.mdx +++ b/pages/instances/how-to/use-placement-groups.mdx @@ -21,7 +21,7 @@ import Requirements from '@macros/iam/requirements.mdx' ## How to create a placement group -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 **Placement groups** tab. 3. Click **Create placement group**. The creation wizard displays. 4. Complete the following steps in the wizard: @@ -33,7 +33,7 @@ import Requirements from '@macros/iam/requirements.mdx' - 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 Instances** to the placement group. + - Add **CPU & GPU Instances** to the placement group. You can only add powered off Instances to a placement group. @@ -46,9 +46,9 @@ import Requirements from '@macros/iam/requirements.mdx' You must power off your Instance to perform this action. -1. Go to the **Placement groups** tab, accessible from the **CPU Instances** page under the **Compute** section of the side menu. A list of your placement groups displays. +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 Instances** tab. +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** You can add up to 20 Instances to each of your placement groups. @@ -57,14 +57,14 @@ import Requirements from '@macros/iam/requirements.mdx' You are returned to the list of Instances attached to your placement group, where the Instance you added now displays. If you wish to power the Instance you added back on, you can do so by clicking , and selecting **Power on** from the drop-down menu. - You can also add an Instance to a placement group from the Instances page (accessible by clicking **CPU 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 **Manage placement group** and select the placement group you want to add the Instance to, confirming your choice when prompted. + You can also add an Instance to 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 **Manage placement group** and select the placement group you want to add the Instance to, confirming your choice when prompted. ## How to remove Instances from a placement group -1. Go to the **Placement groups** tab, accessible from the **CPU Instances** page under the **Compute** section of the side menu. A list of your placement groups displays. +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 wish to remove Instances from. You are taken to the **Overview** for that placement group. -3. Click the **CPU Instances** tab. +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. @@ -72,7 +72,7 @@ You are returned to the list of Instances attached to your placement group, wher 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 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 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. ## How to change an Instance's placement group @@ -81,7 +81,7 @@ You are returned to the list of Instances attached to your placement group, wher You must power off your Instance to perform this action. -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 name of the Instance you want to edit. The Instance Overview tab displays. 3. Scroll down to **Placement groups**. 4. Click next to the placement group name, and select **Switch** from the drop-down menu. A pop-up displays. @@ -90,7 +90,7 @@ You are returned to the list of Instances attached to your placement group, wher Your Instance's placement group is changed, and you are returned to the Instance Overview page. If you wish to power the Instance back on, you can do so using the button at the top right of the page. - You can also switch Instances of a placement group from the Instances page (accessible by clicking **CPU 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 switch from, and select **Switch** from the drop-down menu. You are prompted to select a different placement group, and to confirm your choice. + You can also switch Instances of 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 switch from, and select **Switch** from the drop-down menu. You are prompted to select a different placement group, and to confirm your choice. ## How to modify a placement group's type @@ -99,7 +99,7 @@ You are returned to the list of Instances attached to your placement group, wher You must power off all Instances within a placement group to perform this action. -1. Go to the **Placement groups** tab, accessible from the **CPU Instances** page under the **Compute** section of the side menu. A list of your placement groups displays. +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 in question. You are taken to the placement group's Overview tab. 3. Scroll down to the **Placement group type** section, and choose the required type for your group. @@ -111,7 +111,7 @@ The new group type will be applied immediately, and Instances of the group will You must power off all Instances within a placement group to perform this action. -1. Go to the **Placement groups** tab, accessible from the **CPU Instances** page under the **Compute** section of the side menu. A list of your placement groups displays. +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 in question. You are taken to the placement group's Overview tab. 3. Scroll down to the **Placement group policy** section, and choose the required policy for your group. @@ -121,7 +121,7 @@ The new group policy will be applied immediately, and Instances of the group wil Deleting a placement group will have no direct impact on the Instances attached to it. They will continue to run on their current hypervisors until you reboot them. -1. Go to the **Placement groups** tab, accessible from the **CPU Instances** page under the **Compute** section of the side menu. A list of your placement groups displays. +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 next to the placement group you want to delete, and select **Delete** from the drop-down menu that displays. A pop-up appears asking you to confirm this action. diff --git a/pages/instances/how-to/use-private-networks.mdx b/pages/instances/how-to/use-private-networks.mdx index 7f78ec1058..62d83ded63 100644 --- a/pages/instances/how-to/use-private-networks.mdx +++ b/pages/instances/how-to/use-private-networks.mdx @@ -27,7 +27,7 @@ The procedure below shows you how to create a new Private Network to attach to a 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/). -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 want to add a Private Network to. 3. Click the **Private Networks** tab. 4. Click the **Attach to a Private Network** button. A pop-up displays. @@ -42,7 +42,7 @@ You are taken back to the Private Networks tab, where your new Private Network i ## How to attach Instances to an existing Private Network -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 want to add a Private Network to. 3. Click the **Private Networks** tab. 4. Click the **Attach to a Private Network** button. A pop-up displays. @@ -57,7 +57,7 @@ You are taken back to the Private Networks tab, where your new Private Network i ## How to detach Instances from a Private Network -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 want to detach from a Private Network. 3. Click the **Private Networks** tab. 4. Click the icon next to the resource you want to detach. diff --git a/pages/instances/how-to/use-protected-instance.mdx b/pages/instances/how-to/use-protected-instance.mdx index 42da5db6f5..51df4a1dc7 100644 --- a/pages/instances/how-to/use-protected-instance.mdx +++ b/pages/instances/how-to/use-protected-instance.mdx @@ -3,7 +3,7 @@ title: How to use the Protected Instance feature description: Learn how to effectively use the Protected Instance feature in this comprehensive guide. tags: protected-instance protected instance dates: - validation: 2025-01-02 + validation: 2025-07-15 posted: 2021-05-26 categories: - compute @@ -21,7 +21,7 @@ The [Protected Instance](/instances/concepts/#protected-instance) feature is use ## How to activate the Protected Instance feature -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 want to protect. The **Overview** page for that Instance displays. 3. Click the **Advanced settings** tab. 4. Scroll down to the **Protected Instance** section, and use the toggle to activate the Protected Instance feature. diff --git a/pages/instances/how-to/use-security-groups.mdx b/pages/instances/how-to/use-security-groups.mdx index 7b0ff9008f..2a7562fab0 100644 --- a/pages/instances/how-to/use-security-groups.mdx +++ b/pages/instances/how-to/use-security-groups.mdx @@ -26,7 +26,7 @@ import Requirements from '@macros/iam/requirements.mdx' -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 **Security groups** tab. The Security groups dashboard displays. You will see that at least one **Default security group** already exists in your account. A default security group is auto-generated for each [Availability Zone](/instances/concepts/#availability-zone) you have created Instances in. All your Instances within that Availability Zone are automatically added to that default security group unless you specify a different configuration. @@ -36,12 +36,12 @@ import Requirements from '@macros/iam/requirements.mdx' - Choose a **Name** for your security group or keep the randomly generated suggestion. Optionally, add a description. - Choose an **Availability Zone**, which is the geographical location in which your security group will be created. Only Instances from the same Availability Zone can be added to this security group. - Define the inbound and outbound **rules** that will be applied to your security group, including whether you wish to enable SMTP ports. [Learn how to choose security group settings](/instances/how-to/use-security-groups/#how-to-choose-security-group-settings). - - Select the **CPU Instances** you wish to add to the security group. + - Select the **CPU & GPU Instances** you wish to add to the security group. 5. Click **Create security group** to finish. Your security group is created, and you are redirected to the **Security groups** tab, where it now appears. ## How to edit a security group -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 **Security groups** tab. The **Security groups** dashboard displays. 3. Click the security group you want to edit. Alternatively, click the icon to the right of the security group in question, and select **More info**. You are taken to the dashboard for that security group. 4. Navigate to the required tab depending on the edit you want to make: @@ -52,7 +52,7 @@ import Requirements from '@macros/iam/requirements.mdx' - Enable/disable stateful group rules, - Delete the security group. - On the **CPU Instances** tab, you can: + On the **CPU & GPU Instances** tab, you can: - Link Instances to this security group, using the drop-down menu, - Unlink Instances from the security group, using the button. diff --git a/pages/instances/how-to/use-serial-console.mdx b/pages/instances/how-to/use-serial-console.mdx index 6c325bac74..8ccd54114c 100644 --- a/pages/instances/how-to/use-serial-console.mdx +++ b/pages/instances/how-to/use-serial-console.mdx @@ -29,7 +29,7 @@ This page shows how to connect to your Scaleway Instance from the Scaleway conso You have to connect to your Instance using [SSH](/instances/how-to/connect-to-instance/) and define a user password before connecting to your Instance using the serial console. -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 want to connect to. 3. Click **Console** on the Instance **Overview** page. The serial console (TTY) displays in a pop-up. diff --git a/pages/instances/how-to/use-standby-mode.mdx b/pages/instances/how-to/use-standby-mode.mdx index a0610268a2..298952dd4f 100644 --- a/pages/instances/how-to/use-standby-mode.mdx +++ b/pages/instances/how-to/use-standby-mode.mdx @@ -23,7 +23,7 @@ import image from './assets/scaleway-standby-mode.webp' ## How to put an Instance into standby mode -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 want to put into standby mode. The Overview page for that Instance displays. 3. Scroll down to the **Standby mode** section diff --git a/pages/instances/quickstart.mdx b/pages/instances/quickstart.mdx index c2a4116713..b458cadc5f 100644 --- a/pages/instances/quickstart.mdx +++ b/pages/instances/quickstart.mdx @@ -21,7 +21,7 @@ Scaleway [Instances](/instances/concepts/#instance) are computing units that pro ## How to create an Instance - 1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instance dashboard](https://console.scaleway.com/instance/servers) displays. + 1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instance dashboard](https://console.scaleway.com/instance/servers) displays. 2. Click **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers) displays. 3. Complete the following steps: - **Choose an Availability Zone**, which represents the geographical region where your Instance will be deployed. @@ -93,6 +93,6 @@ To connect to your Instance from Windows, you will need to use a small applicati Deleting an Instance will destroy all the volumes and data stored on that Instance. Note that your Instance must be powered off or stopped to be deleted. -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 icon next to the Instance you want to delete and select **Delete** from the drop-down menu. A pop-up asks you to confirm the action. 3. Type **DELETE** and then click **Delete Instance**. \ No newline at end of file diff --git a/pages/instances/reference-content/add-instance-specific-ssh-keys-using-tags.mdx b/pages/instances/reference-content/add-instance-specific-ssh-keys-using-tags.mdx index 4ede2ce15f..f3ecbdbd60 100644 --- a/pages/instances/reference-content/add-instance-specific-ssh-keys-using-tags.mdx +++ b/pages/instances/reference-content/add-instance-specific-ssh-keys-using-tags.mdx @@ -53,7 +53,7 @@ This file lists all the SSH public keys allowed to access the Instance. Our goal ## How to add Instance-specific SSH keys using tags -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances overview](https://console.scaleway.com/Instance/servers) displays. +1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instances overview](https://console.scaleway.com/Instance/servers) displays. 2. Click the Instance you want to add a specific key to. 3. Navigate to the section where you can add tags to the Instance on the Instances overview page. 4. Add the public SSH key tag by writing in the **Tags** form. You can add multiple keys by creating separate `AUTHORIZED_KEY` tags for each SSH key. diff --git a/pages/instances/reference-content/choosing-instance-type.mdx b/pages/instances/reference-content/choosing-instance-type.mdx index d44206ff30..8a10d2b50b 100644 --- a/pages/instances/reference-content/choosing-instance-type.mdx +++ b/pages/instances/reference-content/choosing-instance-type.mdx @@ -9,7 +9,7 @@ dates: tags: instance type stardust range vcpu hyperthread core ram bandwidth dedicated shared memory hypervisor vm storage dev1 play2 gp1 pro2 ent1 gpu arm learning development production production-optimized cost-optimized memory-optimized storage-optimized --- -Scaleway **CPU Instances** are virtual machines in the cloud. You can create and manage Instances via our [console](https://console.scaleway.com/), [API](https://www.scaleway.com/en/developers/api/), [CLI](https://www.scaleway.com/en/cli/), or [other developer tools](https://www.scaleway.com/en/developers/). When you [create an Instance](/instances/how-to/create-an-instance/), you must select the **Instance type** you want to create. This page explains the different ranges of Instances available at Scaleway and helps you to choose the best one for your needs. +Scaleway **CPU & GPU Instances** are virtual machines in the cloud. You can create and manage Instances via our [console](https://console.scaleway.com/), [API](https://www.scaleway.com/en/developers/api/), [CLI](https://www.scaleway.com/en/cli/), or [other developer tools](https://www.scaleway.com/en/developers/). When you [create an Instance](/instances/how-to/create-an-instance/), you must select the **Instance type** you want to create. This page explains the different ranges of Instances available at Scaleway and helps you to choose the best one for your needs. ## Different Instances for different use cases diff --git a/pages/instances/reference-content/learning.mdx b/pages/instances/reference-content/learning.mdx index d91e3f20c9..d1712569cc 100644 --- a/pages/instances/reference-content/learning.mdx +++ b/pages/instances/reference-content/learning.mdx @@ -2,7 +2,7 @@ title: The right Instance for learning purposes description: Discover Scaleway's learning range of Instances, including options like the Stardust Instance, ideal for educational purposes. dates: - validation: 2025-01-06 + validation: 2025-07-15 posted: 2023-02-22 categories: - compute diff --git a/pages/instances/troubleshooting/bootscript-eol.mdx b/pages/instances/troubleshooting/bootscript-eol.mdx index 02b77b4402..c7e97bcf80 100644 --- a/pages/instances/troubleshooting/bootscript-eol.mdx +++ b/pages/instances/troubleshooting/bootscript-eol.mdx @@ -37,7 +37,7 @@ You can find information about the Instances quotas allocated to your account at If your Instance is using the bootscript option to boot in normal mode you are impacted. You can check which boot mode is used by your Instance directly in the Scaleway console. -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 name of the Instance you want to check. The Instance overview displays. 3. Click the **Advanced Settings** tab. 4. Check the **Boot Mode** of your Instance. If it uses **local boot** you are not concerned by the migration. If you are using a **bootscript** your intervention is required. @@ -71,7 +71,7 @@ If your Instance is using the bootscript option to boot in normal mode you are i **This section applies if your Instance supports UEFI boot.** To continue using your current Instance, [change the boot type](/instances/how-to/use-boot-modes/#how-to-use-local-boot) of the Instance to **Local boot**: - 1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. + 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 start with a local boot. 3. Use the toggle icon in the top right corner of the screen to **power off** your Instance. 4. Click the **Advanced settings** tab. diff --git a/pages/instances/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx b/pages/instances/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx index 3dbd55ad41..0176c2ee3c 100644 --- a/pages/instances/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx +++ b/pages/instances/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx @@ -3,7 +3,7 @@ title: I cannot connect to my Instance using SSH after attaching it to a Private description: This page explains how to troubleshoot connection problems after attaching a Scaleway Instance to a Private Network tags: troubleshoot error private-network private network vpc dhcp dates: - validation: 2025-01-02 + validation: 2025-07-15 posted: 2021-05-26 categories: - compute diff --git a/pages/instances/troubleshooting/change-rescue-mode.mdx b/pages/instances/troubleshooting/change-rescue-mode.mdx index 6e45f0bb6f..8c731e7180 100644 --- a/pages/instances/troubleshooting/change-rescue-mode.mdx +++ b/pages/instances/troubleshooting/change-rescue-mode.mdx @@ -23,7 +23,7 @@ This is particularly useful when your Instance is not booting properly due to co ## Updating rescue mode from the Scaleway console -1. Click **CPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 name of the Instance that is using the previous rescue mode. The Instance overview displays. 3. Stop the Instance if it is currently running by using the top right toggle of the Instances overview page. 4. Click the **Advanced settings** tab. diff --git a/pages/instances/troubleshooting/fix-cloud-init-debian12.mdx b/pages/instances/troubleshooting/fix-cloud-init-debian12.mdx index 569b8c10cb..63c3fbdb08 100644 --- a/pages/instances/troubleshooting/fix-cloud-init-debian12.mdx +++ b/pages/instances/troubleshooting/fix-cloud-init-debian12.mdx @@ -3,7 +3,7 @@ title: Fix the wrong user configuration of cloud-init on Debian 12 (Bookworm) description: This page helps you fix the wrong user configuration of cloud-init on Debian 12 (Bookworm) tags: debian12 debian bookworm cloud-init dates: - validation: 2025-01-02 + validation: 2025-07-15 posted: 2023-05-04 categories: - compute @@ -14,7 +14,7 @@ Debian 12 (Bookworm) Instances created before June 2nd, 2023 were delivered with The issue has been fixed for Instances created after June 2nd, 2023. The Debian 12 image now uses the official Debian Unstable `cloud-init` package.
Run the following commands to fix the issue on an Instance affected by this bug: -``` +```sh wget http://ftp.fr.debian.org/debian/pool/main/c/cloud-init/cloud-init_23.2-1_all.deb -O /tmp/cloud-init_23.2-1_all.deb dpkg -i /tmp/cloud-init_23.2-1_all.deb diff --git a/pages/instances/troubleshooting/reboot-from-faulty-kernel.mdx b/pages/instances/troubleshooting/reboot-from-faulty-kernel.mdx index f001e1b8e6..7edff2287d 100644 --- a/pages/instances/troubleshooting/reboot-from-faulty-kernel.mdx +++ b/pages/instances/troubleshooting/reboot-from-faulty-kernel.mdx @@ -3,7 +3,7 @@ title: Troubleshooting issues with faulty kernel installations description: Learn how to troubleshoot and resolve issues caused by faulty kernel installations with our comprehensive guide. tags: kernel faulty-kernel reboot bugfix dates: - validation: 2025-01-06 + validation: 2025-07-15 posted: 2022-11-23 categories: - compute @@ -21,7 +21,7 @@ import Requirements from '@macros/iam/requirements.mdx' 1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the CLI-Tools: - ``` + ```sh scw instance server update {Instance_ID} boot-type=rescue scw instance server reboot {Instance_ID} ``` @@ -82,7 +82,7 @@ import Requirements from '@macros/iam/requirements.mdx' done ``` 5. Switch back the Instance's `boot_type` to `local` and reboot the Instance: - ``` + ```sh scw instance server update {Instance_ID} boot-type=local scw instance server reboot {Instance_ID} ``` diff --git a/pages/ipam/how-to/reserve-ip.mdx b/pages/ipam/how-to/reserve-ip.mdx index 25585d8e99..7304642b28 100644 --- a/pages/ipam/how-to/reserve-ip.mdx +++ b/pages/ipam/how-to/reserve-ip.mdx @@ -18,7 +18,7 @@ import image from './assets/scaleway-reserve-ip.webp' You can use IPAM to reserve a private IP address from a given Private Network's [CIDR block](/vpc/concepts/#cidr-block). When you reserve an IP in this way, it stops it from being potentially auto-allocated to new resources being attached to the Private Network. You can then use the reserved address to attach the specific resource of your choice to the Private Network. If you later detach the resource from the network, the reserved IP will stay reserved, until you either release it back into the general pool, or use it to attach a different resource. -Currently, only **Instances**, **Elastic Metal servers**, **Load Balancers**, and **Public Gateways** are compatible with reserved private IPs. Support for Managed Databases will be coming soon. +Currently, only **CPU & GPU Instances**, **Elastic Metal servers**, **Load Balancers**, and **Public Gateways** are compatible with reserved private IPs. Support for Managed Databases will be coming soon. This page sets out the steps necessary to reserve an IP address with IPAM. @@ -58,7 +58,7 @@ The procedure is the same, whether you want to use the IP to attach a Scaleway-m ## How to attach a managed resource to a Private Network using a reserved IP address -You can currently attach **Instances**, **Elastic Metal servers**, **Load Balancers**, and **Public Gateways** to Private Networks using a reserved IP address. Support for Managed Databases will be coming soon. +You can currently attach **CPU & GPU Instances**, **Elastic Metal servers**, **Load Balancers**, and **Public Gateways** to Private Networks using a reserved IP address. Support for Managed Databases will be coming soon. The option to use a reserved IP displays when you attach the resource to a Private Network in the console. Follow the instructions below: diff --git a/pages/ipam/reference-content/public-connectivity-best-practices.mdx b/pages/ipam/reference-content/public-connectivity-best-practices.mdx index 648aa9f931..69c85a9a8c 100644 --- a/pages/ipam/reference-content/public-connectivity-best-practices.mdx +++ b/pages/ipam/reference-content/public-connectivity-best-practices.mdx @@ -24,7 +24,7 @@ Public vs private connectivity defines how resources are accessed and exposed ov ### Flexible IP addresses: definition -Public connectivity for **Instances**, **Elastic Metal**, **Load Balancers** and **Public Gateways** is facilitated by a [flexible IP address](/ipam/concepts/#public-flexible-ip-address). +Public connectivity for **CPU & GPU Instances**, **Elastic Metal**, **Load Balancers** and **Public Gateways** is facilitated by a [flexible IP address](/ipam/concepts/#public-flexible-ip-address). - A flexible IP address is a public IP address that you can attach and detach from the resource at will. - If you detach it, it returns to the pool of flexible IP addresses kept in your account for that product, and you can attach it to a different resource (or reattach it to the same one as before). diff --git a/pages/ipam/reference-content/understanding-ip-billing.mdx b/pages/ipam/reference-content/understanding-ip-billing.mdx index e5bc47aa18..80d48af49c 100644 --- a/pages/ipam/reference-content/understanding-ip-billing.mdx +++ b/pages/ipam/reference-content/understanding-ip-billing.mdx @@ -13,7 +13,7 @@ This document aims to help you understand how Scaleway bills **public** and **pr ## Public IP addresses - flexible IPs -Public connectivity for **Instances**, **Elastic Metal**, **Load Balancers** and **Public Gateways** is facilitated by a [flexible IP address](/ipam/reference-content/public-connectivity-best-practices/#flexible-ip-addresses-definition). A flexible IP address is a public IP address that you can attach and detach from the resource at will. +Public connectivity for **CPU & GPU Instances**, **Elastic Metal**, **Load Balancers** and **Public Gateways** is facilitated by a [flexible IP address](/ipam/reference-content/public-connectivity-best-practices/#flexible-ip-addresses-definition). A flexible IP address is a public IP address that you can attach and detach from the resource at will. - Flexible IP addresses are billed separately to the resources they are attached to. - Hourly rates for different types of flexible IP addresses can be found on the [Scaleway pricing page](https://www.scaleway.com/en/pricing/network/#additional-ip). Note that while flexible IPv4 addresses are generally billable, flexible IPv6 addresses are often free. diff --git a/pages/kubernetes/how-to/enable-disable-ssh.mdx b/pages/kubernetes/how-to/enable-disable-ssh.mdx index 56767a845b..ca9edac6e4 100644 --- a/pages/kubernetes/how-to/enable-disable-ssh.mdx +++ b/pages/kubernetes/how-to/enable-disable-ssh.mdx @@ -3,7 +3,7 @@ title: How to enable or disable SSH ports on Kubernetes Kapsule cluster nodes description: This page explains how to enable or disable SSH ports on Kubernetes Kapsule cluster nodes. tags: kubernetes kapsule-cluster dates: - validation: 2025-01-06 + validation: 2025-07-15 posted: 2023-05-02 categories: - containers @@ -21,7 +21,7 @@ To activate the preinstalled SSH server for node access within the cluster, it i - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - [Created](/kubernetes/how-to/create-cluster/) a Kubernetes Kapsule cluster -1. Click **Instances** in the side menu, then click **Security groups** to view the [security group](https://console.scaleway.com/instance/security-groups) section in your Scaleway console. +1. Click **CPU & GPU Instances** in the side menu, then click **Security groups** to view the [security group](https://console.scaleway.com/instance/security-groups) section in your Scaleway console. 2. Click next to the security group you intend to configure and choose **More info**. The security group's overview displays. Alternatively, you can also select the security group's name. The security group's overview displays. diff --git a/pages/kubernetes/reference-content/exposing-services.mdx b/pages/kubernetes/reference-content/exposing-services.mdx index 2900a245b4..6abcaff0fa 100644 --- a/pages/kubernetes/reference-content/exposing-services.mdx +++ b/pages/kubernetes/reference-content/exposing-services.mdx @@ -3,7 +3,7 @@ title: Exposing Kubernetes services to the internet description: Exposing Kubernetes services to the internet tags: kubernetes k8s wildcard clusterip nodeport node-port loadbalancer load-balancer ingress ingress-controller dates: - validation: 2025-01-06 + validation: 2025-07-15 posted: 2023-10-25 categories: - kubernetes diff --git a/pages/kubernetes/reference-content/managed-kubernetes-service-definition.mdx b/pages/kubernetes/reference-content/managed-kubernetes-service-definition.mdx index f6869e2383..b529d935b1 100644 --- a/pages/kubernetes/reference-content/managed-kubernetes-service-definition.mdx +++ b/pages/kubernetes/reference-content/managed-kubernetes-service-definition.mdx @@ -3,7 +3,7 @@ title: Managed Kubernetes service definition description: This page explains the definition of the managed Kubernetes service at Scaleway tags: kubernetes kubernetes-kapsule kapsule kosmos kubernetes-kosmos managed service definition dates: - validation: 2025-01-06 + validation: 2025-07-15 posted: 2023-07-06 categories: - kubernetes @@ -34,7 +34,7 @@ Furthermore, Scaleway provides information and reminders when older versions rea Scaleway is committed to providing updates on the product lifecycle as follows: - - Notification of feature deprecation will be announced in the [changelog](/changelog/?tags=containers_kubernetes,status_deprecated/). + - Notification of feature deprecation will be announced in the [changelog](/changelog/?products=kubernetes&status=deprecated). - Information regarding a feature's End of Life (EOL) will be communicated through support tickets in the console and [scheduled maintenance notices](https://status.scaleway.com/). Upon reaching EOL, Scaleway will either remove the feature or initiate a migration (if applicable). While Scaleway endeavors to maintain service continuity, this cannot be guaranteed.

diff --git a/pages/vpc/reference-content/use-case-basic.mdx b/pages/vpc/reference-content/use-case-basic.mdx index 40252952c3..e8e1d69927 100644 --- a/pages/vpc/reference-content/use-case-basic.mdx +++ b/pages/vpc/reference-content/use-case-basic.mdx @@ -37,7 +37,7 @@ Full [Terraform/OpenTofu templates](##terraformopentofu) are available for this ## Detail -User requests go via a domain name, whose DNS record points to the public flexible IP of a Scaleway Load Balancer. This Load Balancer is attached to a **Private Network** in a **VPC**. It distributes user traffic to multiple **Instances** which are also attached to the Private Network, and do not have their own public/flexible IP addresses. These Instances are accessible only from within the VPC. The Instances can store data to and retrieve data from **Block Storage** and a **Managed Database** attached to the same Private Network and not exposed to the internet. +User requests go via a domain name, whose DNS record points to the public flexible IP of a Scaleway Load Balancer. This Load Balancer is attached to a **Private Network** in a **VPC**. It distributes user traffic to multiple **CPU & GPU Instances** which are also attached to the Private Network, and do not have their own public/flexible IP addresses. These Instances are accessible only from within the VPC. The Instances can store data to and retrieve data from **Block Storage** and a **Managed Database** attached to the same Private Network and not exposed to the internet. The **Public Gateway** attached to the Private Network has its own public flexible IP address, and administrators can use solutions such as SSH bastion to connect to Instances via the Public Gateway for maintenance and administrative tasks. The Public Gateway also provides secure access to the public internet should the Instances need to download package updates, for example. Finally, the Public Gateway also allows the Instances to access services outside the VPC, e.g. those hosted on other Scaleway resources which are not compatible with VPC, via their public endpoints. diff --git a/tutorials/create-valheim-server/index.mdx b/tutorials/create-valheim-server/index.mdx index dd14b86062..21f54e212e 100644 --- a/tutorials/create-valheim-server/index.mdx +++ b/tutorials/create-valheim-server/index.mdx @@ -29,7 +29,7 @@ At Scaleway, we offer a large range of Instances that will suit the gaming needs ## Deploying an Instance -1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers/create) displays. 3. Enter the required information for your Instance: * The **Availability Zone** is the geographical region in which your Instance will be deployed. In this tutorial, we use `FR-PAR2`, but you can choose the one closest to your location. diff --git a/tutorials/deploy-phpmyadmin-with-docker/index.mdx b/tutorials/deploy-phpmyadmin-with-docker/index.mdx index 01ed39db2c..e0373f51da 100644 --- a/tutorials/deploy-phpmyadmin-with-docker/index.mdx +++ b/tutorials/deploy-phpmyadmin-with-docker/index.mdx @@ -30,7 +30,7 @@ In this tutorial, you learn how to deploy the tool on an [Instance](https://www. ## Creating a Docker Instance -1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 **Create Instance**. The [Instance creation wizard](https://console.scaleway.com/instance/servers/create) displays. 3. Configure your Instance: * Choose the Availability Zone. diff --git a/tutorials/deploy-ubuntu-20-04-instance-scaleway-elements/index.mdx b/tutorials/deploy-ubuntu-20-04-instance-scaleway-elements/index.mdx index 3f1aeb170a..5a422ecfc9 100644 --- a/tutorials/deploy-ubuntu-20-04-instance-scaleway-elements/index.mdx +++ b/tutorials/deploy-ubuntu-20-04-instance-scaleway-elements/index.mdx @@ -32,7 +32,7 @@ In this tutorial, you will learn how to deploy an Instance with Ubuntu 20.04 LTS ## Deploying your Ubuntu Linux Instance from the Scaleway console -1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 **Create Instance**. The [Instance creation wizard](https://console.scaleway.com/instance/servers/create) displays. 3. Configure your Instance: * Choose an Availability Zone diff --git a/tutorials/deploy-ubuntu-22-04-instance/index.mdx b/tutorials/deploy-ubuntu-22-04-instance/index.mdx index 1f04c7f2a3..63c395149b 100644 --- a/tutorials/deploy-ubuntu-22-04-instance/index.mdx +++ b/tutorials/deploy-ubuntu-22-04-instance/index.mdx @@ -26,7 +26,7 @@ In this tutorial, you learn how to deploy an Instance with Ubuntu 22.04 LTS (Jam ## Deploying your Ubuntu Linux Instance from the Scaleway console -1. Click **Instances** in the **Compute** section of the side menu. The [Instance creation page](https://console.scaleway.com/instance/servers/create) displays. +1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instance creation page](https://console.scaleway.com/instance/servers/create) displays. 2. Configure your Instance: * Choose an Availability Zone * An Availability Zone refers to the geographical location in which your Instance will be created. diff --git a/tutorials/foreman-puppet/index.mdx b/tutorials/foreman-puppet/index.mdx index 08212814a5..8284425f94 100644 --- a/tutorials/foreman-puppet/index.mdx +++ b/tutorials/foreman-puppet/index.mdx @@ -55,7 +55,7 @@ The Foreman installer uses Puppet (> 3.x required) to install the software. To retrieve the Instance's IP, list your existing servers using `scw ps` (Scaleway CLI). For more information on the Scaleway CLI, refer to the tutorial on the [Scaleway Command Line Interface](https://github.com/scaleway/scaleway-cli/). - The Instance's IP can also be retrieved from the Scaleway console. Once logged in, check the **IP addresses** in the **Instances** tab of the left menu. + The Instance's IP can also be retrieved from the Scaleway console. Once logged in, check the **IP addresses** in the **CPU & GPU Instances** tab of the left menu. 2. Check your Instance's full hostname to ensure the hostname is set to a valid [FQDN](https://en.wikipedia.org/wiki/Fully_qualified_domain_name). ``` hostname diff --git a/tutorials/gitlab-instant-app/index.mdx b/tutorials/gitlab-instant-app/index.mdx index fa42c62e86..d6711b2fda 100644 --- a/tutorials/gitlab-instant-app/index.mdx +++ b/tutorials/gitlab-instant-app/index.mdx @@ -23,7 +23,7 @@ Scaleway provides a GitLab image that is built on Ubuntu 22.04 LTS (Jammy Jellyf ## Creating a GitLab Instance -1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 **Create Instance**. The [Instance creation wizard](https://console.scaleway.com/instance/servers/create) displays. 3. Choose the Availability Zone for your Instance. 4. Select the Instance type you want to create. diff --git a/tutorials/mutli-node-rocket-chat-community-private-network/index.mdx b/tutorials/mutli-node-rocket-chat-community-private-network/index.mdx index 14c3635e56..84cf65b7b2 100644 --- a/tutorials/mutli-node-rocket-chat-community-private-network/index.mdx +++ b/tutorials/mutli-node-rocket-chat-community-private-network/index.mdx @@ -50,12 +50,12 @@ To reach the goal of this tutorial, you will use four [Production-Optimized Inst ## Configuring the Private Network -1. Log in to your [Scaleway console](https://console.scaleway.com/) and enter the **Instances** section from the **Compute** group on the side menu. +1. Log in to your [Scaleway console](https://console.scaleway.com/) and enter the **CPU & GPU Instances** section from the **Compute** group on the side menu. 2. Click **Private Networks** to display a list of your Private Networks. Click **+Create a Private Network** to create a new one. 3. Enter the details of the Private Network. Make sure to create the Private Network in the same geographical region as your Instances: -4. Select the newly created Private Network from your networks list. From the drop-down list, click the **Instances** tab to add your Instances: +4. Select the newly created Private Network from your networks list. From the drop-down list, click the **CPU & GPU Instances** tab to add your Instances: 5. Add all Instances for your Rocket.Chat setup to the Private Network. Once added, they are listed on the network overview page together with their corresponding virtual MAC address: diff --git a/tutorials/nextcloud-instantapp/index.mdx b/tutorials/nextcloud-instantapp/index.mdx index 61cfe1fa72..6da693a08a 100644 --- a/tutorials/nextcloud-instantapp/index.mdx +++ b/tutorials/nextcloud-instantapp/index.mdx @@ -26,7 +26,7 @@ Scaleway's NextCloud image is based on Ubuntu 22.04 LTS (Jammy Jellyfish), the N ## Creating a NextCloud Instance -1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 **Create Instance**. The [Instance creation wizard](https://console.scaleway.com/instance/servers/create) displays. 3. Choose the Availability Zone for your Instance. 4. Select the Instance type you want to create. diff --git a/tutorials/openvpn-instant-app/index.mdx b/tutorials/openvpn-instant-app/index.mdx index 45ba1ff84b..76b27c8b91 100644 --- a/tutorials/openvpn-instant-app/index.mdx +++ b/tutorials/openvpn-instant-app/index.mdx @@ -30,7 +30,7 @@ OpenVPN InstantApp comes with: - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - Installed a VPN client on your local machine -1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 **Create Instance**. The [Instance creation wizard](https://console.scaleway.com/instance/servers/create) displays. 3. Choose the **OpenVPN** image in the **InstantApps** tab: 4. Follow the remaining steps to [create your Instance](/instances/how-to/create-an-instance/). diff --git a/tutorials/setup-ampere-ai-framework-arm-instances/index.mdx b/tutorials/setup-ampere-ai-framework-arm-instances/index.mdx index 06d87c4c07..5ad6e25081 100644 --- a/tutorials/setup-ampere-ai-framework-arm-instances/index.mdx +++ b/tutorials/setup-ampere-ai-framework-arm-instances/index.mdx @@ -28,7 +28,7 @@ In this tutorial, we will walk through the process of setting up and using Amper ## Setting up the COP-ARM Instance -1. Navigate to your [Scaleway console](https://console.scaleway.com/). Once logged in, click **Instances**, then select **Create Instance** to get started. +1. Navigate to your [Scaleway console](https://console.scaleway.com/). Once logged in, click **CPU & GPU Instances**, then select **Create Instance** to get started. 2. Choose your preferred Availability Zone. Currently, COP-ARM Instances are exclusively available in the **PARIS2** zone. diff --git a/tutorials/setup-k8s-cluster-rancher/index.mdx b/tutorials/setup-k8s-cluster-rancher/index.mdx index 22fa9d4168..8db40f4693 100644 --- a/tutorials/setup-k8s-cluster-rancher/index.mdx +++ b/tutorials/setup-k8s-cluster-rancher/index.mdx @@ -42,7 +42,7 @@ The Rancher UI makes it easy to manage secrets, roles, and permissions. It allow ## Spinning up the required Instances -1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 **Create Instance**. The [Instance creation wizard](https://console.scaleway.com/instance/servers/create) displays. 3. To deploy Instances with [Docker](https://www.docker.com/) preinstalled, click **+ Create Instance**: diff --git a/tutorials/wordpress-instantapp/index.mdx b/tutorials/wordpress-instantapp/index.mdx index b9fc58dd62..35e404431f 100644 --- a/tutorials/wordpress-instantapp/index.mdx +++ b/tutorials/wordpress-instantapp/index.mdx @@ -65,7 +65,7 @@ When defining the `weblog_title` tag on the console, it is not possible to have ### Deploy WordPress -1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 **Create Instance**. The [Instance creation wizard](https://console.scaleway.com/instance/servers/create) displays. 3. Choose an Availability Zone and an Instance type. 4. Choose the **WordPress** image in the **InstantApps** tab. @@ -85,7 +85,7 @@ To avoid spam, remote mail ports cannot be reached from our infrastructure by de ## Configure and start using WordPress -1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. +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 your WordPress Instance. 3. Copy your Instance's public IP address and paste it into your browser. 4. Select a language and click **Continue**. The WordPress admin page displays.