Version: Next

Installation

This guide covers installing the Aruba Cloud CLI on your platform and initial configuration.

Installation

Download Pre-built Binary

Download the latest release for your platform from the releases page.

Linux AMD64

You can install the CLI using either the direct binary or the tarball:

Option 1: Download the direct binary

wget https://github.com/Arubacloud/acloud-cli/releases/latest/download/acloud-linux-amd64
sudo mv acloud-linux-amd64 /usr/local/bin/acloud
sudo chmod +x /usr/local/bin/acloud

Option 2: Download and extract the tarball

wget https://github.com/Arubacloud/acloud-cli/releases/latest/download/acloud-linux-amd64.tar.gz
tar -xzf acloud-linux-amd64.tar.gz
sudo mv acloud /usr/local/bin/acloud
sudo chmod +x /usr/local/bin/acloud

For Ubuntu 20.04 or older WSL distributions (GLIBC 2.31 compatible):

If you encounter GLIBC version errors (e.g., GLIBC_2.34 not found), use the Ubuntu 20.04 compatible binary:

# Download and extract Ubuntu 20.04 compatible binary
wget https://github.com/Arubacloud/acloud-cli/releases/latest/download/acloud-linux-amd64-ubuntu20.tar.gz
tar -xzf acloud-linux-amd64-ubuntu20.tar.gz

# Move to PATH
sudo mv acloud-linux-amd64-ubuntu20 /usr/local/bin/acloud
sudo chmod +x /usr/local/bin/acloud

Note: The Ubuntu 20.04 compatible binary works on Ubuntu 20.04, 22.04, 24.04, and newer versions. Use this version if you're running older WSL distributions or encounter GLIBC compatibility issues.

Linux ARM64

For Ubuntu 22.04+ or newer distributions:

# Download and extract
wget https://github.com/Arubacloud/acloud-cli/releases/latest/download/acloud-linux-arm64.tar.gz
tar -xzf acloud-linux-arm64.tar.gz

# Move to PATH
sudo mv acloud-linux-arm64 /usr/local/bin/acloud
sudo chmod +x /usr/local/bin/acloud

For Ubuntu 20.04 or older distributions (GLIBC 2.31 compatible):

If you encounter GLIBC version errors, use the Ubuntu 20.04 compatible binary:

# Download and extract Ubuntu 20.04 compatible binary
wget https://github.com/Arubacloud/acloud-cli/releases/latest/download/acloud-linux-arm64-ubuntu20.tar.gz
tar -xzf acloud-linux-arm64-ubuntu20.tar.gz

# Move to PATH
sudo mv acloud-linux-arm64-ubuntu20 /usr/local/bin/acloud
sudo chmod +x /usr/local/bin/acloud

macOS (Intel)

You can install the CLI using either the direct binary or the tarball:

Option 1: Download the direct binary

curl -LO https://github.com/Arubacloud/acloud-cli/releases/latest/download/acloud-darwin-amd64
sudo mv acloud-darwin-amd64 /usr/local/bin/acloud
sudo chmod +x /usr/local/bin/acloud

Option 2: Download and extract the tarball

curl -LO https://github.com/Arubacloud/acloud-cli/releases/latest/download/acloud-darwin-amd64.tar.gz
tar -xzf acloud-darwin-amd64.tar.gz
sudo mv acloud /usr/local/bin/acloud
sudo chmod +x /usr/local/bin/acloud

macOS (Apple Silicon)

You can install the CLI using either the direct binary or the tarball:

Option 1: Download the direct binary

curl -LO https://github.com/Arubacloud/acloud-cli/releases/latest/download/acloud-darwin-arm64
sudo mv acloud-darwin-arm64 /usr/local/bin/acloud
sudo chmod +x /usr/local/bin/acloud

Option 2: Download and extract the tarball

curl -LO https://github.com/Arubacloud/acloud-cli/releases/latest/download/acloud-darwin-arm64.tar.gz
tar -xzf acloud-darwin-arm64.tar.gz
sudo mv acloud /usr/local/bin/acloud
sudo chmod +x /usr/local/bin/acloud

Windows

You can install the CLI using either the direct binary or the zip archive:

Option 1: Download the direct binary

Download acloud-windows-amd64.exe from the latest release
Move it to a folder (e.g., C:\\Program Files\\acloud-cli\\)
Add that folder to your system PATH
Optionally, rename to acloud.exe for convenience

Option 2: Download and extract the zip archive

Download acloud-windows-amd64.zip from the latest release
Extract the ZIP file
Move acloud-windows-amd64.exe to a folder (e.g., C:\\Program Files\\acloud-cli\\)
Add that folder to your system PATH
Optionally, rename to acloud.exe for convenience

Build from Source

