redpanda-data · micheleRP · Nov 11, 2025 · Nov 12, 2025 · Jan 14, 2026 · Jan 14, 2026
@@ -26,31 +26,35 @@
 * xref:networking:index.adoc[Networking]
 ** xref:networking:cloud-security-network.adoc[]
 ** xref:networking:cidr-ranges.adoc[]
+** xref:networking:serverless/index.adoc[Serverless]
+*** xref:networking:serverless/aws/index.adoc[AWS]
+**** xref:networking:serverless/aws/privatelink-ui.adoc[Configure PrivateLink in the Cloud Console]
+**** xref:networking:serverless/aws/privatelink-api.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]
-**** xref:networking:configure-privatelink-in-cloud-ui.adoc[Configure PrivateLink in the Cloud UI]
+**** xref:networking:configure-privatelink-in-cloud-ui.adoc[Configure PrivateLink in the Cloud Console]
 **** xref:networking:aws-privatelink.adoc[Configure PrivateLink with the Cloud API]
 **** xref:networking:byoc/aws/transit-gateway.adoc[Add a Transit Gateway]
 *** xref:networking:byoc/azure/index.adoc[Azure]
 **** xref:networking:azure-private-link-in-ui.adoc[]
 **** xref:networking:azure-private-link.adoc[]
 *** xref:networking:byoc/gcp/index.adoc[GCP]
 **** xref:networking:byoc/gcp/vpc-peering-gcp.adoc[Add a Peering Connection]
-**** xref:networking:configure-private-service-connect-in-cloud-ui.adoc[Configure Private Service Connect in the Cloud UI]
+**** xref:networking:configure-private-service-connect-in-cloud-ui.adoc[Configure Private Service Connect in the Cloud Console]
 **** xref:networking:gcp-private-service-connect.adoc[Configure Private Service Connect with the Cloud API]
 **** xref:networking:byoc/gcp/enable-global-access.adoc[Enable Global Access]
 ** xref:networking:dedicated/index.adoc[Dedicated]
 *** xref:networking:dedicated/aws/index.adoc[AWS]
 **** xref:networking:dedicated/aws/vpc-peering.adoc[Add a Peering Connection]
-**** xref:networking:configure-privatelink-in-cloud-ui.adoc[Configure PrivateLink in the Cloud UI]
+**** xref:networking:configure-privatelink-in-cloud-ui.adoc[Configure PrivateLink in the Cloud Console]
 **** xref:networking:aws-privatelink.adoc[]
 *** xref:networking:dedicated/azure/index.adoc[Azure]
-**** xref:networking:azure-private-link-in-ui.adoc[]
+**** xref:networking:azure-private-link-in-ui.adoc[Configure Private Link in the Cloud Console]
 **** xref:networking:azure-private-link.adoc[]
 *** xref:networking:dedicated/gcp/index.adoc[GCP]
 **** xref:networking:dedicated/gcp/vpc-peering-gcp.adoc[Add a Peering Connection]
-**** xref:networking:dedicated/gcp/configure-psc-in-ui.adoc[Configure Private Service Connect in the Cloud UI]
+**** xref:networking:dedicated/gcp/configure-psc-in-ui.adoc[Configure Private Service Connect in the Cloud Console]
 **** xref:networking:dedicated/gcp/configure-psc-in-api.adoc[Configure Private Service Connect with the Cloud API]
 
 * xref:security:index.adoc[Security]

@@ -59,7 +59,7 @@ Redpanda Cloud offers three fully-managed cloud deployment options, each designe
 | 20 (default), 32 (max)
 
 | *Private networking*
-| ✗
+| ✓
 | ✓
 | ✓
 
@@ -118,7 +118,6 @@ Serverless is the fastest and easiest way to start data streaming. With Serverle
 
 [NOTE]
 ====
-* Serverless on AWS is currently in a glossterm:LA[,limited availability (LA)] release. 
 * Serverless on GCP is currently in a glossterm:beta[] release. 
 ====
 
@@ -177,7 +176,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. 
 * Role-based access control (RBAC) in the data plane
 * Kafka Connect
@@ -382,7 +380,6 @@ Features in limited availability are production-ready and are covered by Redpand
 
 The following features are currently in limited availability in Redpanda Cloud:
 
-* Serverless
 * Dedicated for Azure
 
 == Features in beta

