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/get-started/pages/whats-new-cloud.adoc
+32-18Lines changed: 32 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,24 +8,6 @@ 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
-
25
-
=== BYOVPC on AWS: GA
26
-
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.
28
-
29
11
=== Redpanda Connect updates
30
12
31
13
* Inputs:
@@ -48,6 +30,38 @@ xref:get-started:cluster-types/byoc/aws/vpc-byo-aws.adoc[BYOVPC on AWS] is now g
48
30
+
49
31
Use the unified xref:develop:connect/components/inputs/redpanda_migrator.adoc[`redpanda_migrator`] input and xref:develop:connect/components/outputs/redpanda_migrator.adoc[`redpanda_migrator`] output instead.
50
32
33
+
=== Cloud Topics
34
+
35
+
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.
36
+
37
+
You can use Cloud Topics exclusively or in combination with standard topics on a cluster supporting low-latency workloads.
38
+
39
+
=== User-based throughput quotas
40
+
41
+
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.
42
+
43
+
=== Iceberg: Expanded JSON Schema support
44
+
45
+
Redpanda now supports additional JSON Schema patterns when translating to Iceberg tables:
46
+
47
+
* `$ref` support: Internal references using `$ref` (for example, `"$ref": "#/definitions/myType"`) are resolved from schema resources declared in the same document. External references are not yet supported.
48
+
* Map type from `additionalProperties`: `additionalProperties` objects that contain subschemas now translate to Iceberg `map<string, T>`.
49
+
* `oneOf` nullable pattern: The `oneOf` keyword is now supported for the standard nullable pattern if exactly one branch is `{"type":"null"}` and the other is a non-null schema.
50
+
51
+
See xref:manage:iceberg/specify-iceberg-schema.adoc#how-iceberg-modes-translate-to-table-format[Specify Iceberg Schema] for JSON types mapping and updated requirements.
52
+
53
+
=== Ordered rack preference for leader pinning
54
+
55
+
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.
56
+
57
+
=== Cross-region Remote Read Replicas on AWS
58
+
59
+
xref:get-started:cluster-types/byoc/remote-read-replicas.adoc[Remote read replica] topics on AWS can now be deployed in a different region from the origin cluster's S3 bucket. This enables cross-region disaster recovery and data locality scenarios while maintaining the read-only replication model.
60
+
61
+
=== BYOVPC on AWS: GA
62
+
63
+
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.
64
+
51
65
=== Iceberg topics with Snowflake Open Catalog: GA
52
66
53
67
The xref:manage:iceberg/redpanda-topics-iceberg-snowflake-catalog.adoc[Snowflake and Open Catalog integration] for Iceberg topics is now generally available (GA).
0 commit comments