# Configure GCP Private Service Connect in the Cloud UI > 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: Configure GCP Private Service Connect in the Cloud UI 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: configure-private-service-connect-in-cloud-ui page-component-name: cloud-data-platform page-version: master page-component-version: master page-component-title: Cloud page-relative-src-path: configure-private-service-connect-in-cloud-ui.adoc page-edit-url: https://github.com/redpanda-data/cloud-docs/edit/main/modules/networking/pages/configure-private-service-connect-in-cloud-ui.adoc description: Set up GCP Private Service Connect in the Redpanda Cloud UI. page-git-created-date: "2024-06-06" page-git-modified-date: "2026-04-21" --- > 📝 **NOTE** > > - This guide is for configuring GCP Private Service Connect using the Redpanda Cloud UI. To configure and manage Private Service Connect on an existing cluster with **public** networking, you must use the [Cloud API for BYOC](https://docs.redpanda.com/cloud-data-platform/networking/gcp-private-service-connect/) or the [Cloud API for Dedicated](https://docs.redpanda.com/cloud-data-platform/networking/dedicated/gcp/configure-psc-in-api/). > > - The latest version of Redpanda GCP Private Service Connect (available March, 2025) supports zone affinity. This allows requests from Private Service Connect endpoints to stay within the same availability zone, avoiding additional networking costs. > > - DEPRECATION: The original Redpanda GCP Private Service Connect is deprecated and will be removed in a future release. For more information, see [Deprecated features](https://docs.redpanda.com/cloud-data-platform/manage/maintenance/#deprecated-features). The Redpanda GCP Private Service Connect service provides secure access to Redpanda Cloud from your own VPC network. Traffic over Private Service Connect does not go through the public internet because these connections are treated as their own private GCP service. While your VPC network has access to the Redpanda VPC network, Redpanda cannot access your VPC network. Consider using Private Service Connect if you have multiple VPC networks and could benefit from a more simplified approach to network management. > 📝 **NOTE** > > - Each consumer VPC network can have one Private Service Connect endpoint connected to the Redpanda service attachment. > > - Private Service Connect allows overlapping [CIDR ranges](https://docs.redpanda.com/cloud-data-platform/networking/cidr-ranges/) in VPC networks. > > - The number of connections is limited only by your Redpanda [usage tier](https://docs.redpanda.com/cloud-data-platform/reference/tiers/). Private Service Connect does not add extra connection limits. > > - You control from which GCP projects connections are allowed. ## [](#requirements)Requirements - Use the [gcloud](https://cloud.google.com/sdk/docs/install) command-line interface (CLI) to create the consumer-side resources, such as a consumer VPC network and forwarding rule, or to modify existing resources to use the Private Service Connect service attachment created for your cluster. - The consumer VPC network must be in the same region as your Redpanda cluster. ## [](#enable-private-service-connect-for-existing-clusters)Enable Private Service Connect for existing clusters 1. In the Redpanda Cloud UI, open your [cluster](https://cloud.redpanda.com/clusters), and click **Dataplane settings**. 2. Under Private Service Connect, click **Enable**. 3. For [BYOVPC clusters](https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/gcp/vpc-byo-gcp/), you need a PSC NAT subnet with `purpose` set to `PRIVATE_SERVICE_CONNECT`. You also need to create VPC network firewall rules to allow Private Service Connect traffic. You can use the `gcloud` CLI: > 📝 **NOTE** > > The firewall rules support up to 20 Redpanda brokers. If you have more than 20 brokers, or for help enabling Private Service Connect, contact [Redpanda support](https://support.redpanda.com/hc/en-us/requests/new). ```bash gcloud compute networks subnets create \ --project= \ --network= \ --region= \ --range= \ --purpose=PRIVATE_SERVICE_CONNECT ``` ```bash gcloud compute firewall-rules create redpanda-psc-ingress \ --description="Allow access to Redpanda PSC endpoints" \ --network="" \ --project="" \ --direction="INGRESS" \ --target-tags="redpanda-node" \ --source-ranges="10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,100.64.0.0/10" \ --allow="tcp:30181,tcp:30282,tcp:30292,tcp:31004,tcp:31082-31101,tcp:31182-31201,tcp:31282-31301,tcp:32092-32111,tcp:32192-32211,tcp:32292-32311" ``` Provide your values for the following placeholders: - ``: The name of the PSC NAT subnet. - ``: The host GCP project ID. - ``: The name of the VPC network being used for your Redpanda Cloud cluster. - ``: The region of the Redpanda Cloud cluster. - ``: The CIDR range of the subnet. The mask should be at least `/29`. Each Private Service Connect connection takes up one IP address from the PSC NAT subnet, so the CIDR must be able to accommodate all projects from which connections to the service attachment will be issued. See the GCP documentation for [creating a subnet for Private Service Connect](https://cloud.google.com/vpc/docs/configure-private-service-connect-producer#add-subnet-psc). 4. For the accepted consumers list, you need the GCP project IDs from which incoming connections will be accepted. 5. It may take several minutes for your cluster to update. When the update is complete, the Private Service Connect status in **Dataplane settings** changes from **In progress** to **Enabled**. ## [](#deploy-consumer-side-resources)Deploy consumer-side resources For each consumer VPC network, you must complete the following steps to successfully connect to the service attachment and use the Kafka API and other Redpanda services, such as HTTP Proxy. 1. In **Dataplane settings**, copy the **DNS zone** and **Service attachment URL** under **Private Service Connect**. Use this URL to create the Private Service Connect endpoint in GCP. 2. Get the name of the consumer VPC network and the subnet ``, where the Private Service Connect endpoint forwarding rule will be created. 3. Create a Private Service Connect IP address for the endpoint: ```bash gcloud compute addresses create --subnet= --addresses= --region= ``` 4. Create the Private Service Connect endpoint forwarding rule: > 📝 **NOTE** > > If you enabled global access when creating the cluster, you must include the `--allow-psc-global-access` flag to configure the endpoint to accept client connections from different regions. ```bash gcloud compute forwarding-rules create --region= --network= --address= --target-service-attachment= ``` 5. Create firewall rules allowing egress traffic to the Private Service Connect endpoint: ```bash gcloud compute firewall-rules create redpanda-psc-egress \ --description="Allow access to Redpanda PSC endpoint" \ --network="" \ --direction="EGRESS" \ --destination-ranges= \ --allow="tcp:443,tcp:30081,tcp:30282,tcp:30292,tcp:32092-32141,tcp:35082-35131,tcp:32192-32241,tcp:35182-35231,tcp:32292-32341,tcp:35282-35331" ``` 6. Create a private DNS zone. Use the cluster **DNS zone** value as the DNS name: ```bash gcloud dns managed-zones create \ --project= \ --description="Redpanda Private Service Connect DNS zone" \ --dns-name="" \ --visibility="private" \ --networks="" ``` 7. In the newly-created DNS zone, create a wildcard DNS record using the cluster **DNS record** value: ```bash gcloud dns record-sets create '*.' \ --project= \ --zone="" \ --type="A" \ --ttl="300" \ --rrdatas="" ``` ## [](#access-redpanda-services-through-private-service-connect-endpoint)Access Redpanda services through Private Service Connect endpoint After you have enabled Private Service Connect for your cluster, your connection URLs are available in the **How to Connect** section of the cluster overview in the Redpanda Cloud UI. You can access Redpanda services such as Redpanda Console, Schema Registry, and HTTP Proxy from the client VPC or virtual network; for example, from a compute instance in the VPC or network. The bootstrap server hostname is unique to each cluster. The service attachment exposes a set of bootstrap ports for access to Redpanda services. These ports load balance requests among brokers. Make sure you use the following ports for initiating a connection from a consumer: | Redpanda service | Default port | | --- | --- | | Kafka API | 30292 | | HTTP Proxy | 30282 | | Schema Registry | 30081 | | Redpanda Console | 443 | ### [](#access-kafka-api-seed-service)Access Kafka API seed service Use port `30292` to access the Kafka API seed service. ```bash export RPK_BROKERS=':30292' rpk cluster info -X tls.enabled=true -X user= -X pass= ``` When successful, the `rpk` output should look like the following: ```bash CLUSTER ======= redpanda.rp-cki01qgth38kk81ard3g BROKERS ======= ID HOST PORT RACK 0* 0-3da65a4a-0532364.cki01qgth38kk81ard3g.fmc.dev.cloud.redpanda.com 32092 use2-az1 1 1-3da65a4a-63b320c.cki01qgth38kk81ard3g.fmc.dev.cloud.redpanda.com 32093 use2-az1 2 2-3da65a4a-36068dc.cki01qgth38kk81ard3g.fmc.dev.cloud.redpanda.com 32094 use2-az1 ``` ### [](#access-schema-registry-seed-service)Access Schema Registry seed service Use port `30081` to access the Schema Registry seed service. ```bash curl -vv -u : -H "Content-Type: application/vnd.schemaregistry.v1+json" --sslv2 --http2 :30081/subjects ``` ### [](#access-http-proxy-seed-service)Access HTTP Proxy seed service Use port `30282` to access the Redpanda HTTP Proxy seed service. ```bash curl -vv -u : -H "Content-Type: application/vnd.kafka.json.v2+json" --sslv2 --http2 :30282/topics ``` ### [](#verify-the-redpanda-console-network-path)Verify the Redpanda Console network path When you configure private connectivity through the Cloud API, set `connect_console: true` on the network configuration to enable Console access through the cluster’s private endpoint. The Cloud UI sets this for you when you enable private connectivity. The Redpanda Console URL is served on port `443` (HTTPS) and follows the form `[https://console-.](https://console-\.\);`. The `` is a per-cluster suffix assigned by the Redpanda control plane and is opaque to you; the full URL is shown in the **How to Connect** section of the cluster overview in the Redpanda Cloud Console. To verify that the network path to Redpanda Console is open, run the following commands from a host in the client network. First, confirm DNS resolves the hostname to a private IP on the cluster’s private endpoint: ```bash dig +short console-. ``` The response is a private IP from your client network’s address range, for example: ```bash 10.0.0.42 ``` Then confirm Redpanda Console responds over HTTPS through the endpoint: ```bash curl -sS -o /dev/null -w "%{http_code}\n" https://console-./ ``` Expected output: ```bash 200 ``` A 200 response confirms the network path. The Console UI itself does not expose a standalone login form: sign in to [cloud.redpanda.com](https://cloud.redpanda.com), navigate to the cluster, and use the cluster’s left navigation (**Topics**, **Brokers**, **Consumer groups**) to interact with Redpanda Console. > 📝 **NOTE** > > - DNS resolution for the Redpanda Console hostname is handled automatically by the cluster’s private endpoint. You don’t need to create a private hosted zone or override DNS in the client network. > > - Ensure your network access rules (for example, AWS security groups, Azure NSGs, or GCP firewall rules) on the private endpoint allow inbound TCP on port `443` from your client workload sources only (for example, the client network’s CIDR or specific client access groups). Avoid broad source ranges such as `0.0.0.0/0`. ## [](#test-the-connection)Test the connection You can test the Private Service Connect connection from any VM or container in the consumer VPC. If configuring a client isn’t possible right away, you can do these checks using `rpk` or curl: 1. Set the following environment variables. ```bash export RPK_BROKERS=':30292' export RPK_TLS_ENABLED=true export RPK_SASL_MECHANISM="" export RPK_USER= export RPK_PASS= ``` 2. Create a test topic. ```bash rpk topic create test-topic ``` 3. Produce to the test topic. ### rpk ```bash echo 'hello world' | rpk topic produce test-topic ``` ### curl ```bash curl -s \ -X POST \ "/topics/test-topic" \ -H "Content-Type: application/vnd.kafka.json.v2+json" \ -d '{ "records":[ { "value":"hello world" } ] }' ``` 4. Consume from the test topic. ### rpk ```bash rpk topic consume test-topic -n 1 ``` ### curl ```bash curl -s \ "/topics/test-topic/partitions/0/records?offset=0&timeout=1000&max_bytes=100000"\ -H "Accept: application/vnd.kafka.json.v2+json" ``` ## [](#disable-private-service-connect)Disable Private Service Connect In **Dataplane settings**, click **Disable**. Existing connections are closed after it is disabled. To connect using Private Service Connect again, you must re-enable it.