For AI agents: The documentation index is at https://docs.digitalocean.com/llms.txt. Markdown versions of pages use the same URL with index.html.md in place of the HTML page (for example, append index.html.md to the directory path instead of opening the HTML document).

VPC peering joins two VPC networks with a secure, private connection. This allows resources in those networks to connect to each other’s private IP addresses as if they were in the same network.

VPC peering is available across all regions and enables routing between any two VPC networks. The one exception is that peering between datacenters is not available in BLR1.

Peering works with the following resources:

• Droplets
  • Private Droplets support VPC peering automatically without additional configuration or route updates.
  • Droplets created after 2 October 2024 on a peered VPC network are configured for peering automatically. If you add a peering to an existing Droplet’s VPC network, restart the Droplet’s networking stack to add the necessary peering route information. See How to Update Droplet Routes to Enable VPC Peering for instructions.
  • Droplets created before 2 October 2024 must be updated manually to enable peering traffic. See How to Update Droplet Routes to Enable VPC Peering for instructions.
• Managed Databases
  • All managed databases are compatible with VPC peering.
• Managed Kubernetes (DOKS)
  • Worker nodes created after 2 October 2024 on a peered VPC network are configured for peering automatically. If you created the nodes before this date, or added your first peering connection after the nodes were created, recycle your worker nodes to add the new peering routes.

Create a VPC Peering Using the CLI

The VPC peering creation command requires you to provide two VPC network IDs for the --vpc-ids flag. Use doctl vpcs list command to retrieve a list of your VPC networks and their IDs.

doctl vpcs peerings create example-peering-name --vpc-ids f81d4fae-7dec-11d0-a765-00a0c91e6bf6,3f900b61-30d7-40d8-9711-8c5d6264b268

Create a VPC Peering Using the API

The VPC peering creation call requires you to provide two VPC network IDs for the vpc_ids field. Use the /v2/vpcs endpoint to retrieve a list of your VPC networks and their IDs.

curl -X POST \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
  -d '{"name": "my-first-vpc-peering", "vpc_ids": [ "997615ce-132d-4bae-9270-9ee21b395e5d", "e51aed59-3bb1-4a6a-8de0-9d1329e9c997"]}' \
  "https://api.digitalocean.com/v2/vpc_peerings"

Create a VPC Peering Using the Control Panel

To create a VPC peering, click Networking in the main menu, then click VPC. On the VPC Networks page, click Actions, then Create a Peering Connection to open the Create VPC Peering window. You can also open a VPC’s detail page, click the Peering Connections tab, then click Create a Peering Connection.

In the Create VPC Peering window, select a network from the VPC Network drop-down and a second network from the Peer to VPC Network drop-down. The drop-downs filter to matching VPCs as you type.

Under Choose a name, accept the default generated name (such as vpc-peering-1234567890) or enter a name. Names can only contain alphanumeric characters, dashes, and periods. Click Create peering connection.

View a VPC’s Peering Connections

To view a VPC network’s peering connections, click Networking in the main menu, then click VPC. Peering connections are listed in the Connections column on the VPC Networks page.

You can also click a VPC network’s name to go to its detail page, then click the Peering Connections tab. All active connections are listed. To peer another network to this VPC, click Create a Peering Connection.