Cloud

Cluster Overview

This reference describes the overview page for BYOC and Serverless clusters in the Redpanda Cloud Console. The overview page is the first place to check the health of a cluster and to copy the connection details that clients need to reach it.

Use this reference to:

  • Locate connection endpoints and the cluster ID on the overview page

  • Locate the source of a cluster health warning

  • Identify which product cards support self-service setup

On Dedicated clusters, the cluster ID is in the Details section of the overview page, and connection URLs are in the How to connect section.

Page header

The header identifies the cluster and summarizes its state:

  • The line above the cluster name shows the cluster type, the network access type (public or private), and the cluster ID. Click the copy icon next to the ID to copy it.

  • Next to the cluster name, a health indicator shows All systems healthy when everything is running normally. When a product reports a problem, a Needs attention indicator appears instead. See Health and warnings.

  • Header stats show the cloud provider and region, the availability zones, and the network name.

  • The Get started menu opens quickstart shortcuts, such as connecting data sources, streaming from the command line, and querying streams with SQL.

Health and warnings

When one or more products on the cluster report a problem, the Needs attention indicator next to the cluster name expands into an entry for each affected product with a count of its issues. Click an entry to jump to that product’s card and open its Needs attention section, which describes each issue in detail.

Product cards also show status badges, such as Unavailable, Metrics unavailable, or Awaiting metrics, when a product or its metrics cannot be reached.

On clusters with private networking, live product stats are read from inside the cluster’s network. To see them, open the page from a host connected to your private network.

How to connect

The How to connect panel lists the details clients need to reach the cluster:

  • Streaming: bootstrap servers, Schema Registry endpoint, HTTP Proxy endpoint (BYOC only), Admin API endpoint, Redpanda Console URL, and the supported SASL mechanisms.

  • SQL (shown when Redpanda SQL is enabled): connection details for the PostgreSQL-compatible SQL engine.

  • Prometheus: the metrics endpoint and scrape configuration for monitoring tools. See Monitor Redpanda Cloud.

The endpoints shown reflect your cluster’s network configuration: on a cluster with private networking, the panel lists private endpoints, which are reachable only from inside your connected network. On Serverless clusters with private access enabled, the private bootstrap URL and private Schema Registry endpoint appear alongside the public ones.

On Serverless clusters, the Manage credentials link on the Streaming tab opens the cluster’s security pages, where you manage users and ACLs.

Product cards

Each product on the cluster has a card summarizing its status:

  • Redpanda Streaming: broker count, topics, client connections, and recent throughput, with an expandable list of the largest topics.

  • Redpanda Connect: pipeline status. Expand Pipelines to see each pipeline’s input, output, and state.

  • Iceberg Topics: table count, rows per hour, backlog, and dead letter queue rows, plus storage and catalog details.

  • Redpanda SQL: engine status, active sessions, queries per minute, and node count.

  • Shadow link: status of shadow links that mirror topics from another cluster.

Serverless clusters show the Redpanda Streaming and Redpanda Connect cards. The other cards appear on BYOC clusters. The card states described on this page apply to both cluster types.

If a product is not yet set up on the cluster, its card explains what the product does and why you might want it, links to the product’s documentation, and shows the next step:

  • If you can set up or enable the product yourself, the card offers the action directly: create a Redpanda Connect pipeline, enable or materialize an Iceberg topic, enable Redpanda SQL, or create a shadow link.

  • If your role does not allow enabling the product, the card tells you to ask an administrator of your organization.

  • If the product is not included in the cluster’s plan, the card says so and links to the plan limits.

Network card

BYOC clusters show a card named for the cluster’s network access: Private network, Public network, or BYOVPC network. The card provides:

  • Private connectivity options for the cluster’s cloud provider: AWS PrivateLink, AWS Transit Gateway, and VPC peering on AWS; Azure Private Link and VNet peering on Azure; Private Service Connect and VPC peering on GCP. Configured connections appear as tiles with their status, and the card offers setup actions where configuration through the Console is supported. See Redpanda Cloud Networking.

  • Connect to your network: network details for configuring connectivity from your side, including the Redpanda network name, CIDR range, and NAT gateways.

  • Manage network: opens the Redpanda network page.

Serverless clusters show a card named for the cluster’s network access: Private network or Public network. Private connectivity for Serverless clusters is available on AWS only, through AWS PrivateLink. When a private link is configured, the card shows its status, endpoint service name, region, number of permitted principals, and availability zones. To set up private access on a Serverless cluster on AWS, click Enable private access, which opens the cluster’s Dataplane settings page. See Configure AWS PrivateLink in the Cloud Console.

See also