From e7227d7d054c31150cef596110374e245376d375 Mon Sep 17 00:00:00 2001 From: Firdevs ARSLAN Date: Wed, 12 Aug 2026 11:57:30 +0200 Subject: [PATCH 1/6] docs(instance): add instance groups --- .../how-to/create-manage-instance-groups.mdx | 179 ++++++++++++++++++ 1 file changed, 179 insertions(+) create mode 100644 pages/instances/how-to/create-manage-instance-groups.mdx diff --git a/pages/instances/how-to/create-manage-instance-groups.mdx b/pages/instances/how-to/create-manage-instance-groups.mdx new file mode 100644 index 0000000000..70478cc573 --- /dev/null +++ b/pages/instances/how-to/create-manage-instance-groups.mdx @@ -0,0 +1,179 @@ +--- +title: Create and manage Instance groups +description: This page explains how to create and manage Instance groups for Scaleway Instances. +tags: instance group autoscaling +dates: + validation: 2026-08-12 + posted: 2026-08-12 +--- +import Requirements from '@macros/iam/requirements.mdx' + +An [Instance group](/instances/concepts/#instance-group) is a collection of identical Instances, created from an [Instance template](/instances/concepts/#instance-template) and managed together. A group can run at a fixed size for predictable workloads, or scale automatically between a minimum and maximum number of Instances based on CPU or RAM usage. When you attach a Load Balancer to a group, Scaleway keeps its backend up to date as the group scales, and can automatically replace Instances that fail their health check. + + + Instance groups are currently in [Public Beta](https://www.scaleway.com/en/betas/). Feature and interface may change. + + + + +- A Scaleway account logged in to the [console](https://console.scaleway.com) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance template](/instances/how-to/create-manage-instance-templates/) with a CPU-only configuration + +## Understand Instance group permissions + +Instance group actions rely on the same [permission sets](/iam/reference-content/permission-sets/) as standalone Instances: `InstancesReadOnly` and `InstancesFullAccess`. Attaching or editing a Load Balancer or Private Network for a group also requires the corresponding `LoadBalancersFullAccess` and/or `PrivateNetworksFullAccess` permission sets. + +With `InstancesReadOnly`, you can: + +- View the list of Instance groups, and open a group's **Overview**, **Instances**, **Logs**, and **Settings** tabs. +- Filter and sort the Instance groups list. +- Copy IDs and other information displayed on a group's pages. +- Close banners and alerts. +- Switch between Availability Zones or Regions. + +With `InstancesReadOnly` alone, you cannot: + +- Open the Instance group creation wizard or the **Edit settings** form. +- Create an Instance group or an Instance template. +- Edit an Instance group's settings, or delete an Instance group or one of its Instances. + +To perform these actions, you need the `InstancesFullAccess` permission set, or broader access such as [Owner](/iam/concepts/#owner) status. + +## Create an Instance group + +You can start the Instance group creation wizard from 3 places in the console: the **Groups** tab, the **Templates** tab, or an Instance template's Overview page. + +1. In the **Compute** section of the side menu, click **CPU & GPU Instances**. The [Instances dashboard](https://console.scaleway.com/instance/servers) opens. +2. Open the creation wizard using one of the following methods: + - Click the **Groups** tab, then click **Create Instance group**. + - Click the **Templates** tab, click next to the template you want to use, then click **Create Instance group**. + - Click the **Templates** tab, click the name of the template you want to use, then in the **Instance groups** section of its Overview page, click **Create Instance group**. + + + You can also reach this wizard right after creating a new Instance template: in the confirmation dialog, click **Create Instance group** instead of **Skip for now**. + + +3. Enter a **name** for your Instance group, or keep the randomly-generated name. Optionally, add [tags](/instances/concepts/#tags). +4. Select the **Availability Zone** and the **Instance template** to use. Every Instance in the group is created from this template. + + + Only CPU-only Instance templates are available for Instance groups in the console. GPU template support is available via the API or CLI only. + + +5. Under **Choose capacity management**, select whether the group runs at a **fixed size** or uses **autoscaling**, and configure the corresponding settings. See [Choose capacity management](#choose-capacity-management) for details. +6. (Optional) Enable **Use Load Balancer for traffic routing** to register the Instances of the group as backend servers and enable autohealing. See [Configure a Load Balancer for traffic routing and autohealing](#configure-a-load-balancer-for-traffic-routing-and-autohealing) for details. +7. Check the **environment footprint details** and the **estimated cost** of your Instance group. +8. Read and accept the Scaleway terms and conditions, then click **Create Instance group**. + +Your Instance group is created, and you are taken to its **Overview** tab, where its Instances begin provisioning. + +### Choose capacity management + +An Instance group runs in one of two capacity modes: fixed size, or autoscaling. You choose the mode when you create the group, and can switch between modes later from the group's **Settings** tab. + +#### Fixed size + +A fixed-size group always runs the same number of Instances, and is best suited to predictable workloads. + +**Number of Instances**: set how many Instances the group runs. You can set between 1 and 50 Instances. + +#### Autoscaling + +An autoscaling group dynamically adjusts its Instance count between a minimum and maximum value, based on the usage thresholds you define. This mode is best suited to unpredictable workloads. + +- **Minimum Instance count** and **Maximum Instance count**: set the range the group can scale between (from 1 to 50 Instances). +- **Scaling thresholds**: for each metric, set a target usage percentage. The group scales up when usage exceeds the target, and scales down when it drops below it. + + + CPU usage and RAM usage are the metrics currently supported in the console. When you set several metrics, the group scales to the maximum Instance count required by any of them. + + + Click **Add metric** to monitor an additional metric, or click next to a metric to remove it. + +- **Cooldown period**: set the minimum wait time between scaling events. This gives new Instances time to start and stabilize before further scaling changes occur, so set it long enough to ensure they are ready to serve traffic. + +### Configure a Load Balancer for traffic routing and autohealing + +Attaching a Load Balancer to an Instance group lets Scaleway automatically register the Instances of the group as backend servers, and route traffic to them as the group scales. + +1. In the Instance group creation wizard, or from the group's **Settings** tab, enable **Use Load Balancer for traffic routing**. +2. Select an existing **Load Balancer**.
+ Only Load Balancers in the same Availability Zone as your Instance group are available for selection. Make sure the Load Balancer you select has enough capacity and quota for your group's Instances.
+ Creating a Load Balancer from the Instance group flow is not supported. [Create a Load Balancer](/load-balancer/how-to/create-load-balancer/) beforehand if you do not have one yet. +3. For each backend, select the **network** and **IP type** to use to route traffic to your Instances. +4. (Optional) Enable **Autohealing**. If a backend server fails its health check, the Instance group automatically replaces it.
+ Autohealing requires a Load Balancer. You cannot enable autohealing on an Instance group that does not have a Load Balancer configured for traffic routing. + + + While a Load Balancer or one of its backends is in use by an Instance group, the **Delete** action is disabled on the Load Balancer pages. Attach a different Load Balancer to the group before you can delete the one currently in use. + + +## Manage an Instance group + +Each Instance group has four tabs: **Overview**, **Instances**, **Logs**, and **Settings**. + +### View Instance group information + +The **Overview** tab of an Instance group shows its status (**Stable**, **Scaling up**, **Scaling down**, or an error status), its Instance group ID, creation date, and Availability Zone, along with the following: + +- **Instance template** used to create the group, and its ID. +- **Capacity management** mode, group capacity, scaling thresholds, and cooldown period. +- **Public Network** and **Private Network** information, inherited from the Instance template. +- **Placement group**, if the Instance template includes one. +- **Tags** you assigned to the group. + +The placement group and tags inherited from the Instance template cannot be changed from an Instance group. Create a new Instance template with the settings you need, and use it to create a new Instance group. + + + If your group displays an error status, such as **Insufficient capacity** or **Insufficient Instance quota**, see [Fix common Instance group errors](/instances/troubleshooting/fix-common-instance-group-errors/). + + +### View and manage the Instances in a group + +1. Click the **Instances** tab of your Instance group. + For an autoscaling group, an **Autoscaling status** card displays the current, minimum, and maximum Instance count, along with the scaling status of the group. +2. Review the list of Instances belonging to the group. +3. Click next to an Instance to: + - Click **More info** to open the Instance details. + - Click **Reboot** to restart the Instance. Confirm by clicking **Reboot Instance** in the dialog box that appears. + - Click **Delete** to remove the Instance from the group. Optionally, select **Delete associated IPs** and/or **Delete Block Storage volumes**, type **DELETE** to confirm, then click **Delete Instance**. + + + Deleting an Instance is permanent and cannot be undone. If autohealing is enabled, the Instance group may automatically create a replacement Instance to maintain its configured capacity. + + +### View Instance group logs + +The **Logs** tab of an Instance group gives you access to Scaleway Observability's Cockpit, which ingests the metrics and logs of the group. + +- Click **Open Grafana logs dashboard** to view and monitor your Instance group logs in a Grafana-managed dashboard. +- Click **Manage custom data with tokens** to create a token and send data from other sources than Scaleway to the same Cockpit. + +### Edit Instance group settings + +1. Click the **Settings** tab of your Instance group. +2. Review the current **Capacity management** and **Traffic routing & autohealing** configuration. +3. Click **Edit settings**. +4. Update the minimum and maximum Instance count, scaling thresholds, cooldown period, and/or Load Balancer and autohealing configuration as needed. +5. Click **Save settings** to confirm your changes. + +## Delete an Instance group + + + Deleting an Instance group does not delete its associated resources. Instances, IPs, volumes, and Load Balancers remain active and continue to be billed. To delete them, scale the group down to zero Instances (or set the fixed size to zero), then remove the remaining resources manually. + + +### Delete a single Instance group + +1. Click the **Groups** tab of the [Instances dashboard](https://console.scaleway.com/instance/servers). +2. Click next to the Instance group you want to delete, then click **Delete**. + Alternatively, from the group's **Overview** or **Settings** tab, click **Actions** > **Delete**. +3. Type **DELETE** to confirm, then click **Delete Instance group**. + +### Delete several Instance groups at once + +1. Click the **Groups** tab of the [Instances dashboard](https://console.scaleway.com/instance/servers). +2. Select the Instance groups you want to delete. +3. In the selection toolbar that appears, click . +4. Type **DELETE** to confirm, then click **Delete Instance groups**. \ No newline at end of file From 51f7e66ed8bc835bed04a5a99e099f62cf4ac967 Mon Sep 17 00:00:00 2001 From: Firdevs ARSLAN Date: Wed, 12 Aug 2026 11:59:50 +0200 Subject: [PATCH 2/6] fixed syntax --- pages/instances/how-to/create-manage-instance-groups.mdx | 6 +++--- pages/instances/how-to/create-manage-instance-templates.mdx | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/pages/instances/how-to/create-manage-instance-groups.mdx b/pages/instances/how-to/create-manage-instance-groups.mdx index 70478cc573..9334729bfb 100644 --- a/pages/instances/how-to/create-manage-instance-groups.mdx +++ b/pages/instances/how-to/create-manage-instance-groups.mdx @@ -98,11 +98,11 @@ An autoscaling group dynamically adjusts its Instance count between a minimum an Attaching a Load Balancer to an Instance group lets Scaleway automatically register the Instances of the group as backend servers, and route traffic to them as the group scales. 1. In the Instance group creation wizard, or from the group's **Settings** tab, enable **Use Load Balancer for traffic routing**. -2. Select an existing **Load Balancer**.
- Only Load Balancers in the same Availability Zone as your Instance group are available for selection. Make sure the Load Balancer you select has enough capacity and quota for your group's Instances.
+2. Select an existing **Load Balancer**.
+ Only Load Balancers in the same Availability Zone as your Instance group are available for selection. Make sure the Load Balancer you select has enough capacity and quota for your group's Instances.
Creating a Load Balancer from the Instance group flow is not supported. [Create a Load Balancer](/load-balancer/how-to/create-load-balancer/) beforehand if you do not have one yet. 3. For each backend, select the **network** and **IP type** to use to route traffic to your Instances. -4. (Optional) Enable **Autohealing**. If a backend server fails its health check, the Instance group automatically replaces it.
+4. (Optional) Enable **Autohealing**. If a backend server fails its health check, the Instance group automatically replaces it.
Autohealing requires a Load Balancer. You cannot enable autohealing on an Instance group that does not have a Load Balancer configured for traffic routing. diff --git a/pages/instances/how-to/create-manage-instance-templates.mdx b/pages/instances/how-to/create-manage-instance-templates.mdx index e42b5d8d16..8dcd75342a 100644 --- a/pages/instances/how-to/create-manage-instance-templates.mdx +++ b/pages/instances/how-to/create-manage-instance-templates.mdx @@ -1,7 +1,7 @@ --- title: Create and manage Instance templates description: This page explains how to create and manage Instance templates -tags: instance template create delete +tags: instance template dates: validation: 2025-07-09 posted: 2021-07-09 From b990e1d3a3fa246f5f516726e9e35e5681fb7e37 Mon Sep 17 00:00:00 2001 From: Firdevs ARSLAN Date: Wed, 12 Aug 2026 14:40:54 +0200 Subject: [PATCH 3/6] added concept and troubleshooting --- pages/instances/concepts.mdx | 10 ++ pages/instances/menu.ts | 4 + .../fix-common-instance-group-errors.mdx | 109 ++++++++++++++++++ pages/instances/troubleshooting/index.mdx | 1 + 4 files changed, 124 insertions(+) create mode 100644 pages/instances/troubleshooting/fix-common-instance-group-errors.mdx diff --git a/pages/instances/concepts.mdx b/pages/instances/concepts.mdx index dd6f5a93ad..d6f00a6d36 100644 --- a/pages/instances/concepts.mdx +++ b/pages/instances/concepts.mdx @@ -65,6 +65,16 @@ An image is a complete backup of your Instance. One image contains all the [volu An Instance is a virtual computing unit that offers resources for running applications. It functions as a self-contained entity with its own operating system, RAM, and storage. Each type of Instance has unique specifications. You can choose the type that best meets your requirements. Refer to our [Instance types documentation](/instances/reference-content/choosing-instance-type/) for further details on the various Scaleway Instance options. +## Instance group + +An Instance group is a collection of identical Instances, created from the same [Instance template](#instance-template) and managed together as a single resource. A group can run at a fixed size for predictable workloads, or scale automatically between a minimum and maximum Instance count based on CPU or RAM usage.
+When you attach a Load Balancer to a group, Scaleway keeps its backend up to date as the group scales, and can automatically replace Instances that fail their health check. [Learn how to create and manage Instance groups](/instances/how-to/create-manage-instance-groups/). + +## Instance template + +An Instance template saves a predefined, immutable server configuration — Instance type, boot image, network and security settings, tags, and cloud-init — so you can deploy consistent Instances repeatedly without re-entering the same parameters each time.
+You cannot edit a template once it is created; create a new template if you need to change its configuration. Instance templates are used to deploy standalone Instances, or to create [Instance groups](#instance-group). [Learn how to create and manage Instance templates](/instances/how-to/create-manage-instance-templates/). + ## InstantApp An InstantApp is an image with a preinstalled application. By choosing an InstantApp when prompted to select an image during the [creation of your Instance](/instances/how-to/create-an-instance/), you choose to install the specified application on your Instance. You can then start using the application immediately. diff --git a/pages/instances/menu.ts b/pages/instances/menu.ts index 0b9ceb2a8c..7ce5c741bc 100644 --- a/pages/instances/menu.ts +++ b/pages/instances/menu.ts @@ -26,6 +26,10 @@ export const instancesMenu = { label: 'Create and manage Instance templates', slug: 'create-manage-instance-templates', }, + { + label: 'Create and manage Instance groups', + slug: 'create-manage-instance-groups', + }, { label: 'Manage Instance storage', slug: 'manage-storage', diff --git a/pages/instances/troubleshooting/fix-common-instance-group-errors.mdx b/pages/instances/troubleshooting/fix-common-instance-group-errors.mdx new file mode 100644 index 0000000000..dea45bdd25 --- /dev/null +++ b/pages/instances/troubleshooting/fix-common-instance-group-errors.mdx @@ -0,0 +1,109 @@ +--- +title: Fix common Instance group errors +description: This page helps you understand and resolve the error states you may encounter with Scaleway Instance groups. +tags: instance-group autoscaling load-balancer quota error troubleshooting +dates: + validation: 2026-08-12 + posted: 2026-08-12 +--- + +This page helps you understand and resolve the error states an [Instance group](/instances/concepts/#instance-group) can display on the [Instances dashboard](https://console.scaleway.com/instance/servers) and on the group **Overview** tab. + +## Instance type is out of stock + +### Symptoms + +- The Instances dashboard displays the banner **Instance type temporarily unavailable**. +- An Instance group displays the **Insufficient capacity** status. +- The **Overview** tab of the group displays the banner **The Instance type used by this group's template is currently out of stock**. + +### Cause + +The Instance type defined in the [Instance template](/instances/concepts/#instance-template) of the group is out of stock in the Availability Zone of the group. The group cannot provision new Instances, and cannot scale up, until stock is restored. + +### Solution + +1. [Create a new Instance template](/instances/how-to/create-manage-instance-templates/) using an available Instance type. +2. [Create a new Instance group](/instances/how-to/create-manage-instance-groups/) from this template. + +## Insufficient Instance quota + +### Symptoms + +- The Instances dashboard displays the banner **Instances or groups may fail to create or scale due to insufficient quotas**. +- An Instance group displays the **Insufficient Instance quota** status. + +### Cause + +Your Organization has reached its Instance quota, so the group cannot create or scale the Instances it needs. + +### Solution + +1. [Add and verify a payment method](/account/how-to/verify-identity/), and verify your identity document, to increase your quotas. +2. Alternatively, click **Check quotas** in the banner to review your current [Organization quotas](/organizations-and-projects/how-to/manage-quotas/). +3. If you have already completed these steps, click **Open support ticket** to contact Scaleway Support. + +## Instance limit reached due to Load Balancer capacity + +### Symptoms + +- The Instances dashboard displays the banner **Instances limit reached**. +- The group's **Overview** tab displays the banner **Instance limit reached**, stating that the Load Balancer attached to the group limits how many Instances can run. + +### Cause + +The [Load Balancer](/load-balancer/concepts/#load-balancer) attached to the group for traffic routing does not have enough backend capacity for the group to reach its configured maximum Instance count. + +### Solution + +- Click **Edit Load Balancer** in the banner to [resize the Load Balancer](/load-balancer/how-to/resize-lb/) to a larger size. +- Alternatively, remove some existing Instances from the group to free up capacity on the Load Balancer. + +## Several errors occur at the same time + +### Symptoms + +The Instances dashboard and the **Overview** tab of the groupdisplay a generic banner, **Unable to scale or deploy resources**, mentioning unavailable Instance types, quota restrictions, and Load Balancer capacity limits together. + +### Cause + +More than one of the issues described above (out-of-stock Instance type, insufficient quota, Load Balancer capacity) affects the group at the same time. Rather than stacking several banners, the console displays a single, generic message. + +### Solution + +Check each potential cause individually: + +- Review whether the Instance type used by the group's template is [out of stock](#instance-type-is-out-of-stock). +- Review whether your Organization has [insufficient quota](#insufficient-instance-quota). +- Review whether the attached [Load Balancer has reached its capacity](#instance-limit-reached-due-to-load-balancer-capacity). + +If the group still fails to scale or deploy after checking these points, click **Open support ticket** to contact Scaleway Support. + +## Load Balancer is unavailable or has been deleted + +### Symptoms + +- The Instances dashboard displays the banner **Associated Load Balancers unavailable**. +- The group's **Overview** tab displays the banner **Load Balancer unavailable**, stating that traffic routing and health checks may be affected. + +### Cause + +The Load Balancer associated with the Instance group cannot be found. This can happen if the Load Balancer, or one of the backends it uses to route traffic to the group, was deleted outside the Instance group flow (for example, via the API or CLI). + + + From the **Load Balancers** pages of the console, the **Delete** action is disabled for a Load Balancer or a backend currently in use by an Instance group, to help prevent this situation. + + +### Solution + +1. Click **Check Load Balancer configuration** in the banner, or go to the group's **Settings** tab. +2. Click **Edit settings**. +3. Select an existing Load Balancer, or create a new one, then save your changes. + +## Going further + +If an issue persists after following the steps above, provide the following information when creating a support ticket: + +- The Instance group ID and Instance template ID. +- The Availability Zone of the group. +- The exact error message and status displayed on the Overview tab of the group. \ No newline at end of file diff --git a/pages/instances/troubleshooting/index.mdx b/pages/instances/troubleshooting/index.mdx index 77248f8d87..ba77ce77f6 100644 --- a/pages/instances/troubleshooting/index.mdx +++ b/pages/instances/troubleshooting/index.mdx @@ -64,6 +64,7 @@ productIcon: InstanceProductIcon - [Fix broken VPN when switching OpenVPN Instance to routed IP](/instances/troubleshooting/fix-broken-vpn-when-switching-openvpn-vm-to-routed-ip) - [Fix the wrong user configuration of cloud-init on Debian 12 (Bookworm)](/instances/troubleshooting/fix-cloud-init-debian12) - [Fix common issues with Scaleway Instances](/instances/troubleshooting/fix-common-issues) + - [Fix common Instance group errors](/instances/troubleshooting/fix-common-instance-group-errors) - [Fixing DNS resolution with a routed IPv6-only setup on Debian Bullseye](/instances/troubleshooting/fix-dns-routed-ipv6-only-debian-bullseye) - [Fix error when fetching SSH keys on Windows Server 2022](/instances/troubleshooting/fix-error-message-in-scw-fetch-ssh-keys) - [Fix long delays when booting without a public IP](/instances/troubleshooting/fix-long-delays-booting-without-public-ip) From 53c76e7d5adcfc3f6949ecfac9c1cdc4d97bf5b8 Mon Sep 17 00:00:00 2001 From: Firdevs ARSLAN Date: Wed, 12 Aug 2026 14:44:14 +0200 Subject: [PATCH 4/6] updated permission sets --- pages/iam/reference-content/permission-sets.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/iam/reference-content/permission-sets.mdx b/pages/iam/reference-content/permission-sets.mdx index e82993c868..765f61602c 100644 --- a/pages/iam/reference-content/permission-sets.mdx +++ b/pages/iam/reference-content/permission-sets.mdx @@ -61,8 +61,8 @@ Below is a list of the permission sets available at Scaleway. | Permission set | Description | | :--------------------------: | :-----------------------------------------------------------------------------------: | -| InstancesFullAccess | Full access to create, read, list, edit and delete Instances | -| InstancesReadOnly | List and read access to Instances | +| InstancesFullAccess | Full access to create, read, list, edit and delete Instances, Instance templates, and Instance groups | +| InstancesReadOnly | List and read access to Instances, Instance templates, and Instance groups | | InstancesServerStart | Allows starting Instance servers | | InstancesServerStop | Allows stopping Instance servers | | SSHKeysReadOnly | Read access to SSH keys | From 9fdb70e993871f282aa3c0335a9a6d8b11b84883 Mon Sep 17 00:00:00 2001 From: Firdevs ARSLAN Date: Wed, 12 Aug 2026 15:12:04 +0200 Subject: [PATCH 5/6] corrections --- pages/instances/concepts.mdx | 3 +- .../how-to/create-manage-instance-groups.mdx | 34 +++++++++---------- 2 files changed, 19 insertions(+), 18 deletions(-) diff --git a/pages/instances/concepts.mdx b/pages/instances/concepts.mdx index d6f00a6d36..0af1ce4a7a 100644 --- a/pages/instances/concepts.mdx +++ b/pages/instances/concepts.mdx @@ -73,7 +73,8 @@ When you attach a Load Balancer to a group, Scaleway keeps its backend up to dat ## Instance template An Instance template saves a predefined, immutable server configuration — Instance type, boot image, network and security settings, tags, and cloud-init — so you can deploy consistent Instances repeatedly without re-entering the same parameters each time.
-You cannot edit a template once it is created; create a new template if you need to change its configuration. Instance templates are used to deploy standalone Instances, or to create [Instance groups](#instance-group). [Learn how to create and manage Instance templates](/instances/how-to/create-manage-instance-templates/). +You cannot edit a template once it is created; create a new template if you need to change its configuration. Instance templates are used to deploy standalone Instances, or to create [Instance groups](#instance-group).
+[Learn how to create and manage Instance templates](/instances/how-to/create-manage-instance-templates/). ## InstantApp diff --git a/pages/instances/how-to/create-manage-instance-groups.mdx b/pages/instances/how-to/create-manage-instance-groups.mdx index 9334729bfb..cef250103f 100644 --- a/pages/instances/how-to/create-manage-instance-groups.mdx +++ b/pages/instances/how-to/create-manage-instance-groups.mdx @@ -8,7 +8,8 @@ dates: --- import Requirements from '@macros/iam/requirements.mdx' -An [Instance group](/instances/concepts/#instance-group) is a collection of identical Instances, created from an [Instance template](/instances/concepts/#instance-template) and managed together. A group can run at a fixed size for predictable workloads, or scale automatically between a minimum and maximum number of Instances based on CPU or RAM usage. When you attach a Load Balancer to a group, Scaleway keeps its backend up to date as the group scales, and can automatically replace Instances that fail their health check. +An [Instance group](/instances/concepts/#instance-group) is a collection of identical Instances, created from an [Instance template](/instances/concepts/#instance-template) and managed together. A group can run at a fixed size for predictable workloads, or scale automatically between a minimum and maximum number of Instances based on CPU or RAM usage.
+When you attach a Load Balancer to a group, Scaleway keeps its backend up to date as the group scales, and can automatically replace Instances that fail their health check. Instance groups are currently in [Public Beta](https://www.scaleway.com/en/betas/). Feature and interface may change. @@ -22,7 +23,8 @@ An [Instance group](/instances/concepts/#instance-group) is a collection of iden ## Understand Instance group permissions -Instance group actions rely on the same [permission sets](/iam/reference-content/permission-sets/) as standalone Instances: `InstancesReadOnly` and `InstancesFullAccess`. Attaching or editing a Load Balancer or Private Network for a group also requires the corresponding `LoadBalancersFullAccess` and/or `PrivateNetworksFullAccess` permission sets. +Instance group actions rely on the same [permission sets](/iam/reference-content/permission-sets/) as standalone Instances: `InstancesReadOnly` and `InstancesFullAccess`.
+Attaching or editing a Load Balancer or Private Network for a group also requires the corresponding `LoadBalancersFullAccess` and/or `PrivateNetworksFullAccess` permission sets. With `InstancesReadOnly`, you can: @@ -42,7 +44,7 @@ To perform these actions, you need the `InstancesFullAccess` permission set, or ## Create an Instance group -You can start the Instance group creation wizard from 3 places in the console: the **Groups** tab, the **Templates** tab, or an Instance template's Overview page. +You can start the Instance group creation wizard from 3 places in the console: the **Groups** tab, the **Templates** tab, or the Overview page of an Instance template. 1. In the **Compute** section of the side menu, click **CPU & GPU Instances**. The [Instances dashboard](https://console.scaleway.com/instance/servers) opens. 2. Open the creation wizard using one of the following methods: @@ -51,7 +53,7 @@ You can start the Instance group creation wizard from 3 places in the console: t - Click the **Templates** tab, click the name of the template you want to use, then in the **Instance groups** section of its Overview page, click **Create Instance group**. - You can also reach this wizard right after creating a new Instance template: in the confirmation dialog, click **Create Instance group** instead of **Skip for now**. + You can also reach this wizard right after creating a new Instance template: in the dialog box, click **Create Instance group** instead of **Skip for now**. 3. Enter a **name** for your Instance group, or keep the randomly-generated name. Optionally, add [tags](/instances/concepts/#tags). @@ -61,22 +63,22 @@ You can start the Instance group creation wizard from 3 places in the console: t Only CPU-only Instance templates are available for Instance groups in the console. GPU template support is available via the API or CLI only. -5. Under **Choose capacity management**, select whether the group runs at a **fixed size** or uses **autoscaling**, and configure the corresponding settings. See [Choose capacity management](#choose-capacity-management) for details. +5. Under **Choose capacity management**, select whether the group runs at a fixed size or uses autoscaling, and configure the corresponding settings. See [Choose capacity management](#choose-capacity-management) for details. 6. (Optional) Enable **Use Load Balancer for traffic routing** to register the Instances of the group as backend servers and enable autohealing. See [Configure a Load Balancer for traffic routing and autohealing](#configure-a-load-balancer-for-traffic-routing-and-autohealing) for details. -7. Check the **environment footprint details** and the **estimated cost** of your Instance group. +7. Check the **Environment footprint details** and the estimated cost of your Instance group. 8. Read and accept the Scaleway terms and conditions, then click **Create Instance group**. Your Instance group is created, and you are taken to its **Overview** tab, where its Instances begin provisioning. ### Choose capacity management -An Instance group runs in one of two capacity modes: fixed size, or autoscaling. You choose the mode when you create the group, and can switch between modes later from the group's **Settings** tab. +An Instance group runs in one of two capacity modes: fixed size, or autoscaling. You choose the mode when you create the group, and can switch between modes later from the **Settings** tab of the group. #### Fixed size A fixed-size group always runs the same number of Instances, and is best suited to predictable workloads. -**Number of Instances**: set how many Instances the group runs. You can set between 1 and 50 Instances. +- **Number of Instances**: set how many Instances the group runs. You can set between 1 and 50 Instances. #### Autoscaling @@ -97,17 +99,15 @@ An autoscaling group dynamically adjusts its Instance count between a minimum an Attaching a Load Balancer to an Instance group lets Scaleway automatically register the Instances of the group as backend servers, and route traffic to them as the group scales. -1. In the Instance group creation wizard, or from the group's **Settings** tab, enable **Use Load Balancer for traffic routing**. +1. In the Instance group creation wizard, or from the **Settings** tab of the group, enable **Use Load Balancer for traffic routing**. 2. Select an existing **Load Balancer**.
- Only Load Balancers in the same Availability Zone as your Instance group are available for selection. Make sure the Load Balancer you select has enough capacity and quota for your group's Instances.
+ Only Load Balancers in the same Availability Zone as your Instance group are available for selection. Make sure the Load Balancer you select has enough capacity and quota for the Instances of your group.
Creating a Load Balancer from the Instance group flow is not supported. [Create a Load Balancer](/load-balancer/how-to/create-load-balancer/) beforehand if you do not have one yet. -3. For each backend, select the **network** and **IP type** to use to route traffic to your Instances. +3. For each backend, select the **Network** and **IP type** to use to route traffic to your Instances. 4. (Optional) Enable **Autohealing**. If a backend server fails its health check, the Instance group automatically replaces it.
Autohealing requires a Load Balancer. You cannot enable autohealing on an Instance group that does not have a Load Balancer configured for traffic routing. - - While a Load Balancer or one of its backends is in use by an Instance group, the **Delete** action is disabled on the Load Balancer pages. Attach a different Load Balancer to the group before you can delete the one currently in use. - +While a Load Balancer or one of its backends is in use by an Instance group, the **Delete** action is disabled on the Load Balancer pages. Attach a different Load Balancer to the group before you can delete the one currently in use. ## Manage an Instance group @@ -115,7 +115,7 @@ Each Instance group has four tabs: **Overview**, **Instances**, **Logs**, and ** ### View Instance group information -The **Overview** tab of an Instance group shows its status (**Stable**, **Scaling up**, **Scaling down**, or an error status), its Instance group ID, creation date, and Availability Zone, along with the following: +The **Overview** tab of an Instance group shows its status (Stable, Scaling up, Scaling down, or an error status), its Instance group ID, creation date, and Availability Zone, along with the following: - **Instance template** used to create the group, and its ID. - **Capacity management** mode, group capacity, scaling thresholds, and cooldown period. @@ -132,7 +132,7 @@ The placement group and tags inherited from the Instance template cannot be chan ### View and manage the Instances in a group 1. Click the **Instances** tab of your Instance group. - For an autoscaling group, an **Autoscaling status** card displays the current, minimum, and maximum Instance count, along with the scaling status of the group. + For an autoscaling group, an **Autoscaling status** card displays the current, minimum and maximum Instance count, along with the scaling status of the group. 2. Review the list of Instances belonging to the group. 3. Click next to an Instance to: - Click **More info** to open the Instance details. @@ -168,7 +168,7 @@ The **Logs** tab of an Instance group gives you access to Scaleway Observability 1. Click the **Groups** tab of the [Instances dashboard](https://console.scaleway.com/instance/servers). 2. Click next to the Instance group you want to delete, then click **Delete**. - Alternatively, from the group's **Overview** or **Settings** tab, click **Actions** > **Delete**. + Alternatively, from the **Overview** or **Settings** tab of the group, click **Actions** > **Delete**. 3. Type **DELETE** to confirm, then click **Delete Instance group**. ### Delete several Instance groups at once From 971d04b2a484049a95ba36c22d144bf20c94343b Mon Sep 17 00:00:00 2001 From: Firdevs ARSLAN Date: Thu, 13 Aug 2026 11:58:32 +0200 Subject: [PATCH 6/6] removed note --- pages/instances/how-to/create-manage-instance-groups.mdx | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/pages/instances/how-to/create-manage-instance-groups.mdx b/pages/instances/how-to/create-manage-instance-groups.mdx index cef250103f..da2b9da5cc 100644 --- a/pages/instances/how-to/create-manage-instance-groups.mdx +++ b/pages/instances/how-to/create-manage-instance-groups.mdx @@ -137,11 +137,9 @@ The placement group and tags inherited from the Instance template cannot be chan 3. Click next to an Instance to: - Click **More info** to open the Instance details. - Click **Reboot** to restart the Instance. Confirm by clicking **Reboot Instance** in the dialog box that appears. - - Click **Delete** to remove the Instance from the group. Optionally, select **Delete associated IPs** and/or **Delete Block Storage volumes**, type **DELETE** to confirm, then click **Delete Instance**. + - Click **Delete** to remove the Instance from the group. Optionally, select **Delete associated IPs** and/or **Delete Block Storage volumes**, type **DELETE** to confirm, then click **Delete Instance**.
- - Deleting an Instance is permanent and cannot be undone. If autohealing is enabled, the Instance group may automatically create a replacement Instance to maintain its configured capacity. - + Deleting an Instance is irreversible. If autohealing is enabled, the Instance group may automatically create a replacement Instance to maintain its configured capacity. ### View Instance group logs