Requirements:

Go 1.24 or later

git clone https://github.com/Arubacloud/acloud-cli.git
cd acloud-cli
go build -o acloud

Authentication

The Aruba Cloud CLI requires API credentials to authenticate with Aruba Cloud services.

Setting up Credentials

Obtain API Credentials: Get your Client ID and Client Secret from the Aruba Cloud console.
Configure the CLI — pass --client-id on the command line; the secret is read securely with echo disabled:
```
acloud config set --client-id YOUR_CLIENT_ID
# Enter client secret: (hidden input, does not appear in shell history)
```
For CI/automation where shell history is not a concern, both flags may be passed together:
```
acloud config set --client-id YOUR_CLIENT_ID --client-secret YOUR_CLIENT_SECRET
```
Security note: Avoid passing --client-secret interactively — it will appear in your shell history. Omitting the flag causes the CLI to prompt for it with echo disabled.
Verify configuration:
```
acloud config show
```

Configuration File

Credentials are stored in ~/.acloud.yaml (file permissions 0600):

clientId: your-client-id
clientSecret: your-client-secret

Security Note: Keep your credentials secure. The configuration file contains sensitive information.

Configuration

The CLI configuration allows you to manage API credentials and optional settings like custom API endpoints.

Setting Configuration

Required Settings:

--client-id is required. --client-secret may be passed on the command line or omitted to be prompted securely with echo disabled (recommended for interactive use):

# Recommended: secret entered via hidden prompt (does not appear in shell history)
acloud config set --client-id YOUR_CLIENT_ID

# CI/automation: pass both flags on the command line
acloud config set --client-id YOUR_CLIENT_ID --client-secret YOUR_CLIENT_SECRET

Optional Settings:

You can optionally configure custom API endpoints:

# Set base URL (default: https://api.arubacloud.com)
acloud config set --base-url "https://api.arubacloud.com"

# Set token issuer URL (default: https://login.aruba.it/auth/realms/cmp-new-apikey/protocol/openid-connect/token)
acloud config set --token-issuer-url "https://login.aruba.it/auth/realms/cmp-new-apikey/protocol/openid-connect/token"

You can also set all values at once:

acloud config set \
  --client-id YOUR_CLIENT_ID \
  --client-secret YOUR_CLIENT_SECRET \
  --base-url "https://api.arubacloud.com" \
  --token-issuer-url "https://login.aruba.it/auth/realms/cmp-new-apikey/protocol/openid-connect/token"

Viewing Configuration

To view your current configuration:

acloud config show

Output example:

Current configuration:
  Client ID: your-client-id
  Client Secret: ********
  Base URL: https://api.arubacloud.com (default)
  Token Issuer URL: https://login.aruba.it/auth/realms/cmp-new-apikey/protocol/openid-connect/token (default)

Configuration File Format

The configuration is stored in ~/.acloud.yaml:

clientId: your-client-id
clientSecret: your-client-secret
baseUrl: https://api.arubacloud.com  # Optional, uses default if not set
tokenIssuerUrl: https://login.aruba.it/auth/realms/cmp-new-apikey/protocol/openid-connect/token  # Optional, uses default if not set

Default Values:

If baseUrl and tokenIssuerUrl are not specified in the configuration file, the CLI uses these defaults:

Base URL: https://api.arubacloud.com
Token Issuer URL: https://login.aruba.it/auth/realms/cmp-new-apikey/protocol/openid-connect/token

Updating Configuration

You can update individual settings without affecting others:

# Update only the client secret
acloud config set --client-secret NEW_SECRET

# Update only the base URL
acloud config set --base-url "https://custom-api.example.com"

Note: Both --client-id and --client-secret must always be present in the configuration. If you're updating one, make sure the other is already set or provide both. When updating the secret interactively, omit --client-secret to be prompted with echo disabled:

acloud config set --client-secret   # prompted securely

Context Management

The CLI provides context management to avoid passing --project-id repeatedly. Contexts allow you to save project IDs and switch between them easily.

Setting up a Context

Create a context with a project ID:

acloud context set my-prod --project-id "66a10244f62b99c686572a9f"

Using a Context

Switch to a saved context:

acloud context use my-prod

Once a context is active, you can run commands without specifying --project-id:

# Works without --project-id
acloud storage blockstorage list
acloud storage snapshot list
acloud management project get <project-id>

Managing Contexts

List all contexts:

acloud context list

Output shows all contexts with the current one marked with *:

Contexts:
=========
my-prod              Project ID: 66a10244f62b99c686572a9f *
my-dev               Project ID: 66a10244f62b99c686572a9e
my-staging           Project ID: 66a10244f62b99c686572a9d

* = current context

Show current context:

acloud context current

