You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/develop/pages/managed-connectors/create-iceberg-sink-connector.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Before you can create an Iceberg Sink connector in Redpanda Cloud, you
22
22
must:
23
23
24
24
. https://iceberg.apache.org/concepts/catalog/[Set up an Iceberg catalog^].
25
-
. Create the Iceberg connector control topic, which cannot be used by other connectors. For details, see xref:get-started:create-topic.adoc[Create a Topic].
25
+
. Create the Iceberg connector control topic, which cannot be used by other connectors. For details, see xref:develop:topics/create-topic.adoc[Create a Topic].
Redpanda Cloud requires a minimum of 3 topic replicas. If a topic is created with a replication factor of 1, Redpanda resets the replication factor to 3.
27
+
Redpanda Cloud requires a minimum of 3 topic replicas. If a topic is created with a replication factor of 1, Redpanda resets the replication factor to 3.
28
28
29
29
| *Cleanup policy*
30
-
| The policy that determines how to clean up old log segments.
30
+
| The policy that determines how to clean up old log segments.
31
31
32
32
The default is *delete*.
33
33
34
34
| *Retention time*
35
-
| The maximum length of time to keep messages in a topic.
35
+
| The maximum length of time to keep messages in a topic.
36
36
37
37
The default is *7 days*.
38
38
39
39
| *Retention size*
40
-
| The maximum size of each partition. If a partition reaches this size and more messages are added, the oldest messages are deleted.
40
+
| The maximum size of each partition. If a partition reaches this size and more messages are added, the oldest messages are deleted.
41
41
42
42
The default is *infinite*.
43
43
44
44
| *Message size*
45
-
| The maximum size of a message or batch for a newly-created topic.
45
+
| The maximum size of a message or batch for a newly-created topic.
46
46
47
47
The default is *20 MiB* for BYOC and Dedicated clusters, and *8 MiB* for Serverless clusters. You can increase this value up to *32 MiB* for BYOC and Dedicated clusters, and *20 MiB* for Serverless clusters, with the `message.max.bytes` topic property.
Copy file name to clipboardExpand all lines: modules/get-started/pages/cluster-types/byoc/remote-read-replicas.adoc
+51-5Lines changed: 51 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,10 @@ Redpanda Cloud supports remote read replica topics in BYOC clusters on AWS or GC
8
8
9
9
== Prerequisites
10
10
11
-
* A BYOC source cluster in Ready state.
11
+
To use remote read replicas, you need:
12
+
12
13
* A BYOC reader cluster in Ready state. This separate reader cluster must exist in the same Redpanda organization as the source cluster.
13
-
** AWS: The reader cluster must be in the same region as the source cluster. The reader cluster must be in the same account as the source cluster.
14
+
** AWS: The reader cluster can be in the same or a different region as the origin cluster's S3 bucket. For cross-region remote read replica topics, see <<create-cross-region-rrr-topic>>.
14
15
** GCP: The reader cluster can be in the same or a different region as the source cluster. The reader cluster must be in the same project as the source cluster.
15
16
** Azure: Remote read replicas are not supported.
16
17
@@ -84,15 +85,60 @@ A source cluster cannot be deleted if it has remote read replica topics. When yo
For standard BYOC clusters, the source cluster tiered storage bucket name follows the pattern: `redpanda-cloud-storage-$\{SOURCE_CLUSTER_ID}`
96
+
- For `<topic_name>`, use the same name as the original topic.
97
+
- For `<source-cluster-bucket-name>`, use the bucket specified in the `cloud_storage_bucket` properties for the origin cluster.
98
+
99
+
For standard BYOC clusters, the source cluster bucket name follows the pattern: `redpanda-cloud-storage-${SOURCE_CLUSTER_ID}`
100
+
101
+
[[create-cross-region-rrr-topic]]
102
+
=== Create a cross-region remote read replica topic on AWS
103
+
104
+
Use this configuration only when the remote cluster is in a *different AWS region* than the origin cluster's S3 bucket. For same-region AWS or GCP deployments, use the standard <<Create remote read replica topic,topic creation command>>.
105
+
106
+
==== Create the topic
107
+
108
+
To create a cross-region remote read replica topic, append `region` and `endpoint` query-string parameters to the bucket name.
109
+
110
+
In the following example, replace the placeholders:
111
+
112
+
- `<topic_name>`: The name of the topic in the cluster hosting the remote read replica.
113
+
- `<bucket_name>`: The S3 bucket configured on the origin cluster (`cloud_storage_bucket`).
114
+
- `<origin_bucket_region>`: The AWS region of the origin cluster's S3 bucket (not the remote cluster's region).
NOTE: The `endpoint` value must not include the bucket name. When using `virtual_host` URL style, Redpanda automatically prepends the bucket name to the endpoint. When using `path` URL style, Redpanda appends the bucket name as a path segment.
133
+
134
+
==== Limits
135
+
136
+
Each unique combination of region and endpoint creates a separate object storage target on the remote cluster. A cluster supports a maximum of 10 targets.
137
+
138
+
How targets are counted depends on `cloud_storage_url_style`:
139
+
140
+
- `virtual_host`: Each unique combination of bucket, region, and endpoint counts as one target. You can create up to 10 distinct cross-region remote read replica topics for each cluster.
141
+
- `path`: Each unique combination of region and endpoint counts as one target (the bucket name is not part of the key). You can create cross-region remote read replica topics for multiple buckets using the same region/endpoint combination, with a maximum of 10 distinct region/endpoint combinations for each cluster.
Copy file name to clipboardExpand all lines: modules/get-started/pages/whats-new-cloud.adoc
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,20 @@ This page lists new features added to Redpanda Cloud.
8
8
9
9
== March 2026
10
10
11
+
=== Cloud Topics
12
+
13
+
xref:develop:topics/cloud-topics.adoc[Cloud Topics] are now available, making it possible to use durable cloud storage (S3, ADLS, GCS) as the primary backing store instead of local disk, eliminating over 90% of cross-AZ replication costs. This makes them ideal for latency-tolerant, high-throughput workloads such as observability streams, analytics pipelines, and AI/ML training data feeds, where cross-AZ networking charges are the dominant cost driver.
14
+
15
+
You can use Cloud Topics exclusively in Redpanda Streaming clusters, or in combination with standard topics on a shared cluster supporting low-latency workloads.
16
+
17
+
=== User-based throughput quotas
18
+
19
+
Redpanda now supports throughput quotas based on authenticated user principals. Unlike client-based quotas (which rely on self-declared `client-id` values), xref:manage:cluster-maintenance/manage-throughput.adoc#set-user-based-quotas[user-based quotas] enforce limits using verified identities from SASL, mTLS, or OIDC authentication. You can set quotas for individual users, default users, or fine-grained user/client combinations.
20
+
21
+
=== Ordered rack preference for leader pinning
22
+
23
+
xref:develop:produce-data/leader-pinning.adoc[Leader pinning] now supports the `ordered_racks` configuration value, which lets you specify preferred racks in priority order. Unlike `racks`, which distributes leaders uniformly across all listed racks, `ordered_racks` places leaders in the highest-priority available rack and fails over to subsequent racks only when higher-priority racks become unavailable.
24
+
11
25
=== BYOVPC on AWS: GA
12
26
13
27
xref:get-started:cluster-types/byoc/aws/vpc-byo-aws.adoc[BYOVPC on AWS] is now generally available (GA). With Bring Your Own VPC (BYOVPC), you deploy the Redpanda data plane into your own VPC and manage security policies and resources yourself, including subnets, IAM roles, firewall rules, and storage buckets. The Redpanda BYOVPC Terraform Module contains Terraform code that deploys the resources required for a BYOVPC cluster on AWS. Secrets management is enabled by default with the Terraform module.
@@ -108,7 +122,7 @@ You can view details about Kafka client connections using `rpk` or the Data Plan
108
122
109
123
=== Increased message size limit
110
124
111
-
Redpanda Cloud increased the xref:get-started:create-topic.adoc[message size limit] on newly-created topics. BYOC and Dedicated clusters have a default message size limit of 20 MiB with a maximum of 32 MiB. Serverless clusters have a default message size limit of 8 MiB with a maximum of 20 MiB. Configure the message size limit with the `max_message_bytes` topic property.
125
+
Redpanda Cloud increased the xref:develop:topics/create-topic.adoc[message size limit] on newly-created topics. BYOC and Dedicated clusters have a default message size limit of 20 MiB with a maximum of 32 MiB. Serverless clusters have a default message size limit of 8 MiB with a maximum of 20 MiB. Configure the message size limit with the `max_message_bytes` topic property.
112
126
113
127
The message size setting on existing topics is not changed, but the message size limit on existing topics can only be updated to the new maximum.
0 commit comments