---
title: "ezgh compute autoscaling-groups set-launch-spec"
description: "Change what an autoscaling group launches, and roll it out to the members."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.ezghcloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ezgh compute autoscaling-groups set-launch-spec

{/* Generated by ezgh-cli's internal/tools/clidocs from the ezgh command tree. Don't edit: change the command's help in ezgh-cli and regenerate. */}

```sh
ezgh compute autoscaling-groups set-launch-spec <group> [launch flags] [flags]
```

Change the launch spec: each flag given changes its own field of the current spec, as `ezgh compute autoscaling-groups get` shows it, and everything else stays. `--instance-type`, `--image` and `--bot` set their field; `--ssh-key`, `--tag` and `--new-volume` replace the whole list; `--root-size`, `--root-volume-type`, `--root-iops` and `--root-throughput` each set only their part of the root volume; `--ipv4`, `--no-ipv4`, `--ipv6`, `--no-ipv6`, `--primary-subnet`, `--firewall` and `--no-firewalls` each set only their part of the first network interface; `--subnet` replaces the interfaces after the first. The group then replaces its members with the new spec, `--batch-percent` of the group at a time (`ezgh compute autoscaling-groups update` sets it; `cancel-release` stops a release). User data stays as it is unless `--user-data` replaces it or `--no-user-data` clears it. An image alias is resolved again when the spec is written. The change is conditional on the spec being as it was read; if someone else changed it, the command fails and nothing is written. It is refused while the group is still being created, and a new spec takes over a release in progress.

It prints the operation, which ends when the whole release ends; `--wait` waits for that (each batch waits for its warmup, so raise `--wait-timeout` for a large group) and prints the group. Needs compute.autoscalingGroups.update.

Part of [`ezgh compute autoscaling-groups`](/cli/reference/compute-autoscaling-groups).

## Examples

```sh
ezgh compute autoscaling-groups set-launch-spec web --instance-type gp-1.xlarge
```

## Flags

| Flag | Type | Default | Description |
| --- | --- | --- | --- |
| `--bot` | string |  | attach a Bot (bot\_…): code on the instance gets short-lived credentials for it |
| `--firewall` | string, repeatable |  | a firewall for the new interface (ID, UUID or name), in place of the project's default (repeat) |
| `--image` | string |  | the image alias, such as linux/ubuntu:26.04, or an exact image ID (img\_…) |
| `--instance-type` | string |  | the instance type, such as gp-1.large (required); ezgh compute instance-types list shows the organization's |
| `--ipv4` | boolean |  | give the new interface a public IPv4 address |
| `--ipv6` | boolean |  | with `--primary-subnet`: give it a public IPv6 /64 |
| `--new-volume` | string, repeatable |  | create and attach a volume: &lt;GiB&gt;\[:&lt;volume type&gt;\] (repeat) |
| `--no-firewalls` | boolean |  | no firewall on the new interface |
| `--no-ipv4` | boolean |  | with `--primary-subnet`: no public IPv4 address, whatever the subnet's auto-assign |
| `--no-ipv6` | boolean |  | with `--primary-subnet`: no public IPv6 /64, whatever the subnet's auto-assign |
| `--no-user-data` | boolean |  | clear the group's user data |
| `--primary-subnet` | string |  | make the new interface private, in this VPC subnet (ID, UUID or name) |
| `--root-iops` | int |  | the root volume's provisioned IOPS, for types that take it |
| `--root-size` | int |  | the root volume's size in GiB (default: the image's minimum) |
| `--root-throughput` | int |  | the root volume's provisioned throughput in MB/s, for types that take it |
| `--root-volume-type` | string |  | the root volume's type (default: the block store's default) |
| `--ssh-key` | string, repeatable |  | an SSH key of the project to install, by ID, UUID or name (repeat, at most 10) |
| `--subnet` | string, repeatable |  | add a new private interface in this VPC subnet (ID, UUID or name), after the primary (repeat) |
| `--tag` | string, repeatable |  | a tag, key=value (repeat) |
| `--user-data` | string |  | a file of user-data (cloud-init), - for stdin, at most 16 KiB |
| `--wait` | boolean |  | wait until the release finishes, and print the group then (see `--wait-timeout`) |
| `--wait-timeout` | duration | `10m0s` | how long `--wait` waits |

This command also takes the [global flags](/cli/reference#global-flags).

Source: https://docs.ezghcloud.com/cli/reference/compute-autoscaling-groups-set-launch-spec/index.mdx