@@ -7,7 +7,6 @@ Serverless is the fastest and easiest way to start data streaming. With Serverle
 
 [NOTE]
 ====
-* Serverless on AWS is currently in a glossterm:LA[,limited availability (LA)] release.
 * Serverless on GCP is currently in a glossterm:beta[] release. 
 
 ====
@@ -50,9 +49,15 @@ To create a Serverless cluster:
 
 . Select a cloud provider and xref:reference:tiers/serverless-regions.adoc[region]. For best performance, select the region closest to your applications. Redpanda expects your applications to be deployed in the same cloud provider and region as your Serverless cluster. 
 +
-Serverless clusters are not guaranteed to be pinned to a particular availability zone within the selected region.
+Serverless clusters are available in the regions listed in xref:reference:tiers/serverless-regions.adoc[Serverless regions]. Redpanda expects your applications to be deployed in the same 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. Enabling private access incurs additional charges. If you select private access, you can either create a new PrivateLink, or, if you have PrivateLinks for other Serverless clusters in this same resource group, you can use an existing PrivateLink. 
++
+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. However, the PrivateLink endpoint remains provisioned and continues to incur charges until you explicitly delete it from your AWS account.
+
+. Click **Create cluster**.
 
-. Add team members and grant them access with glossterm:ACL[,access control lists (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. 
 
 == Interact with your cluster
 
@@ -89,7 +94,6 @@ Explore the rest of the UI:
 Not all features included in BYOC clusters are available in Serverless. For example, the following features are not supported:
 
 * HTTP Proxy API
-* 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 

@@ -6,6 +6,12 @@
 
 This page lists new features added to Redpanda Cloud.
 
+== January 2026
+
+=== Serverless on AWS: GA
+
+xref:get-started:cluster-types/serverless.adoc[Serverless] on AWS is now generally available (GA). This GA release includes private networking with AWS PrivateLink and the ability to view and export metrics from Serverless clusters to third-party monitoring systems.
+
 == December 2025
 
 === Remote MCP: GA

@@ -1,7 +1,7 @@
-= Configure Azure Private Link in the Cloud UI
-:description: Set up Azure Private Link in the Redpanda Cloud UI.
+= Configure Azure Private Link in the Cloud Console
+:description: Set up Azure Private Link in the Redpanda Cloud Console.
 
-NOTE: This guide is for configuring new clusters with Azure Private Link using the Redpanda Cloud UI. To configure and manage Private Link on an existing cluster, you must use the xref:networking:azure-private-link.adoc[Cloud API].
+NOTE: This guide is for configuring new clusters with Azure Private Link using the Redpanda Cloud Console. To configure and manage Private Link on an existing cluster, you must use the xref:networking:azure-private-link.adoc[Cloud API].
 
 The Redpanda Azure Private Link service provides secure access to Redpanda Cloud from your own VNet. Traffic over Private Link does not go through the public internet because these connections are treated as their own private Azure service. While your VNet has access to the Redpanda virtual network, Redpanda cannot access your VNet.
 
@@ -19,7 +19,7 @@ TIP: In Kafka clients, set `connections.max.idle.ms` to a value less than 350 se
 
 == Enable endpoint service for new clusters
 
-. In the Redpanda Cloud UI, create a new cluster.
+. In the Redpanda Cloud Console, create a new cluster.
 . On the *Networking* page:
 .. For *Connection type*, select *Private*.
 .. For *Azure Private Link*, select *Enabled*.

@@ -1,7 +1,7 @@
 = Configure Azure Private Link with the Cloud API
 :description: Set up Azure Private Link with the Cloud API.
 
-NOTE: For UI-based configuration of Azure Private Link on new clusters, see xref:networking:azure-private-link-in-ui.adoc[Configure Azure Private Link in the Cloud UI].
+NOTE: For UI-based configuration of Azure Private Link on new clusters, see xref:networking:azure-private-link-in-ui.adoc[Configure Azure Private Link in the Cloud Console].
 
 The Redpanda Azure Private Link service provides secure access to Redpanda Cloud from your own virtual network. Traffic over Azure Private Link does not go through the public internet, but instead through Microsoft's backbone network. While clients can initiate connections against the Redpanda Cloud cluster endpoints, Redpanda Cloud services cannot access your virtual networks directly.
 
@@ -52,7 +52,7 @@ If you have not yet created a cluster in Redpanda Cloud, <<create-new-cluster-wi
 
 === Create new cluster with Private Link service enabled
 
-. In the Redpanda Cloud UI, go to https://cloud.redpanda.com/resource-groups[**Resource groups**^] and select the Redpanda Cloud resource group in which you want to create a cluster.
+. In the Redpanda Cloud Console, go to https://cloud.redpanda.com/resource-groups[**Resource groups**^] and select the Redpanda Cloud resource group in which you want to create a cluster.
 +
 NOTE: Redpanda Cloud resource groups exist in your Redpanda Cloud account only. They do not correspond to Azure resource groups and do not appear in your Azure tenant.
 +
@@ -158,7 +158,7 @@ rpk cloud byoc azure apply --redpanda-id=$CLUSTER_ID --subscription-id=$REDPANDA
 
 CAUTION: Enabling Private Link on your VNet interrupts all communication on existing Redpanda bootstrap server and broker ports due to the change of private DNS resolution. Make sure all applications running in your virtual network are ready to start using the corresponding Private Link ports.
 
-. In the Redpanda Cloud UI, go to the cluster overview and copy the cluster ID from the **Details** section.
+. In the Redpanda Cloud Console, go to the cluster overview and copy the cluster ID from the **Details** section.
 +
 [,bash]
 ----
@@ -189,7 +189,7 @@ curl -vv -X PATCH \
 
 == Configure Azure Private Link connection to Redpanda Cloud
 
-. In the Redpanda Cloud UI, go to https://cloud.redpanda.com/users?tab=users[**Users**^] and create a new user to authenticate the Private Link endpoint connections with the service. You will need the username and password to <<connect-to-redpanda-services-through-private-link-endpoints,access Redpanda services>> or <<test-the-connection,test the connection>> using `rpk` or cURL.
+. In the Redpanda Cloud Console, go to https://cloud.redpanda.com/users?tab=users[**Users**^] and create a new user to authenticate the Private Link endpoint connections with the service. You will need the username and password to <<connect-to-redpanda-services-through-private-link-endpoints,access Redpanda services>> or <<test-the-connection,test the connection>> using `rpk` or cURL.
 
 . Call the link:/api/doc/cloud-controlplane/operation/operation-clusterservice_getcluster[`GET /v1/clusters/\{id}`] endpoint to check the service status and retrieve the service ID, DNS name, and Redpanda Console URL to use.
 +
@@ -288,7 +288,7 @@ az network private-dns record-set a add-record \
 
 == Connect to Redpanda services through Private Link endpoints
 
-After you enable Private Link for your cluster, your connection URLs are available in the *How to Connect* section of the cluster overview in the Redpanda Cloud UI.
+After you enable Private Link for your cluster, your connection URLs are available in the *How to Connect* section of the cluster overview in the Redpanda Cloud Console.
 
 include::networking:partial$private-links-access-rp-services-through-vpc.adoc[]
 

@@ -1,8 +1,8 @@
-= Configure AWS PrivateLink in the Cloud UI
-:description: Set up AWS PrivateLink in the Redpanda Cloud UI.
+= Configure AWS PrivateLink in the Cloud Console
+:description: Set up AWS PrivateLink in the Redpanda Cloud Console.
 :page-aliases: deploy:deployment-option/cloud/configure-privatelink-in-cloud-ui.adoc
 
-NOTE: This guide is for configuring AWS PrivateLink using the Redpanda Cloud UI. To configure and manage PrivateLink on an existing public cluster, you must use the xref:networking:aws-privatelink.adoc[Redpanda Cloud API].
+NOTE: This guide is for configuring AWS PrivateLink using the Redpanda Cloud Console. To configure and manage PrivateLink on an existing public cluster, you must use the xref:networking:aws-privatelink.adoc[Redpanda Cloud API].
 
 The Redpanda AWS PrivateLink endpoint service provides secure access to Redpanda Cloud from your own VPC. Traffic over PrivateLink does not go through the public internet because these connections are treated as their own private AWS service. While your VPC has access to the Redpanda VPC, Redpanda cannot access your VPC.
 
@@ -29,7 +29,7 @@ include::networking:partial$dns_resolution.adoc[]
 
 == Enable endpoint service for existing clusters
 
-. In the Redpanda Cloud UI, select your https://cloud.redpanda.com/clusters[cluster^], and go to the *Cluster settings* page.
+. In the Redpanda Cloud Console, select your https://cloud.redpanda.com/clusters[cluster^], and go to the *Cluster settings* page.
 . For AWS PrivateLink, click *Enable*.
 . On the Enable PrivateLink page, for Allowed principal ARNs, click *Add*, and enter the Amazon Resource Names (ARNs) for each AWS principal allowed to access the endpoint service. For example, for all principals in a specific account, use `arn:aws:iam::<account-id>:root`. See the AWS documentation on https://docs.aws.amazon.com/vpc/latest/privatelink/configure-endpoint-service.html#add-remove-permission[configuring an endpoint service^] for details. 
 . Click *Add* after entering each ARN, and when finished, click *Enable*. 
@@ -39,7 +39,7 @@ NOTE: For help with issues when enabling PrivateLink, contact https://support.re
 
 == Access Redpanda services through VPC endpoint
 
-After you have enabled PrivateLink for your cluster, your connection URLs are available in the *How to Connect* section of the cluster overview in the Redpanda Cloud UI.
+After you have enabled PrivateLink for your cluster, your connection URLs are available in the *How to Connect* section of the cluster overview in the Redpanda Cloud Console.
 
 include::networking:partial$private-links-access-rp-services-through-vpc.adoc[]
 

@@ -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.

@@ -6,7 +6,7 @@ include::networking:partial$psc-api.adoc[]
 
 == Create a new cluster with Private Service Connect
 
-. In the https://cloud.redpanda.com/[Redpanda Cloud UI], go to **Resource groups** and select the resource group in which you want to create a cluster.
+. In the https://cloud.redpanda.com/[Redpanda Cloud Console], go to **Resource groups** and select the resource group in which you want to create a cluster.
 +
 Copy and store the resource group ID (UUID) from the URL in the browser.
 +
@@ -104,7 +104,7 @@ Enabling Private Service Connect on your VPC interrupts all communication on exi
 To avoid disruption, consider using a staged approach. See: xref:networking:dedicated/gcp/vpc-peering-gcp.adoc#switch-from-vpc-peering-to-private-service-connect[Switch from VPC peering to Private Service Connect].
 ====
 
-. In the Redpanda Cloud UI, go to the cluster overview and copy the cluster ID from the **Details** section.
+. In the Redpanda Cloud Console, go to the cluster overview and copy the cluster ID from the **Details** section.
 +
 [,bash]
 ----

@@ -1,11 +1,11 @@
-= Configure GCP Private Service Connect in the Cloud UI
-:description: Set up GCP Private Service Connect in the Redpanda Cloud UI.
+= Configure GCP Private Service Connect in the Cloud Console
+:description: Set up GCP Private Service Connect in the Redpanda Cloud Console.
 :env-dedicated: true
 
 [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 xref:networking:gcp-private-service-connect.adoc[Cloud API for BYOC] or the xref:networking:dedicated/gcp/configure-psc-in-api.adoc[Cloud API for Dedicated].
+* This guide is for configuring GCP Private Service Connect using the Redpanda Cloud Console. To configure and manage Private Service Connect on an existing cluster with *public* networking, you must use the xref:networking:gcp-private-service-connect.adoc[Cloud API for BYOC] or the xref:networking:dedicated/gcp/configure-psc-in-api.adoc[Cloud API for Dedicated].
 * The latest version of Redpanda GCP Private Service Connect (available March, 2025) supports AZ 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 xref:manage:maintenance.adoc#deprecated-features[Deprecated features].
 ==== 
@@ -30,7 +30,7 @@ Consider using Private Service Connect if you have multiple VPC networks and cou
 
 == Enable Private Service Connect for existing clusters
 
-. In the Redpanda Cloud UI, open your https://cloud.redpanda.com/clusters[cluster^], and click **Cluster settings**.
+. In the Redpanda Cloud Console, open your https://cloud.redpanda.com/clusters[cluster^], and click **Cluster settings**.
 . Under Private Service Connect, click **Enable**. 
 ifdef::env-byoc[]
 . For xref:get-started:cluster-types/byoc/gcp/vpc-byo-gcp.adoc[BYOVPC clusters], you need a 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:

@@ -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