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:
How it works
- You fill in the Deploy page and click Deploy.
- 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.
- The VM shows Provisioning, then Running. Billing starts when creation finishes; a create that fails is not billed.
- 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
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.
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.
Select the operating system
Under Operating System, pick where the boot disk comes from:
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.
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.
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.
Configure the network
Under Network Configuration → VM network, choose Internet and VPC access:
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.
Choose a billing term
Under Billing, choose how the VM is billed. The cards offered depend on the plan:
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>-2and so on under Instance hostnames. Every hostname must be unique.
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:
List the IDs a create needs, then create the VM:
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.
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.
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:
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
Troubleshooting
Related pages
- Launch your first VM
- Instance types
- Networking for VMs
- SSH Keys
- Power actions: start, stop, reboot and delete
