Cloud changelog

## April 4, 2025[​](#april-4-2025 "Direct link to April 4, 2025")

- Slack notifications for ClickHouse Cloud: ClickHouse Cloud now supports Slack notifications for billing, scaling, and ClickPipes events, in addition to in-console and email notifications. These notifications are sent via the ClickHouse Cloud Slack application. Organization admins can configure these notifications via the notification center by specifying slack channels to which notifications should be sent.
- Users running Production and Development services will now see ClickPipes and data transfer usage price on their bills.

## March 21, 2025[​](#march-21-2025 "Direct link to March 21, 2025")

- Cross-region Private Link connectivity on AWS is now in Beta. Please refer to
  ClickHouse Cloud private link [docs](/docs/manage/security/aws-privatelink) for
  details of how to set up and list of supported regions.
- The maximum replica size available for services on AWS is now set to 236 GiB RAM.
  This allows for efficient utilization, while ensuring we have resources
  allocated to background processes.

## March 7, 2025[​](#march-7-2025 "Direct link to March 7, 2025")

- New `UsageCost` API endpoint: The API specification now supports a new endpoint
  for retrieving usage information. This is an organization endpoint and usage
  costs can be queried for a maximum of 31 days. The metrics that can be
  retrieved include Storage, Compute, Data Transfer and ClickPipes. Please refer
  to the [documentation](https://clickhouse.com/docs/cloud/manage/api/usageCost-api-reference) for details.
- Terraform provider [v2.1.0](https://registry.terraform.io/providers/ClickHouse/clickhouse/2.1.0/docs/resources/service#nestedatt--endpoints_configuration) release supports enabling the MySQL endpoint.

## February 21, 2025[​](#february-21-2025 "Direct link to February 21, 2025")

### ClickHouse Bring Your Own Cloud (BYOC) for AWS is now generally available[​](#clickhouse-byoc-for-aws-ga "Direct link to ClickHouse Bring Your Own Cloud (BYOC) for AWS is now generally available")

In this deployment model, data plane components (compute, storage, backups, logs, metrics)
run in the Customer VPC, while the control plane (web access, APIs, and billing)
remains within the ClickHouse VPC. This setup is ideal for large workloads that
need to comply with strict data residency requirements by ensuring all data stays
within a secure customer environment.

- For more details, you can refer to the [documentation](/docs/cloud/reference/byoc/overview) for BYOC
  or read our [announcement blog post](https://clickhouse.com/blog/announcing-general-availability-of-clickhouse-bring-your-own-cloud-on-aws).
- [Contact us](https://clickhouse.com/cloud/bring-your-own-cloud) to request access.

### Postgres CDC connector for ClickPipes[​](#postgres-cdc-connector-for-clickpipes "Direct link to Postgres CDC connector for ClickPipes")

Postgres CDC connector for ClickPipes allows you to seamlessly replicate your Postgres databases to ClickHouse Cloud.

- To get started, refer to the [documentation](https://clickhouse.com/docs/integrations/clickpipes/postgres) for ClickPipes Postgres CDC connector.
- For more information on customer use cases and features, please refer to the [landing page](https://clickhouse.com/cloud/clickpipes/postgres-cdc-connector) and the [launch blog](https://clickhouse.com/blog/postgres-cdc-connector-clickpipes-public-beta).

### PCI compliance for ClickHouse Cloud on AWS[​](#pci-compliance-for-clickhouse-cloud-on-aws "Direct link to PCI compliance for ClickHouse Cloud on AWS")

ClickHouse Cloud now supports **PCI-compliant services** for **Enterprise tier**
customers in **us-east-1** and **us-west-2** regions. Users who wish to launch
a service in a PCI-compliant environment can contact [support](https://clickhouse.com/support/program)
for assistance.

### Transparent Data Encryption and Customer Managed Encryption Keys on Google Cloud Platform[​](#tde-and-cmek-on-gcp "Direct link to Transparent Data Encryption and Customer Managed Encryption Keys on Google Cloud Platform")

Support for **Transparent Data Encryption (TDE)** and **Customer Managed
Encryption Keys (CMEK)** is now available for ClickHouse Cloud on **Google Cloud Platform (GCP)**.

- Please refer to the [documentation](https://clickhouse.com/docs/cloud/security/cmek#transparent-data-encryption-tde) of these features for more information.

### AWS Middle East (UAE) availability[​](#aws-middle-east-uae-availability "Direct link to AWS Middle East (UAE) availability")

New region support is added for ClickHouse Cloud, which is now available in the
**AWS Middle East (UAE) me-central-1** region.

### ClickHouse Cloud guardrails[​](#clickhouse-cloud-guardrails "Direct link to ClickHouse Cloud guardrails")

To promote best practices and ensure stable use of ClickHouse Cloud, we are
introducing guardrails for the number of tables, databases, partitions and parts
in use.

- Refer to the [usage limits](https://clickhouse.com/docs/cloud/bestpractices/usage-limits)
  section of the documentation for details.
- If your service is already above these limits, we will permit a 10% increase.
  Please contact [support](https://clickhouse.com/support/program) if you have any questions.

## January 27, 2025[​](#january-27-2025 "Direct link to January 27, 2025")

### Changes to ClickHouse Cloud tiers[​](#changes-to-clickhouse-cloud-tiers "Direct link to Changes to ClickHouse Cloud tiers")

We are dedicated to adapting our products to meet the ever-changing requirements of our customers. Since its introduction in GA over the past two years, ClickHouse Cloud has evolved substantially, and we've gained invaluable insights into how our customers leverage our cloud offerings.

We are introducing new features to optimize the sizing and cost-efficiency of ClickHouse Cloud services for your workloads. These include **compute-compute separation**, high-performance machine types, and **single-replica services**. We are also evolving automatic scaling and managed upgrades to execute in a more seamless and reactive fashion.

We are adding a **new Enterprise tier** to serve the needs of the most demanding customers and workloads, with focus on industry-specific security and compliance features, even more controls over underlying hardware and upgrades, and advanced disaster recovery features.

To support these changes, we are restructuring our current **Development** and **Production** tiers to more closely match how our evolving customer base is using our offerings. We are introducing the **Basic** tier, oriented toward users that are testing out new ideas and projects, and the **Scale** tier, matching users working with production workloads and data at scale.

You can read about these and other functional changes in this [blog](https://clickhouse.com/blog/evolution-of-clickhouse-cloud-new-features-superior-performance-tailored-offerings). Existing customers will need to take action to select a [new plan](https://clickhouse.com/pricing). Customer-facing communication was sent via email to organization administrators.

### Warehouses: Compute-compute separation (GA)[​](#warehouses-compute-compute-separation-ga "Direct link to Warehouses: Compute-compute separation (GA)")

Compute-compute separation (also known as "Warehouses") is Generally Available; please refer to [blog](https://clickhouse.com/blog/introducing-warehouses-compute-compute-separation-in-clickhouse-cloud) for more details and the [documentation](/docs/cloud/reference/warehouses).

### Single-replica services[​](#single-replica-services "Direct link to Single-replica services")

We are introducing the concept of a "single-replica service", both as a standalone offering and within warehouses. As a standalone offering, single-replica services are size limited and intended to be used for small test workloads. Within warehouses, single-replica services can be deployed at larger sizes, and utilized for workloads not requiring high availability at scale, such as restartable ETL jobs.