feat(ins): update create instance (#3850)

* feat(ins): update create instance * Update compute/instances/how-to/create-an-instance.mdx Co-authored-by: SamyOubouaziz <soubouaziz@scaleway.com> * Update compute/instances/quickstart.mdx Co-authored-by: SamyOubouaziz <soubouaziz@scaleway.com> --------- Co-authored-by: SamyOubouaziz <soubouaziz@scaleway.com>
scaleway · Oct 17, 2024 · 7bab1e3 · 7bab1e3
1 parent f3f65f6
commit 7bab1e3
Show file tree

Hide file tree

Showing 2 changed files with 39 additions and 41 deletions.
diff --git a/compute/instances/how-to/create-an-instance.mdx b/compute/instances/how-to/create-an-instance.mdx
@@ -31,29 +31,28 @@ Select a tab below for instructions on how to create an Instance via either our
     1. Click **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**. <br />
+        - **Choose an Availability Zone**, which represents the geographical region where your Instance will be deployed.
+        - **Choose an Instance type**. <br />
           Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/compute/instances/reference-content/choosing-instance-type/).
-        - Choose an **Image** to run on your Instance. <br />
+        - ***Choose an Image** to run on your Instance. <br />
           This can be an operating system, an InstantApp, or a custom image. [Check all available Linux distributions and InstantApps](/compute/instances/reference-content/images-and-instantapps/).
-        - Add **Volumes**, which are storage spaces used by your Instances.
-          - For **GP1 Instances** you can leave the default settings of maximum local storage, or choose how much [local](/compute/instances/concepts/#local-volumes) and/or [block](/compute/instances/concepts/#block-volumes) storage you want. Your **system volume** is the volume on which your Instance will boot. The system volume can be either a local or a block volume.
-          - **PLAY2**, **PRO2**, and **Enterprise** Instances boot directly [on block volumes](/compute/instances/concepts/#boot-on-block). You can add several block volumes and define how much storage you want for each.
+        - **Name** your Instance, or leave the randomly-generated name in place. Optionally, you can add [tags](/compute/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 up to 16 local and/or block type volumes as needed.
           <Message type="important">
-             - Ensure that a volume with an OS image has a minimum capacity of 10 GB. For a GPU OS, the recommended size is 125 GB.
+             - 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. Once the Instance is created can [modify your boot volume](/compute/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.
           </Message>
-        - Configure the network of the Instance. You can either select to use **Routed public IP** (a dedicated public IP address routed to your Instance that allows direct communication between the Instance and the Internet) or a **NAT public IP** (a public IP address that uses a carrier-grade NAT to translate the Instances NAT IP address). If you are unsure which to use, we recommend a routed public IP for ease of use and improved performance.
+        - **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.
             <Message type="tip">
-              You can attach up to 5 IPs to an Instance, combining IPv4 and IPv6 addresses.
+              You can attach up to 5 IPs to an Instance, combining IPv4 and IPv6 addresses, which is useful for running different services or applications on the same Instance.
             </Message>
-        - Enter a **Name** for your Instance, or leave the randomly-generated name in place. Optionally, you can add [tags](/compute/instances/concepts/#tags) to help you organize your Instance.
-        - Click **Advanced options** if you want to configure a [cloud-init configuration](/compute/instances/concepts/#cloud-init). Otherwise, leave these options at their default values.
-        - Verify the [SSH keys](/console/account/concepts/#ssh-key) that will give you access to your Instance.
-        - Verify the **Estimated cost** of your Instance, based on the specifications you chose.
+        - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/compute/instances/concepts/#cloud-init). Otherwise, leave these options at their default values.
+          You can configure a cloud-init script to automate instance setup, such as setting up software, users, and system configurations at the first boot.
+        - **Verify the [SSH keys](/console/account/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.
 
         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](/compute/instances/how-to/create-an-instance/), and other information, settings, and actions for the Instance.

diff --git a/compute/instances/quickstart.mdx b/compute/instances/quickstart.mdx
@@ -23,34 +23,33 @@ Scaleway [Instances](/compute/instances/concepts/#instance) are computing units
 
 ## How to create an Instance
 
-1. Click **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**. <br />
-      Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/compute/instances/reference-content/choosing-instance-type/).
-    - Choose an **Image** to run on your Instance. <br />
-      This can be an operating system, an InstantApp, or a custom image. [Check all available Linux distributions and InstantApps](/compute/instances/reference-content/images-and-instantapps/).
-    - Add **Volumes**, which are storage spaces used by your Instances.
-      - For **GP1 Instances** you can leave the default settings of maximum local storage, or choose how much [local](/compute/instances/concepts/#local-volumes) and/or [block](/compute/instances/concepts/#block-volumes) storage you want. Your **system volume** is the volume on which your Instance will boot. The system volume can be either a local or a block volume.
-      - **PLAY2**, **PRO2**, and **Enterprise** Instances boot directly [on block volumes](/compute/instances/concepts/#boot-on-block). You can add several block volumes and define how much storage you want for each.
-      <Message type="important">
-          - Ensure that a volume with an OS image has a minimum capacity of 10 GB. For a GPU OS, the recommended size is 125 GB.
-          - The minimum volume size for Microsoft Windows OS is 25 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. Once the Instance is created can [modify your boot volume](/compute/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.
-      </Message>
-    - Configure the network of the Instance. You can either select to use **Routed public IP** (a dedicated public IP address routed to your Instance that allows direct communication between the Instance and the Internet) or a **NAT public IP** (a public IP address that uses a carrier-grade NAT to translate the Instances NAT IP address). If you are unsure which to use, we recommend a routed public IP for ease of use and improved performance.
-      - 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 IPv46. Alternatively, uncheck the box if you do not want an IPv4.
-        <Message type="tip">
-          You can attach up to 5 IPs to an Instance, combining IPv4 and IPv6 addresses.
-        </Message>
-    - Enter a **Name** for your Instance, or leave the randomly-generated name in place. Optionally, you can add [tags](/compute/instances/concepts/#tags) to help you organize your Instance.
-    - Click **Advanced options** if you want to configure a [cloud-init configuration](/compute/instances/concepts/#cloud-init). Otherwise, leave these options at their default values.
-    - Verify the [SSH keys](/console/account/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.
+    1. Click **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**. <br />
+          Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/compute/instances/reference-content/choosing-instance-type/).
+        - ***Choose an Image** to run on your Instance. <br />
+          This can be an operating system, an InstantApp, or a custom image. [Check all available Linux distributions and InstantApps](/compute/instances/reference-content/images-and-instantapps/).
+        - **Name** your Instance, or leave the randomly-generated name in place. Optionally, you can add [tags](/compute/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 up to 16 local and/or block type volumes as needed.
+          <Message type="important">
+             - 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. Once the Instance is created can [modify your boot volume](/compute/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.
+          </Message>
+        - **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.
+            <Message type="tip">
+              You can attach up to 5 IPs to an Instance, combining IPv4 and IPv6 addresses, which is useful for running different services or applications on the same Instance.
+            </Message>
+        - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/compute/instances/concepts/#cloud-init). Otherwise, leave these options at their default values.
+          You can configure a cloud-init script to automate instance setup, such as setting up software, users, and system configurations at the first boot.
+        - **Verify the [SSH keys](/console/account/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