Delete a context:

acloud context delete my-dev

Context File

Contexts are stored in ~/.acloud-context.yaml:

current-context: my-prod
contexts:
  my-prod:
    project-id: 66a10244f62b99c686572a9f
  my-dev:
    project-id: 66a10244f62b99c686572a9e

Overriding Context

You can always override the context by explicitly passing --project-id:

# Uses context project ID
acloud storage blockstorage list

# Overrides with specific project ID
acloud storage blockstorage list --project-id "different-project-id"

Auto-completion

The CLI supports shell auto-completion for commands, flags, and resource IDs.

Bash

Current Session

source <(acloud completion bash)

Permanent Installation

Linux:

acloud completion bash | sudo tee /etc/bash_completion.d/acloud

macOS:

acloud completion bash > $(brew --prefix)/etc/bash_completion.d/acloud

After installation, restart your shell or run:

source ~/.bashrc  # or ~/.bash_profile on macOS

Zsh

Add to ~/.zshrc:

# Enable completion
autoload -Uz compinit
compinit

# Load acloud completion
source <(acloud completion zsh)

Or for permanent installation:

acloud completion zsh > "${fpath[1]}/_acloud"

Fish

acloud completion fish | source

Or for permanent installation:

acloud completion fish > ~/.config/fish/completions/acloud.fish

PowerShell

Add to your PowerShell profile:

acloud completion powershell | Out-String | Invoke-Expression

Features of Auto-completion

The auto-completion system provides:

Command completion: Tab-complete commands and subcommands
```
acloud man<TAB>  # completes to "management"
```

Flag completion: Tab-complete available flags

acloud config set --<TAB>  # shows available flags

Resource ID completion: Tab-complete resource IDs with descriptions

Management Resources:

acloud management project get <TAB>
# Shows:
# 655b2822af30f667f826994e    defaultproject
# 66a10244f62b99c686572a9f    develop
# ...

Storage Resources:

# Block Storage
acloud storage blockstorage get <TAB>
# Shows:
# 6965a6c3ffc0fd1ef8ba5612    MyVolume
# 6965a6c3ffc0fd1ef8ba5613    DataVolume
# ...

# Snapshots
acloud storage snapshot get <TAB>
# Shows:
# 696c9edce63c1af07d60d0c7    MySnapshot
# 696c9edce63c1af07d60d0c8    BackupSnapshot
# ...

# Backups
acloud storage backup get <TAB>
# Shows:
# 67649dac8c7bb1c5d7c80631    MyBackup
# 67649dac8c7bb1c5d7c80632    DailyBackup
# ...

# Restores (hierarchical: backup-id then restore-id)
acloud storage restore get <TAB>
# First shows backup IDs:
# 67649dac8c7bb1c5d7c80631    MyBackup
# ...
acloud storage restore get 67649dac8c7bb1c5d7c80631 <TAB>
# Then shows restore IDs for that backup:
# 67664dde0aca19a92c2c48bb    RestoreOperation1
# ...

Auto-completion works with get, update, and delete commands for all resources.

Verifying Installation

Test your installation:

# Check version
acloud --version

# View available commands
acloud --help

# Test API connectivity
acloud management project list

Next Steps

Debug Mode

The CLI provides a global --debug (or -d) flag that enables verbose logging to help troubleshoot issues. When enabled, it shows:

HTTP Request/Response details: All HTTP requests and responses made by the SDK
Request payloads: JSON-formatted request bodies being sent to the API
Error details: Full error response bodies when requests fail

Security Warning: Debug output may include credentials and tokens from HTTP headers. Do not use --debug in shared terminal sessions or paste its output publicly.

Usage

Add the --debug flag to any command:

# Enable debug logging for a command
acloud --debug network securityrule update <vpc-id> <securitygroup-id> <securityrule-id> --tags test

# Short form
acloud -d network vpc list

Example Output

When debug mode is enabled, you'll see additional output like:

[ArubaSDK] 2025-01-15 10:30:45.123456 HTTP Request: PUT https://api.arubacloud.com/...
[ArubaSDK] 2025-01-15 10:30:45.234567 Request Headers: ...
[ArubaSDK] 2025-01-15 10:30:45.345678 Request Body: {...}

=== DEBUG: Security Rule Update Request ===
VPC ID: 69495ef64d0cdc87949b71ec
Security Group ID: 694b05ac4d0cdc87949b75f9
Security Rule ID: 694b06564d0cdc87949b7608
Request Payload:
{
  "metadata": {
    "name": "my-rule",
    "tags": ["test"],
    ...
  },
  ...
}
==========================================

[ArubaSDK] 2025-01-15 10:30:46.456789 HTTP Response: 200 OK
[ArubaSDK] 2025-01-15 10:30:46.567890 Response Body: {...}

