VPCs

The VPCs page helps you view and manage VPCs (Virtual Private Clouds) in the console.

What are VPCs?

VPCs are isolated networks you create within a cloud provider’s region. Each VPC can have subnets (IP ranges) and is used to group and isolate resources such as machines and Kubernetes clusters. The console lets you manage VPCs across your cloud accounts in one place.

Subnet internet access

Each subnet reports how it is connected to the internet, under Internet access:

Public — instances may hold a public address and are reachable from the internet.
Private — not reachable from the internet, with outbound access through the provider’s NAT.
Isolated — no internet access in either direction; traffic stays within the VPC.
Custom — routing that the console cannot classify, such as a default route to an appliance you manage.
Unsupported — the provider does not model connectivity at subnet level.

Access enforcement says who guarantees it. network means the provider’s own routing enforces it, so instances in the subnet cannot escape it. none means the provider has no subnet-level boundary, and connectivity is configured per instance instead — so the value describes a convention rather than a guarantee.

Both values are read from the provider on every refresh, so they also reflect routing changes you make outside the console. The VPC API guide tabulates every combination of the two the API reports, and the rule that decides whether a subnet can hold a public machine.

When creating a VPC, each subnet can request Public, Private or Isolated where the provider supports it; a subnet defaults to Public. A public subnet is given a route to the internet, and machines launched into it receive a public address. An isolated subnet keeps only VPC-local routing.

A private subnet reaches the internet outbound through a NAT gateway, which has to sit in a public subnet of the same VPC, so a VPC with a private subnet needs a public one as well; a request without it is rejected rather than having a public subnet added to it silently. One gateway is created per VPC and shared by all of its private subnets, which keeps the cost down but places it in a single availability zone: traffic from the other zones is charged as cross-zone, and an outage of that zone takes outbound access with it.

The gateway is charged by the provider for as long as it exists, and the create page shows the monthly rate before you create the VPC. The data it processes and the public address it holds are charged on top of that rate, and depend on use rather than on the configuration. Deleting the VPC deletes the gateway and releases the address it was given, so neither is billed on after the network is gone.

Providers that do not model connectivity at subnet level reject the setting; for those, a machine’s own Network access decides whether it gets a public address.

View VPCs

The VPCs table lists all VPCs from your registered cloud accounts, with their attributes displayed in table columns. Use pagination controls at the bottom of the page to navigate between pages if there are too many VPCs to display.

When table data is being updated, table rows are displayed in italic, and table controls become inactive. It may take time to load the next portion of data.

To refresh the table, use the Reload 🔄 button.

To customize attributes displayed in the table, use the Layout ⠇ button.

When there are too many VPCs available, use the Add filters 🔎 button to fine-tune your search. See the Resource Filter documentation for details.

Attributes

The following VPC attributes are available:

ID — Provider-specific identifier
Provider — Cloud provider (e.g. Akamai)
Region — Region where the VPC is located
Account — Account that owns the VPC
Name — Display name of the VPC
Description — Optional description
CIDR block — Primary IP range for the VPC
Subnets — Subnets (ID, name, IP range) within the VPC
Default — Whether this is the default VPC for the region
Tags — Labels attached to the VPC

Which columns appear by default can vary; use the Layout button in the toolbar to show or hide columns.

Creating a new VPC

To create a new VPC, click Create in the toolbar. You will be taken to the Create VPC page to configure name, subnets, and other options. This action is disabled when the selected account does not have write access.

Deleting a VPC

To delete a VPC, check the VPC’s selection box and click the Delete 🗑️ button. This action is disabled when the VPC is associated with an account that does not have write access.

The delete action may take time. Its status and progress are available on the Actions page.