Skip to main content
A Virtual Private Cloud (VPC) is an isolated network boundary for your resources. Instances, clusters, and filesystems inside a VPC can communicate with each other but are isolated from resources in other VPCs. You need at least one VPC before you can create instances. VPCs are project-scoped and region-bound.
Prerequisite: You need an existing project before creating a VPC.

​
Summary

This page explains how to create and manage Virtual Private Cloud (VPC) networks in the nscale Console UI. Use this workflow if you:
  • Need a private network boundary for workloads in a specific project
  • Want to prepare networking before creating instances (you need at least one VPC to create instances)

​
Availability

This feature is available for On-demand and Reserved cloud services.

​
Requirements

  • A project where the VPC will be created (VPCs are project-scoped; you can create multiple VPCs per project)
  • Permission and sufficient quota to create a VPC
VPCs are project-scoped — you can create and use multiple VPCs within the same project.
Your VPC’s workload subnet must have at least a /24 CIDR block (256 IP addresses). This is the minimum for any network.

​
VPC Lifecycle

ActionDetails
CreateProvide name, project, region, address range, and optional DNS server IPs
Edit DNS IPsYou can update DNS server IPs at any time after creation. Note: changes propagate via DHCP and may take up to 24 hours to apply on machines. Reboot the instance or run dhclient to force an immediate refresh.
DeleteRemove a VPC that is no longer needed
You cannot change the name, region, or address range of a VPC after creation. Plan these values carefully.

​
Step-by-step

​
Create a new VPC

  1. In the Console, open Network from the left-side menu.
  2. Select VPCs.
  3. Click New VPC.
VPC Empty Dashboard
  1. Fill in the VPC details:
  • Name: Enter a name for your network.
  • Project: Choose the project where the VPC should exist.
  • Region: Select the region for the VPC.
  • Address range: Enter the CIDR block for the VPC (e.g., 10.0.0.0/16).
CIDR examples: 10.0.0.0/16 gives you 65,536 addresses (large VPC). 10.0.1.0/24 gives you 256 addresses (minimum). Use a /16 or /20 if you expect to scale.
  • DNS server IPs: Add one or more DNS server IPs (if needed).
If you leave DNS server IPs blank, Nscale-provided DNS defaults will be used.
Adding an explicit DNS server will bypass internal hostname resolution. Instances in the VPC will not be able to resolve each other by hostname. Use with caution.
  1. Create the VPC.
VPC Create Flow
  1. Verify the result:
  • You should see the new VPC appear in the VPC list for the selected project.
VPC Dashboard

​
Quotas

To check your current network quota, go to Dashboard → Resource Usage in the console. The dashboard shows your provisioned and total limits for networks alongside GPU, servers, clusters, and filesystem quotas.

​
Common Issues / Troubleshooting

  • Symptom: You can’t find a VPC you expect to see in the Console. Likely cause: The Console is currently scoped to a different project. VPC networks are project-scoped, so you’ll only see VPCs created in the selected project. Fix: In the Console, switch to the correct project, then return to Network → VPCs and check the list again.
  • Symptom: Your DNS server IPs changed after the VPC was created. Likely cause: DNS servers can change over time (for example, if your upstream DNS changes), and the VPC still has the older DNS server IPs configured. Fix: Go to Network → VPCs, select the VPC, and update the DNS server IPs. You can return later at any time to edit them.

Instances

Create compute instances inside your VPC

Security Groups

Control traffic rules for resources in your VPC

Filesystem

Attach shared persistent storage within your VPC

API Reference

Manage VPCs programmatically via the Networking and Storage API