Merge branch 'update-cloud-overview-adp-focus' into adp-pkg1

# Conflicts:
#	local-antora-playbook.yml
#	modules/get-started/pages/cloud-overview.adoc
#	modules/get-started/pages/whats-new-cloud.adoc

Author: paulohtb6

modules/ROOT/nav.adoc

@@ -382,7 +382,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[]
@@ -464,6 +463,7 @@
 *** xref:manage:schema-reg/schema-reg-ui.adoc[]
 *** xref:manage:schema-reg/schema-reg-api.adoc[]
 *** xref:manage:schema-reg/schema-reg-authorization.adoc[Schema Registry Authorization]
+*** xref:manage:schema-reg/schema-id-validation.adoc[]
 *** xref:manage:schema-reg/record-deserialization.adoc[Deserialization]
 *** xref:manage:schema-reg/programmable-push-filters.adoc[Programmable Push Filters]
 *** xref:manage:schema-reg/edit-topic-configuration.adoc[Edit Topic Configuration]
@@ -491,31 +491,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]

modules/get-started/pages/cloud-overview.adoc

@@ -6,15 +6,15 @@ Redpanda Cloud is a complete data streaming and agentic data plane platform deli
 
 == Redpanda Agentic Data Plane (ADP)
 
-Redpanda ADP is an enterprise-grade infrastructure for building, deploying, and managing AI agents at scale. Redpanda ADP provides unified governance, observability, and security for agentic applications while leveraging Redpanda's streaming and analytical capabilities as the foundational data fabric.
+Redpanda ADP is an enterprise-grade infrastructure for building, deploying, and managing AI agents at scale. Redpanda ADP provides unified governance, observability, and security for agentic applications while leveraging Redpanda's streaming and analytical foundation.
 
 NOTE: The Agentic Data Plane is supported on BYOC clusters running with AWS and Redpanda version 25.3 and later.
 
 Redpanda ADP is built on open standards and protocols, allowing you to pick and choose components that fit your needs. Integrate with existing agent frameworks, data processing systems, or custom code. It includes the following key components:
 
-* **AI agents**: Deploy declarative agents or bring your own agent frameworks (LangChain, LlamaIndex, and others). Build multi-agent systems where specialized sub-agents handle specific responsibilities, following single-responsibility principles.
-* **MCP servers**: Build lightweight data and action interfaces using a low-code framework based on xref:develop:connect/about.adoc[Redpanda Connect]. Connect to hundreds of data sources (databases, cloud storage, APIs) and enforce fine-grained policies that programmatically prevent prompt injection and SQL injection attacks. MCP servers are extremely lightweight—run dozens on minimal resources—with OIDC-based access control and real-time debugging capabilities.
-* **AI Gateway**: Manage LLM provider access with cost controls, rate limiting, intelligent routing, and failover support across multiple providers.
+* **glossterm:AI agent[,AI agents]**: Deploy declarative agents or bring your own agent frameworks (such as LangChain or LlamaIndex). Build multi-agent systems where specialized glossterm:subagent[,sub-agents] handle specific responsibilities, following single-responsibility principles.
+* **glossterm:MCP server[,MCP servers]**: Build lightweight data and action interfaces using xref:develop:connect/about.adoc[Redpanda Connect] or your own hosted MCP servers. Connect to hundreds of data sources (databases, cloud storage, APIs) and enforce fine-grained policies that programmatically prevent prompt injection and SQL injection attacks. MCP servers are extremely lightweight, with OIDC-based access control and real-time debugging capabilities.
+* **AI Gateway**: Manage large language model (LLM) provider access with cost controls, rate limiting, intelligent routing, and failover support across multiple providers.
 //* **Catalog**: Maintain a centralized repository of agents, MCP servers, tools, and policies. Share components across teams and enforce organization-wide standards.
 
 === Enterprise capabilities for AI agents
@@ -25,13 +25,8 @@ Redpanda ADP addresses critical enterprise requirements for AI agent deployments
 
 *Unified authorization*: All components use OIDC-based authentication with an "on-behalf-of" authorization model. When a user invokes an agent, the agent inherits the intersection of its own permissions and the user's permissions, ensuring proper data access scoping.
 
-*Complete observability*: Redpanda ADP provides two levels of inspection: execution logs (transcripts) capture every agent action with 100% sampling using OpenTelemetry standards, while real-time debugging tools allow inspection of individual MCP server calls. Traces span across services and go as deep as needed, down to individual tool invocations with full timing data. View detailed agent actions in Redpanda Console and replay data for agent evaluations.
+*Complete observability*: Redpanda ADP provides two levels of inspection: execution logs (glossterm:transcript[,transcripts]) capture every agent action with 100% sampling using OpenTelemetry standards, while real-time debugging tools allow inspection of individual MCP server calls. Traces span across services and go as deep as needed, down to individual tool invocations with full timing data. View detailed agent actions in Redpanda Console and replay data for agent evaluations.
 
-*Compliance and audit*: For industries requiring multi-year audit trails, Redpanda ADP records every agent action and data source used in decision-making. Execution logs are stored in Redpanda topics and can be materialized to Iceberg tables for long-term retention and analysis.
-
-=== Use cases
-
-Organizations can use Redpanda ADP to:
 
 * *Automate operational workflows*: Create specialized agents for building management, infrastructure monitoring, compliance reporting, and other domain-specific tasks
 * *Monitor manufacturing and operations*: Deploy multi-agent systems that analyze factory machine telemetry in real-time, detect anomalies, search equipment manuals, and create maintenance tickets automatically. Use data aggregation patterns (like tumbling windows) to process high-volume sensor data before sending insights to agents.
@@ -156,7 +151,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. 
 ====
 

modules/get-started/pages/cluster-types/byoc/aws/create-byoc-cluster-aws.adoc

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

modules/get-started/pages/cluster-types/byoc/azure/create-byoc-cluster-azure.adoc

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

modules/get-started/pages/cluster-types/byoc/gcp/create-byoc-cluster-gcp.adoc

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

modules/get-started/pages/cluster-types/create-dedicated-cloud-cluster.adoc

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

modules/get-started/pages/cluster-types/serverless.adoc

@@ -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,24 @@ 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:manage:terraform-provider.adoc[Manage Redpanda Cloud with Terraform]
 * 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]