Instance types, images and zones

What an instance type is, which images boot on it, and how regions and availability zones decide where a machine runs.

Last updated 18 November 2026View as Markdown

Instance types

An instance type is a hardware shape: vCPUs, memory, a local disk, a shared or dedicated CPU, and an architecture. Types are named by family and size:

Family Types CPU
standard standard-2 … standard-16 shared, x86
performance performance-1x1, performance-1 … performance-16 shared, x86
arm arm-2 … arm-16 shared, Arm
dedicated dedicated-2 … dedicated-48 dedicated, x86
memory memory-4 shared, x86
legacy legacy-2x2, legacy-3x4, legacy-4x8, legacy-8x16, legacy-16x32 shared, x86

In <family>-<n> the number is the vCPU count; performance-2 has 2 vCPUs, 4 GiB of memory and an 80 GB disk. In <family>-<n>x<m>, m is the memory in GiB. The API also accepts the provider's own type names (for example cpx22) for existing automation. The launch form lists every type with its price and stock.

Instead of a type, a launch can name a size class (sizeClass): s-2 (2 vCPU / 4 GiB), s-4 (4 / 8), s-8 (8 / 16), s-16 (16 / 32), m-4 (4 / 32), d-2 (2 dedicated / 8) or d-8 (8 dedicated / 32). It becomes the smallest x86 type of your provider that fits; when none fits, the launch is refused with 400 "Your provider offers no size for class …". Give exactly one of serverType and sizeClass.

The root disk is the type's own disk; its size cannot be chosen. A resize changes CPU and memory only and keeps the disk (see Resize an instance).

Images

An image is the operating system the machine boots from, for one architecture (x86_64 or arm64). The catalog is GET /ec2/api/catalog/images (optionally ?architecture=arm64); in Terraform, the dcloud_images data source. Choose an image of the type's architecture: the launch form lists only those. Your own machine images of that architecture and region are listed first, under My images.

Regions and zones

Region Zones Where
de1 de1a (Falkenstein), de1b (Nuremberg) Germany
fi1 fi1a (Helsinki) Finland; opt-in only, see Run outside Germany

Without a zone, an instance runs in its subnet's zone if you named a subnet, and otherwise in the region's default zone (de1a in de1, fi1a in fi1). Networks span every zone of their region; a volume lives in one zone and attaches only to an instance in that zone. Instances cannot move between zones: take a machine image and launch it in the other zone.

GET /ec2/api/availability-zones?regionId=de1

lists each zone with its city, whether it is the default, and the provider location behind it (ec2:DescribeAvailabilityZones). In Terraform, the dcloud_availability_zones and dcloud_regions data sources.

Stock

Instance types are sold from live stock in each zone; a type can be sold out in de1a and in stock in de1b. See Check stock before you launch.

Did this page help you?