Skip to main content

Documentation Index

Fetch the complete documentation index at: https://private-7c7dfe99-page-updates.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

FAQ

Compute

Yes. The infrastructure only needs to be provisioned once for every AWS account and region combination.
BYOC supports the same set of regions as ClickHouse Cloud.
Besides Clickhouse instances (ClickHouse servers and ClickHouse Keeper), we run services such as clickhouse-operator, aws-cluster-autoscaler, Istio etc. and our monitoring stack.Currently, we have three m5.xlarge nodes (one for each AZ) in a dedicated node group to run those workloads.

Network and security

This is currently not possible.
Yes. Implementing a customer controlled mechanism where customers can approve engineers’ access to the cluster is on our roadmap. At the moment, engineers must go through our internal escalation process to gain just-in-time access to the cluster. This is logged and audited by our security team.
By default, we use 10.0.0.0/16 for BYOC VPC. We recommend reserving at least /22 for potential future scaling, but if you prefer to limit the size, it is possible to use /23 if it is likely that you will be limited to 30 server pods.
Contact support to schedule maintenance windows. Please expect a minimum of a weekly update schedule.

Uptime SLAs

No, since the data plane is hosted in the customer’s cloud environment, service availability depends on resources not in ClickHouse’s control. Therefore, ClickHouse does not offer a formal uptime SLA for BYOC deployments. If you have additional questions, please contact support@clickhouse.com.