VPC network
A Virtual Private Cloud (VPC) network allows applications running on instances on the same cloud provider as your YugabyteDB Managed clusters to communicate with those clusters without traversing the public internet; all traffic stays in the cloud provider's network.
Use VPC networks to lower network latencies, make your application and database infrastructure more secure, and reduce network data transfer costs.
In YugabyteDB Managed, a VPC network consists of the following components:
| Component | Description |
|---|---|
| VPC | A VPC reserves a block of IP addresses on the cloud provider. You deploy your cluster in a VPC. |
| Peering connection | Links the cluster VPC to an application VPC on the same cloud provider. A peering connection is created for a VPC. |
| Private service endpoint | Links the cluster endpoint to an application VPC endpoint, using the cloud provider's private linking service. A private service endpoint (PSE) is added to a cluster; the cluster must be deployed in a VPC. |
Typically, you would either have a VPC network with peering, or use PSEs.
VPCs, peering connections, and private service endpoints are managed on the VPC Network tab of the Network Access page.
Note
To connect a cluster to an application VPC using either a peering connection or a private service endpoint, you need to deploy the cluster in a dedicated VPC. You need to set up the dedicated VPC before deploying your cluster.
VPC networking is not supported in Sandbox clusters.
