Skip to navigation

Create a VM

Creating a VM gives you a new server with the size, operating system and network you choose. The portal’s Deploy page is a single form — location, plan, operating system, SSH keys, network, billing and VM details — with a running cost summary and the Deploy button in the bottom bar. This page walks through every field. For the shortest path to a working server, follow Launch your first VM instead.

Which options to choose

Most first VMs need only the defaults. These are the choices that matter:

ChoicePick this if…Pick the other option if…
Templates (OS image)You want a clean install of Ubuntu, Debian, Windows and so on.You are copying an existing VM: use Snapshots or Backups. See Custom images.
SSH key (Linux)Always, if you can. Nobody can guess a key.Without a key, the VM uses a generated password, shown under Overview → Connection Details.
Public IP networkThe VM must be reachable from the internet (websites, APIs, SSH from your laptop).Private + NAT: the VM only needs to reach out to the internet. Private only: the VM only talks to your other VMs.
Hourly billingYou might delete or resize the VM within a month, or you’re testing.Monthly (where offered): the VM will run all month and you want the lower rate. A committed VM can’t be deleted or resized until the commitment ends.

How it works

  1. You fill in the Deploy page and click Deploy.
  2. The portal checks your billing state and wallet balance. If they are fine, the VM is queued and you return to the Cloud Virtual Machines list.
  3. The VM shows Provisioning, then Running. Billing starts when creation finishes; a create that fails is not billed.
  4. You open the VM and copy the sign-in details from Overview → Connection Details.

Before you begin

  • An IBEE account with a verified identity.
  • Write access to the workspace. Read-only members don’t see Deploy VM.
  • Credit in your wallet (Billing and usage).
  • Optional, depending on how you want to connect the VM:
    • An SSH key. You can also create one on the Deploy page.
    • A VPC with a subnet in the same location, for Private + NAT or Private only.
    • A Reserved IP in the same location, if the VM must keep a fixed address.
    • A firewall group. If you pick none, the default group is attached.

Create a VM in the portal

1

Open the Deploy page

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

2

Select a location

Under Location, pick a region tab (for example Asia), then a data center. Plans, images, VPCs and Reserved IPs further down are filtered to this location. You can’t move a VM to another location later.

3

Choose a plan

Under Choose Plan, filter by All, Standard or Performance, then select a plan. Each row shows vCPU, memory, storage, included bandwidth and the price per month and per hour. The portal checks that the plan has room in the location before you deploy. See Instance types.

4

Select the operating system

Under Operating System, pick where the boot disk comes from:

TabUse it for
TemplatesOperating system images maintained by IBEE. The default.
ISOsNot available. The ISO service isn’t running, so the tab shows “No ISOs available for this account.” See ISOs.
SnapshotsA copy of another VM, taken as a snapshot.
BackupsA copy of another VM from a scheduled backup. Only the root disk is used.

On Templates, pick an OS family card (for example Ubuntu or Windows), then a version from the OS Version dropdown. A Selected: <version> chip confirms it.

5

Review licences and control panels

If the plan and image have add-ons, Licences & control panels lists them with a monthly price. For Windows images, the Windows licence is selected automatically and marked Required for the selected Windows image; it is priced per vCPU. Other add-ons are Optional.

6

Add SSH keys (Linux)

For Linux images, open Select SSH Keys and pick one or more saved keys. To add one, click Add Key, then Create Key Pair (the private key downloads once; keep it safe) or Import Key to paste an existing public key. The section is hidden for Windows images, which use a password.

7

Configure the network

Under Network Configuration → VM network, choose Internet and VPC access:

OptionWhat you get
Public IP (default)A public IPv4 address for inbound and outbound traffic. Keep No VPC · public interface only, or pick a VPC and Subnet to also give the VM a private address.
Private + NATThe VM sits in a NAT Gateway VPC. It can reach the internet, but the internet can’t reach it. (NAT, network address translation, lets many private machines share one public address for outgoing traffic.)
Private onlyThe VM sits in a VPC with no route to the internet.

With Public IP, the Reserved public IP field appears. Leave Allocate automatically, or pick one of your unattached Reserved IPs in this location. Picking a specific Reserved IP limits the deploy to one VM. A private VPC needs a Reserved IP for public access.

Under Firewall, pick a firewall group or click Create Group. If you pick none, the default firewall group is attached. See Networking for VMs.

8

Choose a billing term

Under Billing, choose how the VM is billed. The cards offered depend on the plan:

CardHow it works
Hourly (default)“No commitment · metered in 15-minute usage windows”. The monthly figure shown is the hourly rate × 731 hours.
MonthlyA commitment that renews on the 1st of every month. The first month is charged only for the days left in it. The VM can’t be deleted or resized while committed.
9

Set VM details

Under VM Details:

  • Instances: use − and + to create up to 5 identical VMs. The maximum can be lower when capacity or free public addresses in the location are limited, and it is 1 when you picked a specific Reserved IP.
  • Hostname: lowercase letters, numbers and hyphens (spaces become hyphens; other characters are removed). With more than one instance this becomes the Base hostname, and each VM is prefilled as <base>-1, <base>-2 and so on under Instance hostnames. Every hostname must be unique.
10

Deploy

Check the cost in the bottom bar, then click Deploy (or Deploy N VMs). If the billing check passes, you return to the Cloud Virtual Machines list and the VM shows Provisioning. If it doesn’t, a Billing needs attention popup appears: click Add Credits, top up, and deploy again.

Create a VM with the CLI

Install the CLI with python3 -m pip install --upgrade ibee-cli, create an API token under Organization → API Tokens with the vm.read and vm.write scopes, and export it with your workspace ID:

