Documentation is available in English.

Subnets

A subnet is a slice of a network CIDR. Servers, load balancers and databases attach to a subnet to receive a private IP.

You need at least one ready subnet before you can place most compute or data resources.

What you get

  • A CIDR that fits inside the parent VPC (for example 10.40.1.0/24 inside 10.40.0.0/16)
  • Optional purpose label (custom, or labels shown in the form)
  • Private addressing for attached resources

Create in the console

When creating a network

The Create network form can plan and create several subnets in one go (count + allocation percent). That is the fastest path for a new VPC.

On an existing network

  1. Open Cloud → Networks → select the network.
  2. In the subnets section, click Create subnet.
  3. Fill in name, CIDR (must fit and not overlap siblings), and purpose if shown.
  4. Submit and wait until status is active.

Create with CLI

wcc network subnet create \
  --network vpc-prod \
  --name apps \
  --cidr 10.40.1.0/24 \
  --purpose custom

--network accepts the parent network UUID or name. --purpose defaults to custom.

List and inspect:

wcc network subnet list --network vpc-prod
wcc network subnet get --name apps --network vpc-prod

Settings

| Field | Description | |---|---| | Name | Display name | | CIDR | Must fit inside the parent network CIDR and not overlap other subnets | | Purpose | Optional label (custom in CLI by default) | | Network | Parent VPC (chosen in the UI or via --network) |

Tips

  • Split apps and data across subnets if that simplifies firewall design.
  • Failed creates usually mean the CIDR overlaps or does not fit the parent — adjust the mask or pick a free slice.
  • Quota applies to subnets separately from networks; reduce planned count if create is blocked by quota.

Next