Merge pull request #4927 from ClickHouse/byoc-dec-update

byoc: update the latest information

Author: Blargian

docs/cloud/guides/infrastructure/01_deployment_options/byoc/01_overview.md

@@ -7,24 +7,40 @@ description: 'Deploy ClickHouse on your own cloud infrastructure'
 doc_type: 'reference'
 ---
 
+import Image from '@theme/IdealImage';
+import byoc1 from '@site/static/images/cloud/reference/byoc-1.png';
+
 ## Overview {#overview}
 
 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.
 
 > **If you would like access, please [contact us](https://clickhouse.com/cloud/bring-your-own-cloud).** Refer to our [Terms of Service](https://clickhouse.com/legal/agreements/terms-of-service) for additional information.
 
-BYOC is currently only supported for AWS. You can join the wait list for GCP and Azure [here](https://clickhouse.com/cloud/bring-your-own-cloud).
-
 :::note 
 BYOC is designed specifically for large-scale deployments, and requires customers to sign a committed contract.
 :::
 
+Supported Cloud Service Providers:
+* AWS (GA)
+* GCP (Private Preview). Please join the waitlist [here](https://clickhouse.com/cloud/bring-your-own-cloud) if you are interested.
+* Azure (Roadmap). Please join the waitlist [here](https://clickhouse.com/cloud/bring-your-own-cloud) if you are interested.
+
 ## Glossary {#glossary}
 
 - **ClickHouse VPC:**  The VPC owned by ClickHouse Cloud.
 - **Customer BYOC VPC:** The VPC, owned by the customer's cloud account, is provisioned and managed by ClickHouse Cloud and dedicated to a ClickHouse Cloud BYOC deployment.
 - **Customer VPC** Other VPCs owned by the customer cloud account used for applications that need to connect to the Customer BYOC VPC.
 
+## Architecture {#architecture}
+
+Metrics and logs are stored within the customer's BYOC VPC. Logs are currently stored in locally in EBS. In a future update, logs will be stored in LogHouse, which is a ClickHouse service in the customer's BYOC VPC. Metrics are implemented via a Prometheus and Thanos stack stored locally in the customer's BYOC VPC.
+
+<br />
+
+<Image img={byoc1} size="lg" alt="BYOC Architecture" background='black'/>
+
+<br />
+
 ## Features {#features}
 
 ### Supported features {#supported-features}
@@ -35,7 +51,7 @@ BYOC is designed specifically for large-scale deployments, and requires customer
   - View services and status.
 - **Backup and restore.**
 - **Manual vertical and horizontal scaling.**
-- **Idling.**
+- **Auto Idling.**
 - **Warehouses**: Compute-Compute Separation
 - **Zero Trust Network via Tailscale.**
 - **Monitoring**:
@@ -49,6 +65,6 @@ BYOC is designed specifically for large-scale deployments, and requires customer
 ### Planned features (currently unsupported) {#planned-features-currently-unsupported}
 
 - [AWS KMS](https://aws.amazon.com/kms/) aka CMEK (customer-managed encryption keys)
-- ClickPipes for ingest
+- ClickPipes
 - Autoscaling
 - MySQL interface

docs/cloud/guides/infrastructure/01_deployment_options/byoc/03_onboarding/01_aws.md

@@ -59,9 +59,10 @@ After creating the CloudFormation stack, you will be prompted to set up the infr
 By default, ClickHouse Cloud will provision a dedicated VPC for better isolation in your BYOC deployment. However, you can also use an existing VPC in your account. This requires specific configuration and must be coordinated through ClickHouse Support.
 
 **Configure Your Existing VPC**
-1. Allocate at least 3 private subnets across 3 different availability zones for ClickHouse Cloud to use.
-2. Ensure each subnet has a minimum CIDR range of `/23` (e.g., 10.0.0.0/23) to provide sufficient IP addresses for the ClickHouse deployment.
-3. Add the tag `kubernetes.io/role/internal-elb=1` to each subnet to enable proper load balancer configuration.
+1. Tag the VPC with `clickhouse-byoc="true"`.
+2. Allocate at least 3 private subnets across 3 different availability zones for ClickHouse Cloud to use.
+3. Ensure each subnet has a minimum CIDR range of `/23` (e.g., 10.0.0.0/23) to provide sufficient IP addresses for the ClickHouse deployment.
+4. Add the tag `kubernetes.io/role/internal-elb=1` and `clickhouse-byoc="true"` to each subnet to enable proper load balancer configuration.
 
 <br />