Merge pull request #4595 from ClickHouse/restructure-byoc-documentation

Restructure BYOC documentation

Author: Blargian

docs/cloud/features/04_infrastructure/deployment-options.md

@@ -24,7 +24,7 @@ Learn more about [ClickHouse Cloud](/getting-started/quick-start/cloud).
 
 ClickHouse Bring Your Own Cloud (BYOC) allows organizations to deploy and manage ClickHouse within their own cloud environment while leveraging a managed service layer. This option bridges the gap between the fully managed experience of ClickHouse Cloud and the complete control of self-managed deployments. With ClickHouse BYOC, users retain control over their data, infrastructure, and security policies, meeting specific compliance and regulatory requirements, while offloading operational tasks like patching, monitoring, and scaling to the ClickHouse. This model offers the flexibility of a private cloud deployment with the benefits of a managed service, making it suitable for large-scale deployments at enterprises with stringent security, governance, and data residency needs.
 
-Learn more about [Bring Your Own Cloud](/cloud/reference/byoc).
+Learn more about [Bring Your Own Cloud](/cloud/reference/byoc/overview).
 
 ## ClickHouse Private {#clickhouse-private}
 

docs/cloud/guides/index.md

@@ -10,9 +10,12 @@ doc_type: 'landing-page'
 | Page | Description |
 |-----|-----|
 | [Accessing S3 data securely](/cloud/data-sources/secure-s3) | This article demonstrates how ClickHouse Cloud customers can leverage role-based access to authenticate with Amazon Simple Storage Service(S3) and access their data securely. |
+| [Architecture](/cloud/reference/byoc/architecture) | Deploy ClickHouse on your own cloud infrastructure |
 | [AWS PrivateLink](/manage/security/aws-privatelink) | This document describes how to connect to ClickHouse Cloud using AWS PrivateLink. |
 | [Azure Private Link](/cloud/security/azure-privatelink) | How to set up Azure Private Link |
-| [BYOC (Bring Your Own Cloud) for AWS](/cloud/reference/byoc) | Deploy ClickHouse on your own cloud infrastructure |
+| [BYOC on AWS FAQ](/cloud/reference/byoc/faq/aws) | Deploy ClickHouse on your own cloud infrastructure |
+| [BYOC on AWS Observability](/cloud/reference/byoc/observability) | Deploy ClickHouse on your own cloud infrastructure |
+| [BYOC Onboarding for AWS](/cloud/reference/byoc/onboarding/aws) | Deploy ClickHouse on your own cloud infrastructure |
 | [BYOC security playbook](/cloud/security/audit-logging/byoc-security-playbook) | This page illustrates methods customers can use to identify potential security events |
 | [ClickHouse Government](/cloud/infrastructure/clickhouse-government) | Overview of ClickHouse Government offering |
 | [ClickHouse Private](/cloud/infrastructure/clickhouse-private) | Overview of ClickHouse Private offering |
@@ -24,13 +27,14 @@ doc_type: 'landing-page'
 | [Data masking in ClickHouse](/cloud/guides/data-masking) | A guide to data masking in ClickHouse |
 | [Database audit log](/cloud/security/audit-logging/database-audit-log) | This page describes how users can review the database audit log |
 | [Gather your connection details](/cloud/guides/sql-console/gather-connection-details) | Gather your connection details |
-| [GCP Private Service Connect](/manage/security/gcp-private-service-connect) | This document describes how to connect to ClickHouse Cloud using Google Cloud Platform (GCP) Private Service Connect (PSC), and how to disable access to your ClickHouse Cloud services from addresses other than GCP PSC addresses using ClickHouse Cloud IP access lists. |
+| [GCP private service connect](/manage/security/gcp-private-service-connect) | This document describes how to connect to ClickHouse Cloud using Google Cloud Platform (GCP) Private Service Connect (PSC), and how to disable access to your ClickHouse Cloud services from addresses other than GCP PSC addresses using ClickHouse Cloud IP access lists. |
 | [HIPAA onboarding](/cloud/security/compliance/hipaa-onboarding) | Learn more about how to onboard to HIPAA compliant services |
 | [Manage cloud users](/cloud/security/manage-cloud-users) | This page describes how administrators can add users, manage assignments, and remove users |
 | [Manage database users](/cloud/security/manage-database-users) | This page describes how administrators can add database users, manage assignments, and remove database users |
 | [Manage my account](/cloud/security/manage-my-account) | This page describes how users can accept invitations, manage MFA settings, and reset passwords |
 | [Manage SQL console role assignments](/cloud/guides/sql-console/manage-sql-console-role-assignments) | Guide showing how to manage SQL console role assignments |
 | [Multi tenancy](/cloud/bestpractices/multi-tenancy) | Best practices to implement multi tenancy |
+| [Overview](/cloud/reference/byoc/overview) | Deploy ClickHouse on your own cloud infrastructure |
 | [PCI onboarding](/cloud/security/compliance/pci-onboarding) | Learn more about how to onboard to PCI compliant services |
 | [Query API Endpoints](/cloud/get-started/query-endpoints) | Easily spin up REST API endpoints from your saved queries |
 | [SAML SSO setup](/cloud/security/saml-setup) | How to set up SAML SSO with ClickHouse Cloud |

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

@@ -0,0 +1,54 @@
+---
+title: 'Overview'
+slug: /cloud/reference/byoc/overview
+sidebar_label: 'Overview'
+keywords: ['BYOC', 'cloud', 'bring your own cloud']
+description: 'Deploy ClickHouse on your own cloud infrastructure'
+doc_type: 'reference'
+---
+
+## 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.
+:::
+
+## 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.
+
+## Features {#features}
+
+### Supported features {#supported-features}
+
+- **SharedMergeTree**: ClickHouse Cloud and BYOC use the same binary and configuration. Therefore all features from ClickHouse core are supported in BYOC such as SharedMergeTree.
+- **Console access for managing service state**:
+  - Supports operations such as start, stop, and terminate.
+  - View services and status.
+- **Backup and restore.**
+- **Manual vertical and horizontal scaling.**
+- **Idling.**
+- **Warehouses**: Compute-Compute Separation
+- **Zero Trust Network via Tailscale.**
+- **Monitoring**:
+  - The Cloud console includes built-in health dashboards for monitoring service health.
+  - Prometheus scraping for centralized monitoring with Prometheus, Grafana, and Datadog. See the [Prometheus documentation](/integrations/prometheus) for setup instructions.
+- **VPC Peering.**
+- **Integrations**: See the full list on [this page](/integrations).
+- **Secure S3.**
+- **[AWS PrivateLink](https://aws.amazon.com/privatelink/).**
+
+### Planned features (currently unsupported) {#planned-features-currently-unsupported}
+
+- [AWS KMS](https://aws.amazon.com/kms/) aka CMEK (customer-managed encryption keys)
+- ClickPipes for ingest
+- Autoscaling
+- MySQL interface

docs/cloud/guides/infrastructure/01_deployment_options/byoc/02_architecture.md

@@ -0,0 +1,21 @@
+---
+title: 'Architecture'
+slug: /cloud/reference/byoc/architecture
+sidebar_label: 'Architecture'
+keywords: ['BYOC', 'cloud', 'bring your own cloud']
+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';
+
+## 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 />