redpanda-data · micheleRP · Nov 11, 2025 · Nov 12, 2025
@@ -26,6 +26,10 @@
 * xref:networking:index.adoc[Networking]
 ** xref:networking:cloud-security-network.adoc[]
 ** xref:networking:cidr-ranges.adoc[]
+** xref:networking:serverless/index.adoc[Serverless]
+*** xref:networking:byoc/aws/index.adoc[AWS]
+**** xref:networking:serverless/aws/privatelink.adoc[Configure PrivateLink in the Cloud UI]
+**** xref:networking:serverless/aws/privatelink.adoc[Configure PrivateLink with the Cloud API]
 ** xref:networking:byoc/index.adoc[BYOC]
 *** xref:networking:byoc/aws/index.adoc[AWS]
 **** xref:networking:byoc/aws/vpc-peering-aws.adoc[Add a Peering Connection]

@@ -54,7 +54,7 @@ Redpanda Cloud offers three fully-managed cloud deployment options, each designe
 | Up to 112,500
 
 | *Private networking*
-| ✗
+| ✓
 | ✓
 | ✓
 
@@ -168,7 +168,6 @@ Serverless clusters are a good fit for the following use cases:
 
 Consider BYOC or Dedicated if you need more control over the deployment or if you have workloads with consistently-high throughput. BYOC and Dedicated clusters offer the following features:
 
-* Private networking
 * Multiple availability zones (AZs). A multi-AZ cluster provides higher resiliency in the event of a failure in one of the zones. 
 * Ability to export Redpanda metrics to a third-party monitoring system
 * Role-based access control (RBAC) in the data plane

@@ -62,8 +62,12 @@ To create a Serverless cluster:
 . Enter a cluster name, then select the resource group. If you don't have an existing resource group, you can create one. Refresh the page to see newly-created resource groups. 
 +
 Serverless clusters are available in the AWS regions listed in xref:reference:tiers/serverless-regions.adoc[Serverless regions]. Redpanda expects your applications to be deployed in the same AWS region. For best performance, select the region closest to your applications. Serverless is not guaranteed to be pinned to a particular availability zone within that region.
++
+Clusters on AWS can enable private access between their VPC and Redpanda, so data does not traverse the public internet. Private connectivity is implemented using AWS PrivateLink for secure ingress traffic. A Serverless cluster can have both public and private access enabled, although there is an additional charge for private networking. You can enable or disable private access at any time from the cluster's *Settings* page. After private access is disabled, attempts to reach the private endpoints will fail, but the PrivateLink endpoint remains available. This approach provides flexibility to use public access when needed and private access when required.
+
+. Click **Create cluster**.
 
-. Go to the *Topics* page to create a topic. Under the *Actions* dropdown, you can produce messages to it. Add team members and grant them access with ACLs on the *Security* page. 
+. To start working with your cluster, go to the *Topics* page to create a topic. Under the *Actions* dropdown, you can produce messages to it. Add team members and grant them access with ACLs on the *Security* page. 
 
 == Connect with your cluster
 
@@ -92,7 +96,6 @@ Not all features included in BYOC clusters are available in Serverless. For exam
 
 * HTTP Proxy API
 * Ability to export metrics to a third-party monitoring system
-* Private networking (VPC peering or AWS PrivateLink)
 * Multiple availability zones (AZs)
 * RBAC in the data plane and mTLS authentication for Kafka API clients
 * Kafka Connect 

@@ -22,7 +22,7 @@ To create a peering connection between your VPC and Redpanda's VPC:
 
 . In the Redpanda Cloud UI, go to the *Overview* page for your cluster.
 . In the Details section, click the name of the Redpanda network.
-. On the Networks page, click *VPC peering walkthrough*.
+. On the Networking page, click *VPC peering walkthrough*.
 . For *Connection name*, enter a name. For example, the name might refer to the VPC ID of the VPC you created in AWS.
 . For *AWS account number*, enter the account number associated with the VPC you want to connect to.
 . For *AWS VPC ID*, enter the VPC ID by copying it from the AWS VPC Console.

@@ -21,7 +21,7 @@ A peering becomes active after both Redpanda and GCP create a peering that targe
 
 . In the Redpanda Cloud UI, go to the *Overview* page for your cluster.
 . In the Details section, click the name of the Redpanda network.
-. On the Networks page for your cluster, click *VPC peering walkthrough*.
+. On the Networking page for your cluster, click *VPC peering walkthrough*.
 . 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.

@@ -0,0 +1,3 @@
+= AWS
+:description: Learn how to configure private networking for Serverless clusters on AWS. 
+:page-layout: index
@@ -0,0 +1,3 @@
+= Networking: Serverless
+:description: Learn how to configure private networking with AWS PrivateLink. 
+:page-layout: index
@@ -27,7 +27,7 @@ To create a peering connection between your Azure VNet and Redpanda VPC:
 
 . In the Redpanda Cloud UI, go to the *Overview* page for your cluster.
 . In the Details section, click the name of the *Redpanda network*.
-. On the Networks page for your cluster, click *VPC peering walkthrough*.
+. On the Networking page for your cluster, click *VPC peering walkthrough*.
 . For *Connection name*, enter a name. For example, the name could refer to your Azure VNet ID.
 . For *Azure account number*, enter the account number associated with the VNet you want to connect to.
 . For *Azure VNet ID*, enter the VNet ID.