Skip to content

Commit 237be2f

Browse files
authored
Merge pull request #3196 from ClickHouse/krithika-ch-patch-1
Update byoc.md
2 parents d9a9eca + 67d83ea commit 237be2f

File tree

1 file changed

+5
-8
lines changed

1 file changed

+5
-8
lines changed

docs/en/cloud/reference/byoc.md

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,16 @@
11
---
2-
title: BYOC (Bring Your Own Cloud) for AWS - Beta
2+
title: BYOC (Bring Your Own Cloud) for AWS
33
slug: /en/cloud/reference/byoc
44
sidebar_label: BYOC (Bring Your Own Cloud)
55
keywords: [byoc, cloud, bring your own cloud]
66
description: Deploy ClickHouse on your own cloud infrastructure
77
---
8-
import BetaBadge from '@theme/badges/BetaBadge';
98

109
## Overview
1110

12-
<BetaBadge />
13-
1411
BYOC (Bring Your Own Cloud) allows you to deploy ClickHouse Cloud on your own cloud infrastructure. This is useful if you have specific requirements or constraints that prevent you from using the ClickHouse Cloud managed service.
1512

16-
**BYOC is currently in Beta. If you would like access, please contact [support](https://clickhouse.com/support/program).** Refer to our [Terms of Service](https://clickhouse.com/legal/agreements/terms-of-service) for additional information.
13+
**If you would like access, please contact [support](https://clickhouse.com/support/program).** Refer to our [Terms of Service](https://clickhouse.com/legal/agreements/terms-of-service) for additional information.
1714

1815
BYOC is currently only supported for AWS, with GCP and Microsoft Azure in development.
1916

@@ -43,7 +40,7 @@ Metrics and logs are stored within the customer's BYOC VPC. Logs are currently s
4340

4441
## Onboarding Process
4542

46-
During the Beta, initiate the onboarding process by reaching out to ClickHouse [support](https://clickhouse.com/support/program). Customers need to have a dedicated AWS account and know the region they will use. At this time, we are allowing users to launch BYOC services only in the regions that we support for ClickHouse Cloud.
43+
Customers can initiate the onboarding process by reaching out to ClickHouse [support](https://clickhouse.com/support/program). Customers need to have a dedicated AWS account and know the region they will use. At this time, we are allowing users to launch BYOC services only in the regions that we support for ClickHouse Cloud.
4744

4845
### Prepare a Dedicated AWS Account
4946

@@ -202,7 +199,8 @@ State Exporter sends ClickHouse service state information to an SQS owned by Cli
202199
- Supports operations such as start, stop, and terminate.
203200
- View services and status.
204201
- **Backup and restore.**
205-
- **Manual vertical and horizontal scaling.**
202+
- **Manual vertical and horizontal scaling.**
203+
- **Idling.**
206204
- **Runtime security monitoring and alerting via Falco (`falco-metrics`).**
207205
- **Zero Trust Network via Tailscale.**
208206
- **Monitoring**:
@@ -218,7 +216,6 @@ State Exporter sends ClickHouse service state information to an SQS owned by Cli
218216
- [AWS KMS](https://aws.amazon.com/kms/) aka CMEK (customer-managed encryption keys)
219217
- ClickPipes for ingest
220218
- Autoscaling
221-
- Idling
222219
- MySQL interface
223220

224221
## FAQ

0 commit comments

Comments
 (0)