A Virtual Private Cloud (VPC) is a private network interface for collections of DigitalOcean resources. VPC networks are inaccessible from the public internet and other VPC networks, and traffic on them doesn’t count against bandwidth usage. You can link VPC networks to each other using VPC peering connections (currently in early access).
DigitalOcean Virtual Private Cloud (VPC) peering is now in early availability. VPC peering allows you to join two VPC networks with a secure, private connection. See How to Create a VPC Peering to get started.
VPC-native networking is now available in early availability for all DigitalOcean Managed Kubernetes (DOKS) customers. VPC-native networking allows customers to route traffic directly between DOKS pods, services, and other resources on VPC networks. For more information, see the DOKS Features page.
You can now change the default VPC network for a region. When you change the default VPC network for a region, the new default network will be automatically selected during applicable resource set ups unless otherwise specified.
All Droplets created after 1 October 2020 are placed into a VPC network by default. You can no longer manually enable VPC networking on existing Droplets. You can migrate existing Droplets into VPC networks using Snapshots.
For more information, see all VPC release notes.