Skip to navigation

Launch your first VM

This quickstart gives you a working Linux server in the IBEE cloud: you create a small Ubuntu VM, connect to it over SSH from your own computer, put a test web page on it, and then delete it so it stops costing money. Every step uses the defaults, so you don’t need to know anything about networks or firewalls yet.

When to use this page

You want to…Read
Try IBEE for the first time, or check that your account worksThis quickstart
Choose a private network, a Windows image, several VMs or a monthly termCreate a VM
Copy an existing VMCustom images

How it works

  1. You create an SSH key: a pair of files on your computer. The public half goes on the VM; the private half stays with you and acts as your password.
  2. You create the VM in the portal (or with one CLI command) and add the public key to it.
  3. You connect with ssh ubuntu@<the VM's IP address>.
  4. You delete the VM. Billing stops when it’s gone.

Before you begin

  • An IBEE account with a verified identity, and an organization.

  • Write access to a workspace.

  • Credit in your wallet. The Deploy page shows the exact hourly and monthly price before you click Deploy. See Billing and usage.

  • A terminal: Terminal on macOS or Linux, or PowerShell on Windows 10 and later (both include ssh).

  • An SSH key. If you don’t have one, create it now and press Enter to accept the defaults:

    ssh-keygen -t ed25519 -C "you@example.com"

    This creates ~/.ssh/id_ed25519 (private, never share it) and ~/.ssh/id_ed25519.pub (public). Print the public key with cat ~/.ssh/id_ed25519.pub.

Option A: the portal

1

Open the Deploy page

In the portal sidebar, open Infrastructure → Cloud VMs, then click Deploy VM.

2

Pick a location

Under Location, select the Asia tab, then Amaravati.

3

Pick a small plan

Under Choose Plan, pick perf.1.c2.m4: 2 vCPU, 4 GiB of memory, a 50 GB disk and 2 TB of outbound data per month. That’s enough for a test website or API. The price per hour and per month updates as you choose. Other sizes are listed in Instance types.

4

Pick Ubuntu

Under Operating System → Templates, click Ubuntu, then choose Ubuntu 24.04 (or the newest version listed) from OS Version.

5

Add your SSH key

Under SSH Keys, click Add Key, open Import Key, give the key a name and paste the contents of ~/.ssh/id_ed25519.pub. If you’ve saved the key before, pick it from Select SSH Keys instead.

6

Keep the defaults

Leave Network Configuration on Public IP with No VPC · public interface only, leave Firewall empty (the default firewall group allows SSH on port 22 and web traffic on ports 80 and 443), and leave Billing on Hourly.

7

Name it and deploy

Under VM Details, keep Instances at 1 and enter a hostname such as web-01 (lowercase letters, numbers and hyphens). Click Deploy. You return to the Cloud Virtual Machines list, where the VM shows Provisioning. If a Billing needs attention popup appears instead, click Add Credits, top up and deploy again.

8

Connect

When the status changes to Running, click the VM. Under Overview → Connection Details, copy the SSH command, or use the address from the IP Address column:

ssh ubuntu@203.0.113.10

The first time, type yes to trust the server. You are now signed in as ubuntu, a user with sudo rights.

Option B: the ibee CLI

The CLI needs Python 3.10 or later.

1

Install the CLI and sign in

Create an API token under Organization → API Tokens with the vm.read and vm.write scopes. Find your workspace ID in the portal URL (.../workspaces/710995/...). Then:

python3 -m pip install --upgrade ibee-cli
export IBEE_TOKEN="ibee_prod_key_xxxxxxxxxxxx"
export IBEE_WORKSPACE_ID="710995"
ibee --version
2

Find a site, a plan and an image

ibee compute sites
ibee compute plans --vm-type cloud --site-id SITE_ID
ibee compute images --vm-type cloud --site-id SITE_ID

Note the site_id for Amaravati, the plan_id of perf.1.c2.m4, and the template_id of an Ubuntu image.

3

Create the VM

Pass those IDs, the plan’s size (2 vCPU, 4096 MB of memory, a 50 GB disk) and the image’s OS. --billing-interval HOURLY makes the CLI read the plan and send its hourly billing selection, as the portal does:

ibee vms create --name web-01 \
--site-id SITE_ID \
--plan-id PLAN_ID \
--template-id TEMPLATE_ID \
--os-type linux --os-distro ubuntu \
--cpu 2 --ram-mb 4096 --disk-gb 50 \
--billing-interval HOURLY \
--ssh-keys "$(cat ~/.ssh/id_ed25519.pub)"

The command prints an operation_id straight away, while the VM is created in the background. Check it until status is succeeded (or failed), then list your VMs to see the new VM’s ID and public IP:

ibee ops get OPERATION_ID
ibee vms list
4

Connect

ssh ubuntu@PUBLIC_IP

Verify

From your computer, check that the server answers:

ssh ubuntu@203.0.113.10 'uname -a; uptime'

Then, signed in to the VM, install a web server:

sudo apt update
sudo apt install -y nginx
curl -I http://localhost

The last command prints HTTP/1.1 200 OK. Open http://203.0.113.10 (your VM’s address) in a browser to see the “Welcome to nginx!” page. Port 80 is open in the default firewall group, so no firewall change is needed.

Clean up

A VM is billed every hour until you delete it. Stopping it is not enough: a stopped VM is billed at the same rate.

1

Delete in the portal

Open the VM, click Actions → Delete, type the VM name to confirm, leave Reserve public IP unchecked so the address is released, and click Delete VM.

2

Or delete with the CLI

ibee vms delete VM_ID --public-ip-action release --yes

The VM disappears from the list when deletion finishes, and billing stops.

What it costs

ItemBilled?
The VM, while it exists (running or stopped)Yes, at the plan’s hourly rate, from the moment creation finishes
Outbound data up to the plan’s allowance (2 TB a month on perf.1.c2.m4)Included
Inbound dataNo
Time spent provisioning, or a create that failedNo

Troubleshooting

You seeWhat it meansWhat to do
Permission denied (publickey)The VM doesn’t have the public key that matches your private key, or you used the wrong usernameUse ubuntu@… (copy it from Connection Details). Check that you imported ~/.ssh/id_ed25519.pub. To add another key, see SSH Keys.
Connection timed outThe VM isn’t Running yet, or a firewall blocks port 22Wait for Running. If you chose your own firewall group, allow TCP 22 from your address.
Connection refusedThe VM is still finishing its first boot, so the SSH service hasn’t startedWait a little after it shows Running, then try again.
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!You used this IP address for an earlier VMRun ssh-keygen -R 203.0.113.10 (your VM’s address) and connect again.
Billing needs attentionYour wallet balance is too low for the planClick Add Credits, top up, then deploy again.
ibee: command not foundThe CLI’s install folder isn’t on your PATHOpen a new terminal. If that doesn’t help, add Python’s user scripts folder (shown by python3 -m site --user-base, plus /bin) to PATH.
The CLI reports a missing token or workspaceIBEE_TOKEN or IBEE_WORKSPACE_ID isn’t set in this terminalExport both again, or pass --token and --workspace before the command.

Next steps