exo-compute-instance
Manage Exoscale compute instances
TLDR
Create a Debian based Compute instance with a disk size of 10GB
Log into a Compute instance via SSH
List all of the Compute instances
Add an instance to a Security Group
Scale the size of a Compute instance
Create a snapshot of a Compute instance
Revert a Compute instance to a snapshot (the data written after the snapshot has been created will be lost)
Resize the disk size of a Compute instance to 20GB
SYNOPSIS
exo-compute-instance <subcommand> [OPTIONS]
PARAMETERS
create
Create a new compute instance
delete
Delete one or more compute instances
list
List compute instances in a zone
show
Show details of a compute instance
start
Start a stopped compute instance
stop
Stop a running compute instance
reboot
Reboot a compute instance
--zone ZONE
Target Exoscale zone (e.g., ch-dk-2)
--name NAME
Instance name or ID
--template TEMPLATE
Disk template UUID or slug
--instance-type TYPE
Compute instance SKU/size
--key KEY
SSH key name for access
--output FORMAT
Output format: table|json|yaml
--force
Skip confirmation prompts
--help
Show command help
DESCRIPTION
The exo-compute-instance command is part of the Exoscale CLI (exo), a powerful tool for interacting with the Exoscale Infrastructure-as-a Service (IaaS) platform. It enables users to manage virtual machine (VM) instances, including listing available instances, creating new ones from templates, updating configurations, starting, stopping, rebooting, and deleting them.
Key features include support for specifying instance sizes (SKUs), disk templates, SSH keys, security groups, and private networks. Operations can be targeted to specific zones like de-fra-1 or ch-dk-2. Output formats such as table, JSON, or YAML facilitate scripting and automation.
Authentication is handled via API keys, typically set as environment variables (EXOSCALE_API_KEY and EXOSCALE_API_SECRET). The command integrates seamlessly with other Exoscale services like load balancers and object storage, making it essential for cloud infrastructure management workflows.
CAVEATS
Requires valid Exoscale API credentials; operations may incur costs; concurrent modifications can lead to errors; limited to user's account quotas.
AUTHENTICATION
Set EXOSCALE_API_KEY and EXOSCALE_API_SECRET env vars or use --api-key / --api-secret flags.
ZONES
List zones with exo compute zone list; default is first available.
HISTORY
Introduced in Exoscale CLI v1.0 (2019); evolved with platform features like Anti-Affinity Groups in v2.x; actively maintained as open-source on GitHub.
SEE ALSO
exo-compute-template(1), exo-network(1), exo-storage(1), virsh(1)


