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.
A Virtual Private Cloud (VPC) is a private network interface for collections of DigitalOcean resources. VPC networks are private networks that contain collections of resources that are isolated from the public internet and other VPC networks within your account, project or between teams in the same datacenter region. This means your resources, such as Droplets and databases, can reside in a network that is only accessible to other resources in the same network.
You can use VPC networks to organize and isolate resources into a more secure infrastructure for your applications, execution environments, and tenancies. VPC networks also give you more control over your infrastructure’s networking environment: you can select your network’s IP range, set up cloud firewalls, configure internet gateways, and connect VPC networks to each other through VPC peering.
You can create a variety of new resources in a VPC network, but you can’t migrate all kinds of resources between networks. The following table lists DigitalOcean resources compatible with VPC networks and which ones support migration:
Resource Type | Create within VPCs | Migrate between VPCs |
---|---|---|
Droplets | Creation supported. | Migration supported using snapshots. |
Managed databases | Creation supported. | Native migration supported. |
Kubernetes clusters | Creation supported. | Not supported. |
Load balancers | Creation supported. | Not supported. |
Spaces | Not applicable. | Not applicable. |
Volumes | Not applicable. | Not applicable. |