Compute

Launch and manage virtual machine instances.

This guide walks you through creating an instance and connecting to it.

With an agent (MCP)

Connect the redu MCP, then just ask your agent. It runs plan_instance to resolve the image, flavor, and network for you (no opaque IDs to supply), then create_instance to launch the VM and get_ssh_command to hand you the SSH command. From there it can manage the instance with instance_action (start, stop, reboot), get_instance_logs, and delete_instance, and browse with list_instances, list_flavors, and list_images.


Create a medium Ubuntu instance called web-01 with my default keypair on the first available network, and give me the SSH command.

1. Launch an instance

Go to Menu → Compute → Virtual Machines, then click Launch Instance.

The launch form is organised into three required sections and one expandable section:

Section	Field	What to choose
Name and image	Instance name	A meaningful name, for example `app-web-01`
Name and image	Image	The operating system or reusable snapshot to boot
Choose a size	Flavor	The vCPU, RAM, disk, and hourly price that fit the workload
Access	SSH keypair	The public key registration used to sign in
Access	Firewall rules	One or more security groups that allow only the traffic you need
Advanced options	Attach a new volume	Optional persistent block storage created with the instance
Advanced options	Select Network	The private network used for internal traffic
Advanced options	DNS Entries	Optional public domain and application port mappings
Advanced options	Configuration script	Optional cloud-init or shell script that runs once on first boot

Name, image, and size

Choose the image before finalising the flavor. Images can declare minimum RAM or disk requirements, and incompatible sizes are disabled automatically. The size table shows the exact hourly estimate and an approximate monthly cost.

On a limited trial, sizes above m1.medium require a payment card. Some of the largest sizes require approval on every account.

Access

Select an SSH key and at least one security group. If you do not have a key yet, create or import one from SSH Keypairs.

For SSH access, the selected security group must allow inbound TCP traffic on port 22. Web applications normally need inbound TCP traffic on ports 80, 443, or the application’s own port. See Security Groups.

Advanced options

Open Advanced options to configure storage, networking, DNS, and the startup script.

Attach a new volume: enter a volume name and size from 1 to 2048 GB. This option is not available on a limited trial. See Storage.
Select Network: choose a private network. The first available network is selected automatically; if none exists, create one from Private Networks.
DNS Entries: leave the domain blank for a generated .redu.cloud address and leave the port blank to assign an available port. Each extra entry publishes another endpoint. Limited trials allow one DNS entry per instance.
Configuration script: paste #cloud-config or a shell script, upload a .yaml, .yml, .txt, or .sh file, or choose a compatible template. It runs once on first boot.

To use your own domain, verify it first under Account → Domains. See Custom Domains.

Example cloud-init:


#cloud-config
packages:
  - nginx
runcmd:
  - systemctl enable --now nginx

Before you launch

The Launch summary shows the selected name, image, size, storage, security groups, and price. The Launch instance button also explains anything still missing. Confirm that:

The image and flavor are compatible
An SSH keypair, security group, and private network are selected
Every published port is allowed by the selected security group
The configuration script can run unattended

Click Launch instance. Provisioning continues asynchronously; the new instance appears on the Virtual Machines page while it builds.

2. Manage instances

Go to:

Menu → Compute → Virtual Machines → Instances

The list can be filtered by All instances, Solo, Clusters, Managed data, and Other automated. Each row shows the instance’s image, flavor, creation time, uptime, state, and task.

The available Actions depend on the current state:

Manage DNS, or make the instance public or private
Create a snapshot
Start, shut off, soft reboot, or hard reboot
Resize the instance, then confirm or revert the resize
Change the security group
Upgrade the instance to a cluster
Copy the SSH command
Delete the instance

Wait for the state to become Active before connecting or taking a snapshot.

3. Connect via SSH

If SSH is enabled and a keypair is selected:


ssh -p <port> ubuntu@<host>

You can copy the command directly from the UI.

Troubleshooting

Launch button disabled

Missing required fields
Unsupported image/flavor combination

SSH not working

A keypair must be selected
Security group must allow port 22

Network missing

Create one in Networking