Note: Debug output is sent to stderr, so it won't interfere with normal command output and can be redirected separately if needed.

Output Format

All list and get commands support a global --output (or -o) flag that controls the output format.

Value	Description
`table`	Human-readable fixed-width table (default)
`table-json`	JSON array of flat snake_case objects (one per row)
`table-yaml`	YAML sequence of flat snake_case mappings (one per row)
`json`	Full SDK response object as indented JSON
`yaml`	Full SDK response object as YAML

# Default table output
acloud network vpc list

# Flat JSON array — easy to pipe to jq
acloud network vpc list -o table-json

# Full SDK response envelope
acloud network vpc list -o json

table-json is the best choice for scripting with tools like jq:

acloud storage blockstorage list -o table-json | jq '.[].name'

Safe Delete (Dry Run)

Every delete command supports --dry-run to validate that a resource exists without deleting it:

acloud storage blockstorage delete <volume-id> --dry-run
# [dry-run] Would delete block storage '<volume-id>'. Resource exists and is accessible.

Pass --yes (or -y) to skip the interactive confirmation prompt.

Pagination

All list commands support --limit and --offset flags to paginate large result sets.

Flag	Description
`--limit N`	Return at most N results
`--offset N`	Skip the first N results

# First page of 10 results
acloud storage blockstorage list --limit 10

# Second page
acloud storage blockstorage list --limit 10 --offset 10

When neither flag is passed the API returns its default result set.

Troubleshooting

GLIBC Version Errors

If you see errors like:

acloud: /lib/x86_64-linux-gnu/libc.so.6: version 'GLIBC_2.34' not found

This means your Linux distribution has an older GLIBC version than required. Solution: Use the Ubuntu 20.04 compatible binary:

# Download Ubuntu 20.04 compatible binary instead
wget https://github.com/Arubacloud/acloud-cli/releases/latest/download/acloud-linux-amd64-ubuntu20.tar.gz
tar -xzf acloud-linux-amd64-ubuntu20.tar.gz
sudo mv acloud-linux-amd64-ubuntu20 /usr/local/bin/acloud
sudo chmod +x /usr/local/bin/acloud

The Ubuntu 20.04 compatible binaries work on Ubuntu 20.04, 22.04, 24.04, and newer versions.

"Error initializing client"

This usually means credentials are not configured. Run:

acloud config set

"No projects found"

Ensure your credentials have the correct permissions and you have projects in your account.

Debugging API Errors

If you encounter API errors (e.g., 500 Internal Server Error), use the --debug flag to see the full request and response:

acloud --debug network securityrule update <vpc-id> <securitygroup-id> <securityrule-id> --tags test

This will show:

The exact request payload being sent
The full HTTP response (including error details)
Any SDK-level logging

Auto-completion not working

Ensure bash-completion is installed:

# Ubuntu/Debian
sudo apt-get install bash-completion

# macOS
brew install bash-completion

Reload your shell configuration:
```
source ~/.bashrc
```

Installation​

Download Pre-built Binary​

Linux AMD64​

Linux ARM64​

macOS (Intel)​

macOS (Apple Silicon)​

Windows​

Build from Source​

Authentication​

Setting up Credentials​

Configuration File​

Configuration​

Setting Configuration​

Viewing Configuration​

Configuration File Format​

Updating Configuration​

Context Management​

Setting up a Context​

Using a Context​

Managing Contexts​

Context File​

Overriding Context​

Auto-completion​

Bash​

Current Session​

Permanent Installation​

Zsh​

Fish​

PowerShell​

Features of Auto-completion​

Verifying Installation​

Next Steps​

Debug Mode​

Usage​

Example Output​

Output Format​

Safe Delete (Dry Run)​

Pagination​

Troubleshooting​

GLIBC Version Errors​

"Error initializing client"​

"No projects found"​

Debugging API Errors​

Auto-completion not working​

Installation

Download Pre-built Binary

Linux AMD64

Linux ARM64

macOS (Intel)

macOS (Apple Silicon)

Windows

Build from Source

Authentication

Setting up Credentials

Configuration File

Configuration

Setting Configuration

Viewing Configuration

Configuration File Format

Updating Configuration

Context Management

Setting up a Context

Using a Context

Managing Contexts

Context File

Overriding Context

Auto-completion

Bash

Current Session

Permanent Installation

Zsh

Fish

PowerShell

Features of Auto-completion

Verifying Installation

Next Steps

Debug Mode

Usage

Example Output

Output Format

Safe Delete (Dry Run)

Pagination

Troubleshooting

GLIBC Version Errors

"Error initializing client"

"No projects found"

Debugging API Errors

Auto-completion not working