# Add a Dedicated VPC Peering Connection

> For the complete documentation index, see [llms.txt](https://docs.redpanda.com/llms.txt). Component-specific: [cloud-data-platform-full.txt](https://docs.redpanda.com/cloud-data-platform-full.txt)

---
title: Add a Dedicated VPC Peering Connection
latest-operator-version: v26.1.4
latest-console-tag: v3.7.3
latest-connect-version: 4.93.0
latest-redpanda-tag: v26.1.9
docname: dedicated/gcp/vpc-peering-gcp
page-component-name: cloud-data-platform
page-version: master
page-component-version: master
page-component-title: Cloud
page-relative-src-path: dedicated/gcp/vpc-peering-gcp.adoc
page-edit-url: https://github.com/redpanda-data/cloud-docs/edit/main/modules/networking/pages/dedicated/gcp/vpc-peering-gcp.adoc
description: Use the Redpanda Cloud UI to set up VPC peering.
page-git-created-date: "2024-12-13"
page-git-modified-date: "2026-02-02"
---

<!-- Source: https://docs.redpanda.com/cloud-data-platform/networking/dedicated/gcp/vpc-peering-gcp.md -->

A VPC peering connection is a networking connection between two VPCs. This connection allows the VPCs to communicate with each other as if they were within the same network. A route table routes traffic between the two VPCs using private IPv4 addresses.

> 📝 **NOTE**
>
> Traffic is _not_ routed over the public internet.

When you select a network for deploying your Redpanda Dedicated cluster, you have the option to select a private connection with VPC peering. The VPC peering connection connects your VPC to the Redpanda Cloud VPC.

## [](#prerequisites)Prerequisites

-   **VPC network**:Before setting up a peering connection in the Redpanda Cloud UI, you must have a VPC in your own account for Redpanda’s VPC to connect to.

-   **Matching region**: VPC peering connections can only be established between networks created in the **same region**. Redpanda Cloud does not support inter-region VPC peering connections.

-   **Non-overlapping CIDR blocks**: The CIDR block for your VPC network cannot match or overlap with the CIDR block for the Redpanda Cloud VPC.


> 💡 **TIP**
>
> Consider adding `rp` at the beginning of the VPC name to indicate that this VPC is for deploying a Redpanda cluster.

## [](#create-a-peering-connection)Create a peering connection

A peering becomes active after both Redpanda and GCP create a peering that targets the other project/network.

1.  In the Redpanda Cloud UI, go to the **Overview** page for your cluster.

2.  In the Details section, click the name of the Redpanda network.

3.  On the Networking page for your cluster, click **VPC peering walkthrough**.

4.  For **Connection name**, enter a name for the connection.

    For example, the name might refer to the VPC ID of the VPC you created in GCP.

5.  For **GCP project ID**, enter the ID of the project that contains the VPC network you want to connect to.

6.  For **VPC network name**, enter the name of the VPC network.

7.  Click **Create peering connection**.


## [](#create-the-reciprocal-peering-connection)Create the reciprocal peering connection

1.  In the Google Cloud console, go to VPC network peering - Create peering connection.

2.  For **Name**, enter a name for the connection (for example, `rp-peering`).

3.  Select your VPC network, project, and VPC network name.

4.  Click **Create**.


## [](#switch-from-vpc-peering-to-private-service-connect)Switch from VPC peering to Private Service Connect

VPC peering and Private Service Connect use the same DNS hostnames (connection URLs) to connect to the Redpanda cluster. When you configure the Private Service Connect DNS, those hostnames resolve to Private Service Connect endpoints, which can interrupt existing VPC peering-based connections if clients aren’t ready.

To enable Private Service Connect without disrupting VPC peering connections, do a controlled DNS switchover:

1.  Enable Private Service Connect on the existing cluster and deploy consumer-side resources, but **do not create private DNS yet**. See: [Enable Private Service Connect on an existing cluster](https://docs.redpanda.com/cloud-data-platform/networking/dedicated/gcp/configure-psc-in-api/#enable-private-service-connect-on-an-existing-cluster).

2.  During a planned window, create the private DNS zone and records in your VPC to switch the shared hostnames over to Private Service Connect.