> For the complete documentation index, see [llms.txt](https://docs.rumi.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rumi.systems/rumi-cli/commands/cloud/civo/launch-amq.md).

# launch-amq

Launch an ActiveMQ (`rumi-messaging`) message broker node. Requires the bastion to be running.

## Syntax

```bash
rumi cloud civo launch-amq \
  --api-key <token> \
  --region <region> \
  --network <network> \
  --keyPair <keypair> \
  [options]
```

## Options

| Option      | Short | Description                                                   | Default  |
| ----------- | ----- | ------------------------------------------------------------- | -------- |
| `--api-key` | `-k`  | The Civo API token to use (or set `CIVO_API_TOKEN`)           | Required |
| `--region`  | `-r`  | The Civo region in which to create the instance (e.g. `FRA1`) | Required |
| `--network` | `-n`  | Name of the network to launch it into                         | Required |
| `--keyPair` | `-K`  | The network SSH key pair                                      | Required |

## Example

```bash
rumi cloud civo launch-amq \
  --api-key $CIVO_API_TOKEN \
  --region FRA1 \
  --network my-cloud \
  --keyPair rumi
```

## Notes

* Software installs at boot via cloud-init, so the first boot takes longer than a prebaked-image provider.
* The bastion must be launched first.

## See Also

* [start-amq](/rumi-cli/commands/cloud/civo/start-amq.md)
* [stop-amq](/rumi-cli/commands/cloud/civo/stop-amq.md)
* [terminate-amq](/rumi-cli/commands/cloud/civo/terminate-amq.md)
* [launch-platform](/rumi-cli/commands/cloud/civo/launch-platform.md)