Networks (VPC)

A network (VPC) is an isolated private IPv4 address space for your Wonder Cloud account. Subnets, servers, databases, load balancers and VPN traffic live inside it.

When Cloud is first enabled, Wonder usually creates a default network for you. Create additional networks when you need separate ranges (for example non-overlapping CIDRs for VPN peers).

Network list

The network list shows every VPC in the account, its CIDR, region, status and available actions. It also shows quota usage before you create another network. Open a row to inspect subnets and connected services, or use Create network when quota is available.

Network detail

The detail screen shows the VPC topology, subnet ranges and resource relationships. It is also where you choose whether Wonder Desktop should use this VPC for private connectivity. Review dependencies before deleting or changing the network.

Create network

Choose a non-overlapping private CIDR, region and subnet plan. The preview validates the allocation before submission and shows the ranges that will be created. Network and subnet quotas must have enough capacity for the complete plan.

What you get

  • A private CIDR (for example 10.0.0.0/16 or 172.20.0.0/16)
  • A region
  • Zero or more subnets carved from that CIDR
  • Isolation from other accounts — traffic stays private unless you attach public IPs, load balancers or VPN

Create in the console

  1. Open Cloud → Networks.
  2. Click Create network.
  3. Fill in:
    • Name — display name
    • Region — where the network is created
    • CIDR — IPv4 range (presets are available in the form)
    • Number of subnets and allocation % — the console plans equal slices of the VPC range and creates those subnets after the network succeeds
  4. Review the planned subnet table, then submit.
  5. Wait until status is active, then open the network detail page.

Prefer a CIDR that does not overlap remote office ranges if you will use VPN.

Wonder Desktop on this VPC

On the network detail page you can toggle Deploy Wonder Desktop on this VPC.

What it means for your business

When this setting is on, Wonder Desktop sessions for your account use this VPC to reach private resources — for example office printers and systems reachable through VPN on the same network.

When it is off, Wonder Desktop does not use this VPC for that connectivity. Cloud servers, databases and other resources on the VPC keep working as usual; only the Desktop ↔ VPC attachment is affected.

Why only one VPC can be active

At most one network per account may have this toggle enabled at a time. Wonder Desktop needs a single clear private network for office reachability. Enabling it on this VPC automatically turns it off on any other VPC in the account.

Effects when you turn it on

  • Desktop sessions for the account can reach addresses on this VPC (and, via VPN, peers and printers on the remote side of that tunnel).
  • The previous “Desktop VPC” (if any) loses the flag so there is never more than one.

Effects when you turn it off

  • Desktop sessions stop using this VPC for private reachability.
  • Other Cloud resources on the VPC are unchanged.
  • You can enable the toggle later on this or another VPC (still only one at a time).

When to enable it

  • You connect an office with VPN and need Desktops to print or talk to on-prem systems on this network.
  • You want Desktop traffic on the same private address space as your Cloud workloads here.

When to leave it off

  • This VPC is only for Cloud servers / databases and Desktop does not need it.
  • CIDR and VPN planning are still in progress — enable after ranges and tunnels are ready.

Create with CLI

Create the VPC only (subnets are a separate step with wcc):

wcc network create --name vpc-prod --cidr 10.40.0.0/16
# optional: --region us-east4

List and inspect:

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

Promote another VPC to account default (when more than one exists):

wcc network promote --name vpc-prod

Then create subnets — see Subnets.

Settings

| Field | Description | |---|---| | Name | Display name | | CIDR | IPv4 range for the network (for example 10.0.0.0/16) | | Region | Where the network is created |

Tips

  • Plan CIDRs before VPN: peer and Wonder ranges must not collide.
  • In the console, creating a network can also provision the first batch of subnets; with CLI you create the network first, then each subnet.
  • Delete dependents (servers, databases, VPN gateway, subnets) before deleting a network.

Next