VPC Networks

​

Summary

• 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

​

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
• Important: VPCs are project-scoped — multiple VPCs can be create and used within the same project

​

Step-by-step

​

Create a new VPC

1. In the Console, open Network folder from the left-side menu.
2. Select VPCs.
3. Click New VPC.

4. 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 address range for the VPC.
• DNS server IPs: Add one or more DNS server IPs (if needed).

5. Create the VPC.

6. Verify the result:

• You should see the new VPC appear in the VPC list for the selected project. (Exact UI confirmation text is not currently documented.)

​

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.