DigitalOcean VPCs: what private networking does and does not protect
A DigitalOcean VPC keeps your resources apart from the internet and from other VPCs. It does not keep them apart from each other, and the documentation describes it as isolation, not encryption, so put a Cloud Firewall inside the VPC and keep TLS on.
The word private is doing a lot of work in "private networking". It suggests that traffic between your own Droplets is safe because outsiders cannot see it. That is true of outsiders, and says nothing about the resources inside the network, which is where a small team's real exposure usually sits.
Your resources are already in a VPC
DigitalOcean's default VPC page says each datacenter region containing your resources has a default VPC network, and all applicable resources are placed into it unless you specify otherwise at creation. The docs word this carefully: it is the regions where you have resources, not every region.
You cannot delete a default VPC. The doctl reference says to make another VPC the default for the region with doctl vpcs update <vpc-network-id> --default=true and then delete the one you no longer want, and the destroy page adds that a VPC must have no resources in it first. Everything created without a deliberate choice lands in the default, which is how a staging database and a production web server end up on the same network without anyone deciding it.
Old resources are a special case. DigitalOcean replaced its earlier private networking service with VPC in 2020, and its release notes say all Droplets created after 1 October 2020 are placed into a VPC by default. A page on VPC support says older Droplets cannot be added to a VPC without changing their IP address. How the pre-2020 network behaved is not described in the current documentation, so if you run Droplets that old, check what network they are actually on.
What a VPC isolates, and what it does not
The VPC overview says VPC networks are inaccessible from the public internet and from other VPC networks. Two VPCs in the same region and team do not talk over private addresses unless you peer them. DigitalOcean describes VPC peering as joining two networks with a secure, private connection as if they were one. It works across regions, with one stated exception, BLR1, where peering between datacenters is not available. The limits page adds that a VPC cannot span datacenters, that ranges cannot overlap within an account, and that Droplets and Kubernetes nodes created before 2 October 2024 need route updates or recycling to use peering. Whether peering works between two different teams is not documented.
Now the part people assume wrongly. Inside one VPC, nothing keeps resources apart. DigitalOcean's page on adding resources says a resource automatically has an IP address in the VPC's network and is accessible from other resources in the network. No page says in so many words that traffic is open by default. By implication, though, a Droplet with no Cloud Firewall can be reached by every other Droplet in its VPC, so a compromised web server can try your database host's open ports directly. The metadata endpoint article shows one way such a server gets compromised.
Firewalls apply inside the VPC too
The fix is already in the product. The firewall limits page states that firewalls affect both public and VPC network traffic, and that rules specific to either must name the public or private IP range. A source in a rule can be a Droplet, a tag, a VPC or a CIDR range. Write the rule the way you mean it: the database tag accepts the database port from the application tag, and nothing else, even on the private network. The Cloud Firewall article has the commands and an audit script.
Isolation is not encryption
We found no statement anywhere in the VPC documentation that VPC traffic is encrypted. It calls the network private, isolated and secure, and peering a secure, private connection, but none of those is a claim about encryption. DigitalOcean documents isolation and not encryption, so treat private traffic as plaintext unless the service you are using encrypts it itself. Managed databases do: DigitalOcean says they require TLS for connections. Your own services should as well, and an internal HTTP API deserves a certificate in the same way a public one does.
Which resources live in a VPC
The VPC features page lists Droplets, Managed Databases, Kubernetes clusters, load balancers and NAT gateways as resources you can create inside a VPC. Spaces and Volumes are marked not applicable, so a Space is never inside your private network and is always reached through its own endpoint. For databases, only resources in the same VPC can use the private hostname, and the database trusted sources article covers what to add on top.
App Platform apps support VPC networks in all regions, with two limits stated on its page: function components are not supported, and VPC access cannot be combined with dedicated egress IPs.
Public addresses are still the default
Being in a VPC does not mean having no public address. The Droplet API says Droplets are created with public networking available by default, and the create page says a private IPv4 address is always assigned. A Droplet in a VPC therefore usually has both, and the public one is what an internet scanner finds.
You can remove it. DigitalOcean's Private Droplets have no public IP at all: you clear public IPv4 and IPv6 in the control panel, set public_networking to false in the API, or pass --enable-public-networking=false to doctl when creating the Droplet. Private Droplets became generally available on 30 June 2026. The constraints are real:
- You cannot add a public IP address to one later.
- The Droplet Console is not available, because there is no public address, so you reach it through a bastion host.
- External network load balancers are not supported.
- Outbound internet access goes through a VPC NAT gateway.
A VPC NAT gateway became generally available on 19 November 2025. It centralises outbound internet access behind a single static public IP address. Its documented limits include no IPv6 and no attachment to more than one VPC. The pages disagree about a default gateway setting, with the limits page saying the default_gateway setting is not implemented while the features page describes the feature, so read both before relying on it. A fixed outbound address also has a side benefit: you can add it to an allowlist elsewhere, such as a database's trusted sources.
Seeing what you have
The doctl commands are short. The columns below are the ones the reference lists:
doctl vpcs list --format Name,IPRange,Region
doctl compute droplet list --format ID,Name,PrivateIPv4,PublicIPv4,VPCUUID
To find the Droplets that still have a public address, use the JSON output. The API reference documents a networks object with v4 and v6 arrays whose items carry a type of public or private, plus a vpc_uuid field. This filter prints each Droplet with any public interface and its VPC:
doctl compute droplet list -o json | jq -r '
.[] | select(any((.networks.v4[]?, .networks.v6[]?); .type == "public"))
| "\(.name)\t\(.vpc_uuid)"'
For each Droplet it prints, ask whether it needs to face the internet. A database host, a worker or a build machine usually does not, and it is a candidate for a Private Droplet plus a NAT gateway. If the VPC column shows more than one value across production and experiments, that is the separation you may have meant to have and never made.
What to do
- List your VPCs and check what shares the default one.
- Put production in its own VPC if it shares a network with experiments.
- Attach a Cloud Firewall to every Droplet, with private sources named as tags or ranges.
- Remove public addresses from anything that does not need them.
- Keep TLS on service traffic, because the VPC will not do it for you.
FAQ
Is traffic inside a DigitalOcean VPC encrypted?
DigitalOcean documents isolation, not encryption. We found no statement that VPC traffic is encrypted, so use TLS between your own services.
Can Droplets in the same VPC reach each other by default?
Resources in a VPC are accessible from other resources in the network, and Cloud Firewalls apply to VPC traffic as well as public traffic, so attach firewalls with private-side rules.
Can I delete the default VPC?
Not directly. Make another VPC the default for the region with doctl vpcs update --default=true, then delete the old one once it has no resources in it.
How do I create a Droplet with no public IP?
Create a Private Droplet: clear the public IPv4 and IPv6 options, or use doctl with --enable-public-networking=false. It cannot get a public IP later and has no Droplet Console.
Secorvia reads DigitalOcean with a read-scope token. The DigitalOcean integration page and the DigitalOcean page say what it covers.