From 410ed9a961c431ac2e5c0b348dc526241be9ea40 Mon Sep 17 00:00:00 2001 From: Michele Cyran Date: Tue, 29 Oct 2024 15:34:19 -0600 Subject: [PATCH] DOC-377 cost-optimized cloud tiers (#100) * DOC-377 cost-optimized cloud tiers * add what's new blurb * minor fix --- modules/get-started/pages/whats-new-cloud.adoc | 4 ++++ modules/reference/partials/tiers.adoc | 1 + 2 files changed, 5 insertions(+) diff --git a/modules/get-started/pages/whats-new-cloud.adoc b/modules/get-started/pages/whats-new-cloud.adoc index 733e7bad..d6a3f903 100644 --- a/modules/get-started/pages/whats-new-cloud.adoc +++ b/modules/get-started/pages/whats-new-cloud.adoc @@ -9,6 +9,10 @@ This page lists new features added in Redpanda Cloud. == October 2024 +=== Support for AWS Graviton3 + +Redpanda now supports compute-optimized tiers with AWS Graviton3 processors. This saves over 50% in instance costs in all xref:reference:tiers/byoc-tiers.adoc[BYOC tiers]. + === Redpanda Terraform Provider for Redpanda Cloud The xref:manage:terraform-provider.adoc[Redpanda Terraform provider] lets you can create and manage resources in Redpanda Cloud, such as clusters, topics, users, ACLs, networks, and resource groups. diff --git a/modules/reference/partials/tiers.adoc b/modules/reference/partials/tiers.adoc index b3f6d29c..4f65fba6 100644 --- a/modules/reference/partials/tiers.adoc +++ b/modules/reference/partials/tiers.adoc @@ -20,6 +20,7 @@ When you create a BYOC cluster, you select your usage tier. Each tier provides t [NOTE] ==== * On Azure, tiers 1-3 are supported. +* Redpanda supports compute-optimized tiers with AWS Graviton3 processors. * Depending on the workload, it may not be possible to achieve all maximum values. For example, a high number of partitions may make it more difficult to reach the maximum value in throughput. * Partition counts are based on the assumption that the Redpanda Cloud replication factor is 3 (default). If you set a higher replication factor, the maximum value for partitions will be lower. * Connections are regulated per broker for best performance. For example, in a tier 1 cluster with 3 brokers, there could be up to 3,000 connections per broker.