export IBEE_TOKEN="ibee_prod_key_xxxxxxxxxxxx"
export IBEE_WORKSPACE_ID="710995"

List the IDs a create needs, then create the VM:

ibee compute sites
ibee compute plans --vm-type cloud --site-id SITE_ID
ibee compute images --vm-type cloud --site-id SITE_ID
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. Run ibee ops get OPERATION_ID until status is succeeded or failed.

FlagPurpose
--nameRequired. The VM name.
--site-id, --plan-id, --template-idRequired. IDs from ibee compute sites, plans and images.
--os-type, --os-distroRequired. Copy them from the image: linux or windows, and the distribution, such as ubuntu.
--cpu, --ram-mb, --disk-gbCopy them from the plan (--cpu and --ram-mb are required). The example is perf.1.c2.m4.
--billing-intervalRequired: HOURLY, or MONTHLY for a one-month commitment. The CLI reads the plan and sends its billing selection, as the portal does.
--ssh-keysA public key, inline. Repeat it for more keys. --ssh-key-ids takes saved key IDs instead.
--vpc-id, --subnet-id, --network-connectivity, --reserved-public-ip-idThe same network choices as the portal.

One command creates one VM. To create several, run it once per VM with a different --name.

Create a VM with the Python SDK

Install with pip install ibee. The SDK reads IBEE_TOKEN and IBEE_WORKSPACE_ID. It sends exactly what you pass, so copy the size from the plan, the OS from the image, and build billing_catalog from the plan the way the portal does: the plan’s billing_catalog with its HOURLY (or MONTHLY) entry from billing_options merged in.

import os
import time
from ibee import Ibee
client = Ibee()
site_id = os.environ["IBEE_SITE_ID"]
plans = client.compute_catalog.list_compute_plans(vm_type="cloud", site_id=site_id).plans
plan = next(p for p in plans if p.plan_id == os.environ["IBEE_PLAN_ID"])
images = client.compute_catalog.list_compute_images(vm_type="cloud", site_id=site_id).images
image = next(i for i in images if i.template_id == os.environ["IBEE_TEMPLATE_ID"])
hourly = next(o for o in plan.billing_catalog["billing_options"] if o["billing_interval"] == "HOURLY")
accepted = client.cloud_vms.create_cloud_vm(
name="web-01",
site_id=site_id,
plan_id=plan.plan_id,
template_id=image.template_id,
os_type=image.os_type,
os_distro=image.os_distro,
cpu=plan.cpu,
ram_mb=plan.ram_mb,
disk_gb=plan.disk_gb,
billing_catalog={**plan.billing_catalog, **hourly},
ssh_keys=[open(os.path.expanduser("~/.ssh/id_ed25519.pub")).read().strip()],
)
while True:
op = client.cloud_vms.get_compute_operation(accepted.operation_id)
if op.status in ("succeeded", "failed", "cancelled", "timed_out"):
print(op.status, op.error_message or "")
break
time.sleep(10)

The raw API call is POST /compute/cloud-vms with an X-Idempotency-Key header. Its billing_catalog must be the chosen plan’s billing_catalog with one HOURLY or MONTHLY entry from billing_options merged in; the CLI’s --billing-interval does this for you, and with the SDK you build it as above. The response is 202 with an operation_id to poll at GET /compute/operations/{operation_id}.

Verify

Open Infrastructure → Cloud VMs. The VM shows Running and an address in the IP Address column. Click it, and Overview → Connection Details shows how to sign in:

VMWhat’s shown
Linux with an SSH keySSH Key Connection: username, host, the chmod command for your key, and a ready-to-copy ssh command.
Linux without a keySSH Connection: username, host and password.
WindowsRemote Desktop (RDP): IP address, the username Administrator, and the password.
Private + NAT or Private onlyPrivate SSH or RDP commands to run from inside the VPC, for example through a VPN or another VM.

The Linux username is the image’s distribution name, for example ubuntu, and it has passwordless sudo. Passwords are shown only to members with write access while the VM is running.

Limits

Value
VMs per deploy1 to 5
LocationsAmaravati (VGA) and Hyderabad (HYD)
Root diskFixed by the plan, 50 GB to 400 GB
BillingHourly (15-minute usage windows) or Monthly commitment where the plan offers it
Billing startsWhen creation finishes. Provisioning time isn’t billed.
Stopped VMsBilled at the full hourly rate until deleted

Troubleshooting

You seeWhat it meansWhat to do
Please select a VM plan, Please select an Operating System version, Select a subnet for this VPC or Each instance needs a unique hostnameA required field is empty or invalidFix the named field and click Deploy again.
Billing needs attentionYour billing state or wallet balance doesn’t cover the VMClick Add Credits, top up, then deploy again.
Only N VMs of this plan can be deployed right nowCapacity, or free public addresses, in the location is limitedDeploy fewer VMs, pick another plan or location, or use Private + NAT, which needs no public address.
CPU VM limit reached: N used of M allowed. Change your plan or remove a VM before deploying another.Your organization has reached its Cloud VM limitDelete a VM you don’t need, or ask to raise the limit.
Selected VM plan does not support monthly billingThe plan offers only HourlyChoose Hourly.
API 402 with billing_reason insufficient_balanceThe wallet can’t cover the VM; nothing was createdTop up, then retry with the same X-Idempotency-Key.
API 423 organization_suspendedThe organization is suspended, so changes are refusedResolve the suspension under Billing, then retry.
The VM stays in ProvisioningCreation is still running or has stalledCheck Activity logs. If nothing changes, contact IBEE support.