Skip to content

Commit 66533a4

Browse files
committed
Merge branch 'main' of https://github.com/ClickHouse/clickhouse-docs into autogen-toc
2 parents d87c40a + 601a153 commit 66533a4

24 files changed

+386
-8131
lines changed

FormatFactorySettings.h

Lines changed: 0 additions & 1306 deletions
This file was deleted.

Settings.cpp

Lines changed: 0 additions & 6596 deletions
This file was deleted.
File renamed without changes.
File renamed without changes.
File renamed without changes.

docs/about-us/adopters.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -267,6 +267,7 @@ The following list of companies using ClickHouse and their success stories is as
267267
| [Langtrace AI](https://www.langtrace.ai/) | Software & Technology | LLM Monitoring | - | - | [Twitter, May 2024](https://x.com/karthikkalyan90/status/1790483625743716703) |
268268
| [Lago](https://www.getlago.com/) | Billing automation | - ||| [GitHub Wiki post](https://github.com/getlago/lago/wiki/How-ClickHouse-saved-our-events-engine-problem) |
269269
| [Lagon](https://lagon.app/) | Software Development | Serverless Functions ||| [Twitter, 2023](https://twitter.com/tomlienard/status/1702759256909394010) |
270+
| [Last9](https://last9.io/) | Software & Technology | Observability ||| [Mumbai Meetup, 2025](https://clickhouse.com/videos/the-telemetry-data-platform-breaking-down-operational-silos) |
270271
| [Laudspeaker](https://laudspeaker.com/) | Software & Technology | Open Source Messaging ||| [GitHub](https://github.com/laudspeaker/laudspeaker) |
271272
| [Lawrence Berkeley National Laboratory](https://www.lbl.gov) | Research | Traffic analysis | 5 servers | 55 TiB | [Slides in English, April 2019](https://www.smitasin.com/presentations/2019-04-17_DOE-NSM.pdf) |
272273
| [Lever](https://www.lever.co/) | Talent Management | Recruiting | - | - | [Hacker News post](https://news.ycombinator.com/item?id=29558544) |

docs/cloud/manage/upgrades.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -88,3 +88,6 @@ Selecting this option will allow users to select the day of the week/time window
8888
![Scheduled upgrades](./images/scheduled_upgrade_window.png)
8989
</div>
9090
<br/>
91+
:::note
92+
While scheduled upgrades follow the defined schedule, exceptions apply for critical security patches and vulnerability fixes. In cases where an urgent security issue is identified, upgrades may be performed outside the scheduled window. Customers will be notified of such exceptions as necessary.
93+
:::

docs/cloud/reference/byoc.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: BYOC (Bring Your Own Cloud) for AWS
33
slug: /cloud/reference/byoc
44
sidebar_label: BYOC (Bring Your Own Cloud)
5-
keywords: [byoc, cloud, bring your own cloud]
5+
keywords: [BYOC, cloud, bring your own cloud]
66
description: Deploy ClickHouse on your own cloud infrastructure
77
---
88

@@ -44,7 +44,7 @@ Customers can initiate the onboarding process by reaching out to [us](https://cl
4444

4545
### Prepare a Dedicated AWS Account {#prepare-a-dedicated-aws-account}
4646

47-
Customers must prepare a dedicated AWS account for hosting the ClickHouse BYOC deployment to ensure better isolation. With this and the initial organization admin’s email, you can contact ClickHouse support.
47+
Customers must prepare a dedicated AWS account for hosting the ClickHouse BYOC deployment to ensure better isolation. With this and the initial organization admin email, you can contact ClickHouse support.
4848

4949
### Apply CloudFormation Template {#apply-cloudformation-template}
5050

@@ -150,7 +150,7 @@ In ClickHouse BYOC account,
150150

151151
<br />
152152

153-
2. Under the Security tab on the Details page, find the associated Security Group, which follows a naming pattern like k8s-istioing-istioing-xxxxxxxxx.
153+
2. Under the Security tab on the Details page, find the associated Security Group, which follows a naming pattern like `k8s-istioing-istioing-xxxxxxxxx`.
154154

155155
<br />
156156

@@ -314,7 +314,7 @@ BYOC supports the same set of [regions](/cloud/reference/supported-regions#aws-r
314314

315315
#### Will there be some resource overhead? What are the resources needed to run services other than ClickHouse instances? {#will-there-be-some-resource-overhead-what-are-the-resources-needed-to-run-services-other-than-clickhouse-instances}
316316

317-
Besides Clickhouse instances (ClickHouse servers and ClickHouse Keeper), we run services such as clickhouse-operator, aws-cluster-autoscaler, Istio etc. and our monitoring stack.
317+
Besides Clickhouse instances (ClickHouse servers and ClickHouse Keeper), we run services such as `clickhouse-operator`, `aws-cluster-autoscaler`, Istio etc. and our monitoring stack.
318318

319319
Currently we have 3 m5.xlarge nodes (one for each AZ) in a dedicated node group to run those workloads.
320320

docs/cloud/reference/changelog.md

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,59 @@ title: Cloud Changelog
66

77
In addition to this ClickHouse Cloud changelog, please see the [Cloud Compatibility](/cloud/reference/cloud-compatibility.md) page.
88

9+
## February 21, 2025 {#february-21-2025}
10+
11+
### ClickHouse Bring Your Own Cloud (BYOC) for AWS is now generally available! {#clickhouse-byoc-for-aws-ga}
12+
13+
In this deployment model, data plane components (compute, storage, backups, logs, metrics)
14+
run in the Customer VPC, while the control plane (web access, APIs, and billing)
15+
remains within the ClickHouse VPC. This setup is ideal for large workloads that
16+
need to comply with strict data residency requirements by ensuring all data stays
17+
within a secure customer environment.
18+
19+
- For more details, you can refer to the [documentation](/docs/cloud/reference/byoc) for BYOC
20+
or read our [announcement blog post](https://clickhouse.com/blog/announcing-general-availability-of-clickhouse-bring-your-own-cloud-on-aws).
21+
- [Contact us](https://clickhouse.com/cloud/bring-your-own-cloud) to request access.
22+
23+
### Postgres CDC connector for ClickPipes {#postgres-cdc-connector-for-clickpipes}
24+
25+
Postgres CDC connector for ClickPipes is now in public beta. This feature allows
26+
users to seamlessly replicate their Postgres databases to ClickHouse Cloud.
27+
28+
- To get started, refer to the [documentation](https://clickhouse.com/docs/integrations/clickpipes/postgres) for ClickPipes Postgres CDC connector.
29+
- 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).
30+
31+
### PCI compliance for ClickHouse Cloud on AWS {#pci-compliance-for-clickhouse-cloud-on-aws}
32+
33+
ClickHouse Cloud now supports **PCI-compliant services** for **Enterprise tier**
34+
customers in **us-east-1** and **us-west-2** regions. Users who wish to launch
35+
a service in a PCI-compliant environment can contact [support](https://clickhouse.com/support/program)
36+
for assistance.
37+
38+
### Transparent Data Encryption and Customer Managed Encryption Keys on Google Cloud Platform {#tde-and-cmek-on-gcp}
39+
40+
Support for **Transparent Data Encryption (TDE)** and **Customer Managed
41+
Encryption Keys (CMEK)** is now available for ClickHouse Cloud on **Google Cloud Platform (GCP)**.
42+
43+
- Please refer to the [documentation](https://clickhouse.com/docs/cloud/security/cmek#transparent-data-encryption-tde) of these features for more information.
44+
45+
### AWS Middle East (UAE) availability {#aws-middle-east-uae-availability}
46+
47+
New region support is added for ClickHouse Cloud, which is now available in the
48+
**AWS Middle East (UAE) me-central-1** region.
49+
50+
### ClickHouse Cloud guardrails {#clickhouse-cloud-guardrails}
51+
52+
To promote best practices and ensure stable use of ClickHouse Cloud, we are
53+
introducing guardrails for the number of tables, databases, partitions and parts
54+
in use.
55+
56+
- Refer to the [usage limits](https://clickhouse.com/docs/cloud/bestpractices/usage-limits)
57+
section of the documentation for details.
58+
- If your service is already above these limits, we will permit a 10% increase.
59+
Please contact [support](https://clickhouse.com/support/program) if you have any questions.
60+
61+
962
## January 27, 2025 {#january-27-2025}
1063

1164
### Changes to ClickHouse Cloud tiers {#changes-to-clickhouse-cloud-tiers}

docs/cloud/reference/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,6 @@ This section acts as a reference guide for some of the more technical details of
1515
| [SharedMergeTree](/cloud/reference/shared-merge-tree) | Explainer on SharedMergeTree, the cloud-native replacement for the ReplicatedMergeTree and analogues. |
1616
| [Warehouses](/cloud/reference/compute-compute-separation) | Explainer on what Warehouses and Compute-Compute separation are in ClickHouse Cloud. |
1717
| [BYOC (Bring Your Own Cloud)](/cloud/reference/byoc)| Explainer on the Bring Your Own Cloud (BYOC) service available with ClickHouse Cloud. |
18-
| [Changelogs](/cloud/reference/changelogs) | Cloud ChangeLogs and Release Notes. |
18+
| [Changelogs](/cloud/reference/changelogs) | Cloud Changelogs and Release Notes. |
1919
| [Cloud Compatibility](/whats-new/cloud-compatibility) | A guide to what to expect functionally and operationally in ClickHouse Cloud. |
2020
| [Supported Cloud Regions](/cloud/reference/supported-regions) | A list of the supported cloud regions for AWS, Google and Azure. |

0 commit comments

Comments
 (0)