redpanda-data · micheleRP · Feb 2, 2026 · Nov 11, 2025 · Nov 12, 2025 · Jan 14, 2026
@@ -329,7 +329,6 @@
 *** xref:develop:connect/guides/sync_responses.adoc[]
 *** xref:develop:connect/guides/migrate-unified-redpanda-migrator.adoc[]
 
-
 ** xref:develop:connect/cookbooks/index.adoc[]
 *** xref:develop:connect/cookbooks/enrichments.adoc[]
 *** xref:develop:connect/cookbooks/filtering.adoc[]
@@ -437,31 +436,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

@@ -25,7 +25,7 @@ To verify access, you should be able to successfully run `aws sts get-caller-ide
 == Create a BYOC cluster
 
 . Log in to https://cloud.redpanda.com[Redpanda Cloud^].
-. On the Clusters page, click *Create cluster*, then click *Create BYOC cluster*. 
+. On the Clusters page, click *Create cluster*, then click *Create* for BYOC. 
 . Enter a cluster name, then select the resource group, provider (AWS), xref:reference:tiers/byoc-tiers.adoc[region, tier], availability, and Redpanda version.
 +
 [NOTE]

@@ -149,7 +149,7 @@ If you see restrictions, https://learn.microsoft.com/en-us/troubleshoot/azure/ge
 To create a Redpanda cluster in your Azure VNet, follow the <<prerequisites,prerequisites>> then follow the instructions in the Redpanda Cloud UI. The UI contains the parameters necessary to successfully run `rpk cloud byoc apply`.  
 
 . Log in to https://cloud.redpanda.com[Redpanda Cloud^].
-. On the Clusters page, click *Create cluster*, then click *Create BYOC cluster*.
+. On the Clusters page, click *Create cluster*, then click *Create* for BYOC.
 . Enter a cluster name, then select the resource group, provider (Azure), xref:reference:tiers/byoc-tiers.adoc[region, tier], availability, and Redpanda version. 
 +
 [NOTE]

@@ -15,7 +15,7 @@ include::partial$gpq-quotas.adoc[]
 == Create a BYOC cluster
 
 . Log in to https://cloud.redpanda.com[Redpanda Cloud^].
-. On the Clusters page, click *Create cluster*, then click *Create BYOC cluster*.
+. On the Clusters page, click *Create cluster*, then click *Create* for BYOC.
 +
 Enter a cluster name, then select the resource group, provider (GCP), xref:reference:tiers/byoc-tiers.adoc[region, tier], availability, and Redpanda version.
 +

@@ -6,7 +6,7 @@ After you log in to https://cloud.redpanda.com[Redpanda Cloud^], you land on the
 
 == Create a Dedicated cluster
 
-. On the Clusters page, click *Create cluster*, then click *Create Dedicated cluster*.
+. On the Clusters page, click *Create cluster*, then click *Create* for Dedicated.
 +
 Enter a cluster name, then select the resource group, cloud provider (AWS, GCP, or Azure), xref:reference:tiers/dedicated-tiers.adoc[region, tier], availability, and Redpanda version.
 +

@@ -7,8 +7,7 @@ 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. 
+Serverless on GCP is currently in a glossterm:beta[] release. 
 
 ====
 
@@ -44,15 +43,26 @@ include::get-started:partial$get-started-serverless.adoc[]
 
 To create a Serverless cluster: 
 
-. In the https://cloud.redpanda.com[Redpanda Cloud UI^], on the **Clusters** page, click **Create cluster**, then click **Create Serverless cluster**. 
+. In the https://cloud.redpanda.com[Redpanda Cloud Console^], on the **Clusters** page, click **Create cluster**, then click **Create** for Serverless. 
 
-. 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. 
+. 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. 
 
 . 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.
+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 traffic.
++
+** When you enable both public access and private access on the cluster, you can choose between the public address or the private address. When the public address is used the data flows over the public internet.
+** You can either create a new PrivateLink or use an existing one from the same resource group.
+** You can enable or disable private access at any time on the cluster's *Settings* page. 
+** Enabling private access incurs additional charges.
++
+NOTE: After private access is disabled, attempts to reach the private endpoints will fail. However, the PrivateLink endpoint in your AWS account and the PrivateLink resource in Redpanda Cloud both remain provisioned and continue to incur charges until you explicitly delete them.     
+
+. 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 and produce messages to it. Add team members and grant them access with ACLs on the *Security* page. 
 
 == Interact with your cluster
 
@@ -62,7 +72,7 @@ The *Overview* page lists your bootstrap server URL and security settings in the
 
 Or, Redpanda can generate a sample application to interact with your cluster. Run xref:reference:rpk/rpk-generate/rpk-generate-app.adoc[`rpk generate app`], and select Go as the language. Follow the commands in the terminal to run the application, create a demo topic, produce to the topic, and consume the data back.
 
-Follow the steps in the UI to use `rpk` to interact with your cluster from the command line. Here are some helpful commands:
+Follow the steps in the Console to use `rpk` to interact with your cluster from the command line. Here are some helpful commands:
 
 * xref:reference:rpk/rpk-cloud/rpk-cloud-login.adoc[`rpk cloud login`]: Use this to log in to Redpanda Cloud or to refresh the session.
 * xref:reference:rpk/rpk-topic.adoc[`rpk topic`]: Use this to manage topics, produce data, and consume data. 
@@ -71,31 +81,23 @@ Follow the steps in the UI to use `rpk` to interact with your cluster from the c
 
 NOTE: Redpanda Serverless is opinionated about Kafka configurations. For example, automatic topic creation is disabled. Some systems expect the Kafka service to automatically create topics when a message is produced to a topic that doesn't exist. Create topics on the *Topics* page or with `rpk topic create`.
 
-The *How to connect - Kafka API* tab lists your bootstrap server URL and security settings. This area includes code examples for creating a Kafka client to interact with your cluster. Or, Redpanda can generate a sample application to interact with your cluster. Run xref:reference:rpk/rpk-generate/rpk-generate-app.adoc[`rpk generate app`], and select your preferred programming language. Follow the commands in the terminal to run the application, create a demo topic, produce to the topic, and consume the data back.
-
-Explore the rest of the UI: 
-
-* Go to the *Topics* page to create new topics for data streams. 
-* Under the *Actions* dropdown, produce messages to topics. 
-* Add team members with permissions on the *Security* page.
-
 == Supported features
 
 * Redpanda Serverless supports the Kafka API. Serverless clusters work with all Kafka clients. See xref:develop:kafka-clients.adoc[].
-* Serverless clusters support all major Apache Kafka messages for managing topics, producing/consuming data (including transactions), managing groups, managing offsets, and managing ACLs. (User management is available in the Redpanda Cloud UI or with `rpk security acl`.) 
+* Serverless clusters support all major Apache Kafka messages for managing topics, producing/consuming data (including transactions), managing groups, managing offsets, and managing ACLs. (User management is available in the https://cloud.redpanda.com[Redpanda Cloud Console^] or with `rpk security acl`.) 
 
 === Unsupported features
 
 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 
 
 == Next steps
 
+* xref:networking:serverless/aws/index.adoc[Set up private access for Serverless clusters]
 * xref:get-started:cloud-overview.adoc[Learn more about Redpanda Cloud]
 * xref:get-started:config-topics.adoc[Manage topics]
 * xref:billing:billing.adoc[Learn about billing]
@@ -6,6 +6,12 @@
 
 This page lists new features added to Redpanda Cloud.
 
+== February 2026
+
+=== Serverless on AWS: GA
+
+xref:get-started:cluster-types/serverless.adoc[Serverless] on AWS is now generally available (GA). This release includes private networking with AWS PrivateLink and the ability to export metrics to third-party monitoring systems. Serverless is the easiest and fastest way to begin streaming data with Redpanda. Start small and iterate on a budget, with confidence that your cluster can scale to production.
+
 == January 2026
 
 === Redpanda Connect updates
@@ -21,6 +27,7 @@ This page lists new features added to Redpanda Cloud.
 
 The xref:manage:terraform-provider.adoc[Redpanda Terraform provider] now supports managing roles and Redpanda Connect pipelines. Use the provider to create and manage role-based access control and data pipelines in Redpanda Cloud.
 
+
 == December 2025
 
 === Remote MCP: GA

@@ -5,15 +5,15 @@ Free trial::
 --
 A https://www.redpanda.com/try-redpanda[free trial on AWS^] is the fastest way to get started with Serverless. Each free-trial customer qualifies for $100 (USD) in credits to spend in the first 14 days. This should be enough to run Redpanda with reasonable throughput. No credit card is required. To continue using Serverless after your trial expires, you can enter a credit card and pay as you go. Any remaining credit balance is used before you are charged. 
 
-When either the credits expire or the days in the trial expire, the clusters move into a suspended state, and you won't be able to access your data in either the Redpanda Cloud UI or with the Kafka API. There is a seven-day grace period following the end of the trial. After that, the data is permanently deleted. For questions about the trial, use the *#serverless* https://redpandacommunity.slack.com/[Community Slack^] channel.
+When either the credits expire or the days in the trial expire, the clusters move into a suspended state, and you won't be able to access your data in either the Redpanda Cloud Console or with the Kafka API. There is a seven-day grace period following the end of the trial when you can add your credit card and restore service. After that, the data is permanently deleted. For questions about the trial, use the *#serverless* https://redpandacommunity.slack.com/[Community Slack^] channel.
 
 After you start a trial, Redpanda instantly prepares an account for you. Your account includes a `welcome` cluster with a `hello-world` demo topic you can explore. It includes sample data so you can see how real-time messaging works before sending your own data.
 
-xref:get-started:cluster-types/serverless.adoc#interact-with-your-cluster[Get started] by following the wizard to create a Redpanda Connect glossterm:pipeline[], or by following the steps in the UI to use `rpk` to interact with your cluster from the command line:
+xref:get-started:cluster-types/serverless.adoc#interact-with-your-cluster[Get started] by following the wizard to create a Redpanda Connect glossterm:pipeline[], or by following the steps in the Console to use `rpk` to interact with your cluster from the command line:
 
 . Log in with `rpk cloud login`.
 . Consume from the `hello-world` topic with `rpk topic consume hello-world`.
-. In the https://cloud.redpanda.com[Redpanda Cloud UI^], navigate to the *Topics* page and open the `hello-world` topic to see the included messages. 
+. In the https://cloud.redpanda.com[Redpanda Cloud Console^], navigate to the *Topics* page and open the `hello-world` topic to see the included messages. 
 
 --
 Redpanda Sales::

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