Subnets

A subnet is the network segment a VM’s primary interface attaches to. It owns the IPv4 CIDR, IPv6 prefix, default gateway, and DNS resolvers handed to VMs via DHCP.

Managed defaults#

Every zone ships with a managed subnet called DEFAULT. Today there’s one zone (mum-1a, zone_id=1), so there’s one DEFAULT subnet — subnet_id=1. For almost all workloads it’s the right pick: IPv4, IPv6, internet egress, reachable from every other resource in the zone.

exc compute subnet list

Sample output:

ID  NAME     ZONE_ID  CIDR
1   DEFAULT  1        10.0.0.0/20

Reference it at create time:

exc compute create --subnet_id 1 ...

Per-zone#

A subnet lives in exactly one zone. A VM’s subnet pins it to that zone (and therefore to the volumes you can attach). Pick the subnet whose zone_id matches the volumes / public IPs you want to use together. With one zone today this is a freebie; it matters more once a second zone comes online.

Custom subnets#

There’s no public create endpoint yet — you can list and get subnets but not provision new ones. Email [email protected] if you need a dedicated subnet, VPC, or peering arrangement.

The permission model already reserves space for this: compute:subnet:* exists and matches list today.

Terraform data source#

The Terraform provider exposes subnets read-only as data.excloud_subnets so you can look the DEFAULT subnet up by name at plan time instead of hard-coding an ID.