docs(instance): add instance groups

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                                                               |

pages/instances/concepts.mdx

@@ -65,6 +65,17 @@ 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.<br/>
+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.<br/>
+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).<br/>
+[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.

pages/instances/how-to/create-manage-instance-groups.mdx

@@ -0,0 +1,177 @@
+---
+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.<br/>
+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.
+
+<Message type="important">
+  Instance groups are currently in [Public Beta](https://www.scaleway.com/en/betas/). Feature and interface may change.
+</Message>
+
+<Requirements />
+
+- 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`.<br/>
+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 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:
+    - Click the **Groups** tab, then click **Create Instance group**.
+    - Click the **Templates** tab, click <Icon name="more" /> 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**.
+
+    <Message type="tip">
+      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**.
+    </Message>
+
+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.
+
+    <Message type="note">
+      Only CPU-only Instance templates are available for Instance groups in the console. GPU template support is available via the API or CLI only.
+    </Message>
+
+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 **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.
+
+#### 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.
+
+    <Message type="note">
+      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.
+    </Message>
+
+    Click **Add metric** to monitor an additional metric, or click <Icon name="delete" /> 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 **Settings** tab of the group, enable **Use Load Balancer for traffic routing**.
+2. Select an existing **Load Balancer**.<br/>
+    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.<br/>
+    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.<br/>
+    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.
+
+<Message type="tip">
+  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/).
+</Message>
+
+### 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 <Icon name="more" /> 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**.<br/>
+
+    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
+
+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
+
+<Message type="important">
+  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.
+</Message>
+
+### Delete a single Instance group
+
+1. Click the **Groups** tab of the [Instances dashboard](https://console.scaleway.com/instance/servers).
+2. Click <Icon name="more" /> next to the Instance group you want to delete, then click **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
+
+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 <Icon name="delete" />.
+4. Type **DELETE** to confirm, then click **Delete Instance groups**.

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

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',