> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Create and manage VPCs
> How to create and manage Virtual Private Clouds on CoreWeave Kubernetes Service
A VPC defines a network isolation configuration for attaching CoreWeave products, such as CKS clusters. This guide is for administrators who provision or update network isolation for CoreWeave workloads. It covers how to create a new VPC and how to edit or delete an existing one using the Cloud Console. By the end, you have a VPC configured with the address ranges and DNS settings required to attach a CKS cluster or other CoreWeave product.
## Create a VPC with the Cloud Console
This section walks through creating a new VPC from the Cloud Console, including the required address ranges and any advanced settings.
To create a VPC using the Cloud Console, navigate to the [VPCs](https://console.coreweave.com/vpcs) page. This page lists your deployed VPCs along with their statuses.
To open the VPC creation form, click the **Create a VPC** button on the top right of the screen.
The configuration fields on this page include:
| Value | Description |
| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name** | Specify a name for the VPC. |
| **Zone** | A dropdown menu where you can select a Zone. A VPC must exist in the same Zone as the cluster you attach it to. See [Regions](/platform/regions/about-regions-and-azs) for more information. |
| **Allow Public Prefix Announcement** | Specifies whether the VPC allows public prefixes advertised from Nodes to be imported into public-facing networks, making them accessible from the internet. |
| **VPC Prefixes** | A list of additional prefixes associated with the VPC. For example, CKS clusters use these prefixes for Pod and Service CIDR ranges. |
| **Host Prefixes** | Unique IPv4 IP ranges assigned to hosts in the VPC, validated for IPv4 CIDR format with prefix. |
| **Custom DNS Servers** | DNS servers announced through DHCP, validated for IP format. |
### VPC prefixes
VPC prefixes define the address ranges that workloads inside the VPC draw from, so you must plan them before attaching a cluster. A VPC requires at least three unique prefixes to be compatible with a CKS cluster. Prefixes can't use any address in the [RFC6598](https://datatracker.ietf.org/doc/html/rfc6598) (Carrier-Grade NAT) range of `100.64.0.0/10`.
For example, your VPC prefixes might look like this:
| Prefix | Description |
| -------------- | --------------------------------- |
| `10.0.0.0/13` | Pod CIDR Range |
| `10.16.0.0/22` | Service CIDR Range |
| `10.16.4.0/22` | Internal Load Balancer CIDR Range |
Click the **Add a Prefix** button.
The **New VPC Prefix** window opens, where you can enter the prefix details.
Additional configuration settings for the VPC are found under **Advanced Settings**.
| Value | Description |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
| **Disable External Propagate** | Disables external propagation for this prefix, preventing the advertisement of the address space to external networks. |
| **Disable Host BGP Peering** | Disables BGP Peering for this prefix. |
| **Host DHCP Route** | Indicates this prefix has a DHCP route. |
| **Public** | Marks the prefix as publicly accessible. |
### Host prefixes
**Host prefixes** define the IP address ranges assigned to the Nodes within a VPC. Nodes use these ranges for network communications with other resources within the VPC.
**Host prefixes** define the IP address ranges assigned to the Nodes within a VPC, which are used for network communications between Nodes and other resources within the VPC.
You can add more Host Prefixes at any time, but you can't remove an existing Host Prefix.
To add a new range of host IP addresses, click the **Add a Prefix** button to open the **New Host Prefix** window.
Each CoreWeave Availability Zone (AZ) features a default Host Prefix. CoreWeave assigns it automatically unless you specify a different prefix. The default Host Prefixes for each AZ are:
| General Access AZ | Default Host Prefix CIDR |
| --------------------------------------------------------------- | ------------------------ |
| [`EU-SOUTH-03B`](/platform/regions/eu-south#eu-south-03b) | `10.206.192.0/18` |
| [`EU-SOUTH-04A`](/platform/regions/eu-south#eu-south-04a) | `10.104.192.0/18` |
| [`RNO2A`](/platform/regions/us-west#rno2a) | `10.168.192.0/18` |
| [`US-CENTRAL-06A`](/platform/regions/us-central#us-central-06a) | `10.50.192.0/18` |
| [`US-CENTRAL-07A`](/platform/regions/us-central#us-central-07a) | `10.109.128.0/18` |
| [`US-EAST-01A`](/platform/regions/us-east#us-east-01a) | `10.202.192.0/18` |
| [`US-EAST-02A`](/platform/regions/us-east#us-east-02a) | `10.184.192.0/18` |
| [`US-EAST-04A`](/platform/regions/us-east#us-east-04a) | `10.176.192.0/18` |
| [`US-EAST-06A`](/platform/regions/us-east#us-east-06a) | `10.192.192.0/18` |
| [`US-EAST-08A`](/platform/regions/us-east#us-east-08a) | `10.186.192.0/18` |
| [`US-EAST-13A`](/platform/regions/us-east#us-east-13a) | `10.221.128.0/18` |
| [`US-EAST-14A`](/platform/regions/us-east#us-east-14a) | `10.213.128.0/18` |
| [`US-WEST-01A`](/platform/regions/us-west#us-west-01a) | `10.188.192.0/18` |
| [`US-WEST-04A`](/platform/regions/us-west#us-west-04a) | `10.190.192.0/18` |
| [`US-WEST-09B`](/platform/regions/us-west#us-west-09b) | `10.210.192.0/18` |
| [`US-WEST-10A`](/platform/regions/us-west#us-west-10a) | `10.57.128.0/17` |
**SUNK users take note:** If you supply `network.hostPrefixes`, it should have a minimum prefix length of `/18`. Prefixes smaller than `/18` don't have physical-location-based IP addresses, which SUNK uses to calculate adjacency.
## Manage VPCs in the Cloud Console
This section covers ongoing management tasks for existing VPCs, including how to sort, edit, and delete them. After you create a VPC, you can edit its configuration or remove it when you no longer need it. The [VPCs](https://console.coreweave.com/vpcs) page displays a list of your VPCs and their statuses.
You can sort VPCs by **Name**, **Zone**, **Age**, or **Status**. Use the **arrow** buttons near each field to sort the list accordingly.
### Edit a VPC
To make changes to an existing VPC, click the vertical ellipsis menu button to the right of the VPC name. Then, click the **Edit** button.
This opens the **Edit VPC** window, which includes all the same options as the Create VPC window.
### Delete a VPC
To delete a VPC, select the vertical ellipsis beside the VPC name, then select **Delete**.
