An instance type fixes an instance’s shape: its vCPUs and memory, its bandwidth, its storage performance and how many volumes and network interfaces it takes. A type’s shape never changes, so an instance keeps its vCPUs and memory for as long as it has that type.
The types your organization can launch are on the launch page’s Instance type list, and in
ListInstanceTypes (ezgh compute instance-types list):
curl -sS "https://compute-api.ezghcloud.com/v1/organizations/$ORG_ID/instance-types" \
-H "Authorization: Bearer $EZGH_API_KEY"CPU families
| Family | cpuFamily |
vCPUs | Counts against |
|---|---|---|---|
| Shared | shared |
Share the host’s CPUs with other instances | The Shared vCPUs quota |
| Dedicated | dedicated |
Each vCPU has a CPU core to itself; the console shows them as Cores | The Dedicated vCPUs quota |
Each instance’s vCPUs count against its family’s quota while it’s running or launching.
What a type sets
| Field | Meaning |
|---|---|
name |
What you launch it by. Types in a series share a family |
vcpus, memoryMiB |
The instance’s vCPUs and memory |
numaNodes |
The NUMA nodes the guest sees |
architecture |
amd64 |
network.baselineMbps, network.burstMbps, network.pps |
Bandwidth the instance always has, the most it can burst to, and its packets per second (the console’s Bandwidth, baseline / burst) |
storage.iops, storage.throughputMBps |
The most IOPS and throughput (MB/s) its volumes get together, whatever each volume provides |
limits.volumes, limits.networkInterfaces |
The most volumes (root volume included) and network interfaces it takes |
status |
active, or deprecated: existing instances keep running, but new launches and resizes to it are refused (409 instance_type_deprecated) |
An unknown type is 400 instance_type_unknown.
Changing type
Resize an instance to change its type. A running instance restarts with the new type; a stopped one takes it at its next start. Its volumes, network interfaces and addresses stay.