From e30de11391dbde3f48baf09e8b7c57cc21cfada4 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Thu, 18 Dec 2025 15:53:46 +0100 Subject: [PATCH 1/3] docs(ins): update creation funnel --- .../gpu/how-to/create-manage-gpu-instance.mdx | 18 +++-- pages/gpu/quickstart.mdx | 18 +++-- pages/instances/how-to/create-an-instance.mdx | 48 ++++++++------ pages/instances/quickstart.mdx | 65 ++++++++++--------- 4 files changed, 87 insertions(+), 62 deletions(-) diff --git a/pages/gpu/how-to/create-manage-gpu-instance.mdx b/pages/gpu/how-to/create-manage-gpu-instance.mdx index a90f2381e2..d6c6344c4d 100644 --- a/pages/gpu/how-to/create-manage-gpu-instance.mdx +++ b/pages/gpu/how-to/create-manage-gpu-instance.mdx @@ -27,11 +27,13 @@ When you have completed your calculations using the GPU Instance, [deletion can 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. - - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. - - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Noble GPU OS 13 (NVIDIA)**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You can customize your working environment using Docker with our provided Docker images or your own containers. +3. Select the desired GPU Instance type and choose and its Availability Zone in the pop-up. Click **Configure Instance** to continue. + + You can use the filter to find the GPU Instance type that suits best your requirements. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. + +4. Follow these steps to configure your GPU Instance: - **Instance name and tags**: Assign a name to your Instance for easy identification. You can also add tags to organize your Instances efficiently. + - **Image**: Pick an GPU OS image suitable for your GPU Instance. For example, select **Ubuntu Noble GPU OS 13 (Nvidia)**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You can customize your working environment using Docker with our provided Docker images or your own containers. - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local Storage volumes according to your requirements. * The recommended minimum volume size for GPU OS images is 125 GB. @@ -39,9 +41,13 @@ When you have completed your calculations using the GPU Instance, [deletion can - **Network configuration**: You can allocate routed IPv4 and IPv6 addresses as needed, with a maximum of 5 IPs per Instance. - **Cloud-init**: Configure `cloud-init` settings if required, or leave them at default values. + + Cloud-init scripts are the standard way to automate Instance setup, such as setting up software, users, and system configurations at the first boot. [Learn more](/instances/how-to/use-cloud-init/). + - **SSH keys**: Verify the SSH keys that will grant you access to your Instance. - - **Estimated cost**: Review the estimated cost of your GPU Instance based on the selected specifications. -4. Once you have completed the configuration, click on **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use. + - Click **Review** to view a summary of your Instance configuration and estimated costs. + +5. Once you have verified the configuration of your GPU Instance, click on **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use. ## How to connect to a GPU Instance diff --git a/pages/gpu/quickstart.mdx b/pages/gpu/quickstart.mdx index c27deb2cd4..39c6cd30ae 100644 --- a/pages/gpu/quickstart.mdx +++ b/pages/gpu/quickstart.mdx @@ -21,11 +21,13 @@ In addition to this, GPU Instances have all the features of our regular Instance 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. - - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. - - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Noble GPU OS 13 (NVIDIA)**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You can customize your working environment using Docker with our provided Docker images or your own containers. +3. Select the desired GPU Instance type and choose and its Availability Zone in the pop-up. Click **Configure Instance** to continue. + + You can use the filter to find the GPU Instance type that suits best your requirements. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. + +4. Follow these steps to configure your GPU Instance: - **Instance name and tags**: Assign a name to your Instance for easy identification. You can also add tags to organize your Instances efficiently. + - **Image**: Pick an GPU OS image suitable for your GPU Instance. For example, select **Ubuntu Noble GPU OS 13 (Nvidia)**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You can customize your working environment using Docker with our provided Docker images or your own containers. - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local Storage volumes according to your requirements. * The recommended minimum volume size for GPU OS images is 125 GB. @@ -33,9 +35,13 @@ In addition to this, GPU Instances have all the features of our regular Instance - **Network configuration**: You can allocate routed IPv4 and IPv6 addresses as needed, with a maximum of 5 IPs per Instance. - **Cloud-init**: Configure `cloud-init` settings if required, or leave them at default values. + + Cloud-init scripts are the standard way to automate Instance setup, such as setting up software, users, and system configurations at the first boot. [Learn more](/instances/how-to/use-cloud-init/). + - **SSH keys**: Verify the SSH keys that will grant you access to your Instance. - - **Estimated cost**: Review the estimated cost of your GPU Instance based on the selected specifications. -4. Once you have completed the configuration, click on **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use. + - Click **Review** to view a summary of your Instance configuration and estimated costs. + +5. Once you have verified the configuration of your GPU Instance, click on **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use. ## How to connect to your GPU Instance diff --git a/pages/instances/how-to/create-an-instance.mdx b/pages/instances/how-to/create-an-instance.mdx index 3c693ea1e8..9515de1f35 100644 --- a/pages/instances/how-to/create-an-instance.mdx +++ b/pages/instances/how-to/create-an-instance.mdx @@ -25,13 +25,15 @@ Select a tab below for instructions on how to create an Instance via either our 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. - - **Choose an Instance type**.
- Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/instances/reference-content/choosing-instance-type/). + 3. Chose an **Instance range**. You can choose from [General Purpose](/instances/reference-content/general-purpose), [Development](/instances/reference-content/development/), or [Specialized](/instances/reference-content/specialized/) Instances. Click **See Instances**. + + Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/instances/reference-content/choosing-instance-type/). + + 4. Select the desired Instance type and choose and Availability Zone in the pop-up. Click **Configure Instance** to continue. + 5. Complete the following steps: + - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/instances/concepts/#tags) to help you organize your Instance. - **Choose an image** to run on your Instance.
This can be an operating system, an InstantApp, or a custom image. [Check all available Linux distributions and InstantApps](/instances/reference-content/images-and-instantapps/). - - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/instances/concepts/#tags) to help you organize your Instance. - **Add volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed. - Ensure that the volume containing your OS image has a minimum size of 10 GB. For a GPU OS, the recommended size is 125 GB. @@ -44,13 +46,15 @@ Select a tab below for instructions on how to create an Instance via either our You can attach up to 5 IPv4 and 5 IPv6 addresses to an Instance, which is useful for running different services or applications on the same Instance. - - (Optional) Click **Cloud-init** to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave this option set to its default values. - Cloud-init scripts are the standard way to automate Instance setup, such as setting up software, users, and system configurations at the first boot. - - **Verify the [SSH keys](/organizations-and-projects/concepts/#ssh-key)** that will give you access to your Instance. - - **Verify the Estimated cost** of your Instance, based on the specifications you chose. - 4. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready. + - (Optional) Click **+ Cloud-init** and toggle the switch to be able to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave this option set to its default values. + + Cloud-init scripts are the standard way to automate Instance setup, such as setting up software, users, and system configurations at the first boot. [Learn more](/instances/how-to/use-cloud-init/). + + - **Verify the [SSH keys](/organizations-and-projects/concepts/#ssh-key)** that are allowed to access your Instance. + - Click **Review** to view a summary of your Instance configuration and estimated costs. + 6. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready. - Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the SSH command to use to [connect to it](/instances/how-to/create-an-instance/), and other information, settings, and actions for the Instance. + Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the SSH command to use to [connect to it](/instances/how-to/connect-to-instance/), and other information, settings, and actions for the Instance. @@ -63,11 +67,15 @@ Select a tab below for instructions on how to create an Instance via either our 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. - - **Choose a Windows** Instance type from the **General Purpose** range. - - **Choose a Windows Server image** to run on your Instance. + 3. Chose the **General Purpose** Instance range. Click **See Instances**. + + Currently, only selected **General Purpose** Instances are compatible with Windows OS. + + 4. Select the desired Instance type and choose and Availability Zone in the pop-up. Click **Configure Instance** to continue. + + 5. Complete the following steps: - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/instances/concepts/#tags) to help you organize your Instance. + - **Choose a Windows Server image** to run on your Instance. - **Add volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed. - Ensure that a volume containing a Windows Server image has a minimum capacity of 25 GB. @@ -87,14 +95,16 @@ Select a tab below for instructions on how to create an Instance via either our You can attach up to 5 IPv4 and 5 IPv6 addresses to an Instance, which is useful for running different services or applications on the same Instance. - - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave these options at their default values. - Cloud-init scripts are the standard way to automate Instance setup, such as setting up software, users, and system configurations at the first boot. + - (Optional) Click **+ Cloud-init** and toggle the switch to be able to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave this option set to its default values. + + Cloud-init scripts are the standard way to automate Instance setup, such as setting up software, users, and system configurations at the first boot. [Learn more](/instances/how-to/use-cloud-init/). + - **Choose the [RSA SSH key](/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-a-rsa-ssh-key-pair)** that will give you access to your Instance. If you do not have an RSA SSH key yet, click **Add RSA SSH key** and follow the steps indicated. To activate the OpenSSH Server during Instance creation, add a `with-ssh` tag before launching the Instance. - - Verify the **Estimated cost** of your Instance, based on the specifications you chose. - 4. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready. + - Click **Review** to view a summary of your Instance configuration and estimated costs. + 6. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready. Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the command to use to [retrieve the password and connect to it](/instances/how-to/connect-to-instance/), and other information, settings, and actions for the Instance. diff --git a/pages/instances/quickstart.mdx b/pages/instances/quickstart.mdx index daa2b2eeda..1635e203f9 100644 --- a/pages/instances/quickstart.mdx +++ b/pages/instances/quickstart.mdx @@ -17,37 +17,40 @@ Scaleway [Instances](/instances/concepts/#instance) are computing units that pro - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) -## How to create an Instance - - 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. - - **Choose an Instance type**.
- Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/instances/reference-content/choosing-instance-type/). - - **Choose an image** to run on your Instance.
- This can be an operating system, an InstantApp, or a custom image. [Check all available operating system images and InstantApps](/instances/reference-content/images-and-instantapps/). - - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/instances/concepts/#tags) to help you organize your Instance. - - **Add Volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed. - - - Ensure that the volume containing your OS image has a minimum size of 10 GB. For a GPU OS, the recommended size is 125 GB. - - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. If needed, the boot volume can be changed after the creation of the Instance; [see how](/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume). - - Booting from a volume that either lacks an OS or is among multiple volumes with identical operating systems can lead to inconsistent boot outcomes. - - - **Configure network** of the Instance. - - Leave the checkbox ticked to assign a **Public IPv4** to the Instance. You can either allocate a new IPv4 address or select one or multiple existing IPv4s. Alternatively, uncheck the box if you do not want an IPv4. - - Leave the checkbox ticked to assign a **Public IPv6** to the Instance. You can either allocate a new IPv6 address or select one or multiple existing IPv6s. Alternatively, uncheck the box if you do not want an IPv6. - - You can attach up to 5 IPv4 and 5 IPv6 addresses to an Instance, which is useful for running different services or applications on the same Instance. - - - (Optional) Click **Cloud-init** to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave this option set to its default values. - Cloud-init scripts are the standard way to automate Instance setup, such as setting up software, users, and system configurations at the first boot. - - **Verify the [SSH keys](/organizations-and-projects/concepts/#ssh-key)** that will give you access to your Instance. - - **Verify the Estimated cost** of your Instance, based on the specifications you chose. - 4. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready. - Once the Instance is created, you can connect to it using the SSH keys you have configured, and begin setting up your applications. - -## How to connect to an Instance +## How to create a Linux Instance + +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. Chose an **Instance range**. You can choose from [General Purpose](/instances/reference-content/general-purpose), [Development](/instances/reference-content/development/), or [Specialized](/instances/reference-content/specialized/) Instances. Click **See Instances**. + + Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/instances/reference-content/choosing-instance-type/). + +4. Select the desired Instance type and choose and Availability Zone in the pop-up. Click **Configure Instance** to continue. +5. Complete the following steps: + - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/instances/concepts/#tags) to help you organize your Instance. + - **Choose an image** to run on your Instance.
+ This can be an operating system, an InstantApp, or a custom image. [Check all available Linux distributions and InstantApps](/instances/reference-content/images-and-instantapps/). + - **Add volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed. + + - Ensure that the volume containing your OS image has a minimum size of 10 GB. For a GPU OS, the recommended size is 125 GB. + - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. If needed, the boot volume can be changed after the creation of the Instance; [see how](/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume). + - Booting from a volume that either lacks an OS or is among multiple volumes with identical operating systems can lead to inconsistent boot outcomes. + + - **Configure network** of the Instance. + - Leave the checkbox ticked to assign a **Public IPv4** to the Instance. You can either allocate a new IPv4 address or select one or multiple existing IPv4s. Alternatively, uncheck the box if you do not want an IPv4. + - Leave the checkbox ticked to assign a **Public IPv6** to the Instance. You can either allocate a new IPv6 address or select one or multiple existing IPv6s. Alternatively, uncheck the box if you do not want an IPv6. + + You can attach up to 5 IPv4 and 5 IPv6 addresses to an Instance, which is useful for running different services or applications on the same Instance. + + - (Optional) Click **+ Cloud-init** and toggle the switch to be able to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave this option set to its default values. + + Cloud-init scripts are the standard way to automate Instance setup, such as setting up software, users, and system configurations at the first boot. [Learn more](/instances/how-to/use-cloud-init/). + + - **Verify the [SSH keys](/organizations-and-projects/concepts/#ssh-key)** that are allowed to access your Instance. + - Click **Review** to view a summary of your Instance configuration and estimated costs. +6. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready. + + Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the SSH command to use to [connect to it](/instances/how-to/connect-to-instance/), and other information, settings, and actions for the Instance. ### How to connect from OSX (Mac) and Linux From 74b46a9a93d07b35300bb078fc2c6409ac814f49 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Fri, 19 Dec 2025 15:40:01 +0100 Subject: [PATCH 2/3] Update pages/gpu/how-to/create-manage-gpu-instance.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Néda <87707325+nerda-codes@users.noreply.github.com> --- pages/gpu/how-to/create-manage-gpu-instance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/gpu/how-to/create-manage-gpu-instance.mdx b/pages/gpu/how-to/create-manage-gpu-instance.mdx index d6c6344c4d..bac69de2b7 100644 --- a/pages/gpu/how-to/create-manage-gpu-instance.mdx +++ b/pages/gpu/how-to/create-manage-gpu-instance.mdx @@ -33,7 +33,7 @@ When you have completed your calculations using the GPU Instance, [deletion can 4. Follow these steps to configure your GPU Instance: - **Instance name and tags**: Assign a name to your Instance for easy identification. You can also add tags to organize your Instances efficiently. - - **Image**: Pick an GPU OS image suitable for your GPU Instance. For example, select **Ubuntu Noble GPU OS 13 (Nvidia)**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You can customize your working environment using Docker with our provided Docker images or your own containers. + - **Image**: Pick a GPU OS image suitable for your GPU Instance. For example, select **Ubuntu Noble GPU OS 13 (Nvidia)**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You can customize your working environment using Docker with our provided Docker images or your own containers. - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local Storage volumes according to your requirements. * The recommended minimum volume size for GPU OS images is 125 GB. From f43e997c5b5b3b1b796446cad5372e3621758a80 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Fri, 19 Dec 2025 15:49:03 +0100 Subject: [PATCH 3/3] Update pages/gpu/how-to/create-manage-gpu-instance.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Néda <87707325+nerda-codes@users.noreply.github.com> --- pages/gpu/how-to/create-manage-gpu-instance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/gpu/how-to/create-manage-gpu-instance.mdx b/pages/gpu/how-to/create-manage-gpu-instance.mdx index bac69de2b7..b1f9d7ae6d 100644 --- a/pages/gpu/how-to/create-manage-gpu-instance.mdx +++ b/pages/gpu/how-to/create-manage-gpu-instance.mdx @@ -47,7 +47,7 @@ When you have completed your calculations using the GPU Instance, [deletion can - **SSH keys**: Verify the SSH keys that will grant you access to your Instance. - Click **Review** to view a summary of your Instance configuration and estimated costs. -5. Once you have verified the configuration of your GPU Instance, click on **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use. +5. Once you have verified the configuration of your GPU Instance, click **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use. ## How to connect to a GPU Instance