This document provides a comprehensive reference for AI agents using the CloudAMQP CLI tool.
The CLI uses a single API key for all operations in this priority order:
CLOUDAMQP_APIKEYenvironment variable~/.cloudamqprcplain text config file- Interactive prompt
Default: https://customer.cloudamqp.com/api (unified API endpoint)
cloudamqp <category> <action> [--id <instance_id>] [other flags]
All instance-specific operations use the --id flag to specify the instance.
cloudamqp instance list- Returns: Array of instances with id, name, plan, region, ready status
cloudamqp instance get --id <id>- Returns: Full instance details including API key, URLs, hostnames
cloudamqp instance create --name=<name> --plan=<plan> --region=<region> [--tags=<tag1> --tags=<tag2>] [--vpc-subnet=<subnet>] [--vpc-id=<id>]- Required: name, plan, region
- Optional: tags (multiple allowed), vpc-subnet, vpc-id
- Returns: Instance creation response with id, url, apikey
cloudamqp instance update --id <id> --name=<new_name> --plan=<new_plan>- Updates instance name and/or plan
- Use for upgrading/downgrading plans
cloudamqp instance delete --id <id>- Permanently deletes the instance
cloudamqp instance resize-disk --id <id> --disk-size=<gb> [--allow-downtime]- Required: disk-size (in GB)
- Optional: allow-downtime flag
cloudamqp vpc listcloudamqp vpc get --id <id>cloudamqp vpc create --name=<name> --region=<region> --subnet=<subnet> [--tags=<tag>]cloudamqp vpc update --id <id> --name=<new_name>cloudamqp vpc delete --id <id>cloudamqp team listcloudamqp team invite --email=<email> [--role=<role>] [--tags=<tag>]cloudamqp team update --user-id <id> --role=<role>cloudamqp team remove --email=<email>cloudamqp plans [--backend=<rabbitmq|lavinmq>]- Returns: Array of plans with name, price, backend, shared status
cloudamqp regions [--provider=<provider>]cloudamqp audit [--timestamp=<timestamp>]All instance-specific commands use the unified API and --id flag pattern.
cloudamqp instance nodes list --id <id>cloudamqp instance nodes versions --id <id>cloudamqp instance plugins list --id <id>- Returns: Array of plugins with name, version, description, enabled status
cloudamqp instance config list --id <id>cloudamqp instance config get --id <id> --key <config_key>cloudamqp instance config set --id <id> --key <config_key> --value <config_value>cloudamqp instance restart-rabbitmq --id <id> [--nodes=node1,node2]
cloudamqp instance restart-cluster --id <id>
cloudamqp instance restart-management --id <id> [--nodes=node1,node2]cloudamqp instance start --id <id> [--nodes=node1,node2]
cloudamqp instance stop --id <id> [--nodes=node1,node2]
cloudamqp instance reboot --id <id> [--nodes=node1,node2]
cloudamqp instance start-cluster --id <id>
cloudamqp instance stop-cluster --id <id>cloudamqp instance upgrade-erlang --id <id>
cloudamqp instance upgrade-rabbitmq --id <id> --version=<version>
cloudamqp instance upgrade-all --id <id>
cloudamqp instance upgrade-versions --id <id> # Check available versions# Create instance
cloudamqp instance create --name="my-instance" --plan="bunny-1" --region="amazon-web-services::us-east-1"
# Poll until ready
while true; do
cloudamqp instance get --id <id> | grep '"ready": true' && break
sleep 30
donecloudamqp instance update --id <id> --plan="rabbit-3"# Get instance details
cloudamqp instance get --id <id>
# Check nodes and configuration
cloudamqp instance nodes list --id <id>
cloudamqp instance config list --id <id>
# Perform maintenance
cloudamqp instance restart-rabbitmq --id <id>
cloudamqp instance upgrade-all --id <id># List all configuration
cloudamqp instance config list --id <id>
# Get specific setting
cloudamqp instance config get --id <id> --key tcp_listen_options
# Update configuration
cloudamqp instance config set --id <id> --key tcp_listen_options --value '[{"port": 5672}]'lemur- Free RabbitMQ sharedlemming- Free LavinMQ shared
bunny-1- $99bunny-3- $297rabbit-1- $299rabbit-3- $897rabbit-5- $1495
penguin-1- $99penguin-3- $297penguin-5- $495
amazon-web-services::us-east-1amazon-web-services::us-west-1amazon-web-services::us-west-2amazon-web-services::eu-west-1google-compute-engine::us-central1-a
- API errors return non-zero exit codes
- Error messages are printed to stderr
- Most commands return JSON output on success
- Use environment variables for API keys to avoid exposing them in command history
- Unified API: All operations now use a single API key and the unified customer API endpoint
- Flag-based Commands: All instance-specific operations use
--id <instance_id>instead of positional arguments - Instance Creation: Instance creation is async - poll with
get --id <id>untilready: true - Plan Upgrades: Plan upgrades are immediate but may cause brief downtime
- Async Operations: Some actions (upgrades, restarts) are asynchronous - they return immediately but run in background
- Multiple Tags: The
--tagsflag can be used multiple times:--tags=prod --tags=web - VPC Requirements: VPC operations require the instance to be in the same region as the VPC
- Configuration Management: Use the config commands to manage RabbitMQ settings directly
- OpenAPI Specs: When asked for OpenAPI specs, use make targets
make openapi.yamlandmake openapi-instance.yamlto download the latest versions
The ~/.cloudamqprc file contains only your API key in plain text:
your-api-key-here
No JSON formatting or multiple keys are needed - the unified API handles all operations with a single key.