Merge remote-tracking branch 'origin/main'

Author: BentsiLeviav

docs/architecture/cluster-deployment.md

@@ -41,7 +41,7 @@ Follow these best practices to improve JOIN performance:
 When using dictionaries for JOINs in ClickHouse, it's important to understand that dictionaries, by design, do not allow duplicate keys. During data loading, any duplicate keys are silently deduplicated—only the last loaded value for a given key is retained. This behavior makes dictionaries ideal for one-to-one or many-to-one relationships where only the latest or authoritative value is needed. However, using a dictionary for a one-to-many or many-to-many relationship (e.g. joining roles to actors where an actor can have multiple roles) will result in silent data loss, as all but one of the matching rows will be discarded. As a result, dictionaries are not suitable for scenarios requiring full relational fidelity across multiple matches.
 :::
 
-## Choosing the right JOIN Algorithm {#choosing-the-right-join-algorithm}
+## Choosing the correct JOIN Algorithm {#choosing-the-right-join-algorithm}
 
 ClickHouse supports several JOIN algorithms that trade off between speed and memory:
 

docs/best-practices/minimize_optimize_joins.md

@@ -24,6 +24,10 @@ ClickHouse Cloud allows you to configure the schedule for your backups for **Sca
 The custom schedule will override the default backup policy in ClickHouse Cloud for your given service.
 :::
 
+:::note
+In some rare scenarios, the backup scheduler will not respect the **Start Time** specified for backups. Specifically, this happens if there was a successful backup triggered < 24 hours from the time of the currently scheduled backup. This could happen due to a retry mechanism we have in place for backups. In such instances, the scheduler will skip over the backup for the current day, and will retry the backup the next day at the scheduled time. 
+:::
+
 To configure the backup schedule for a service, go to the **Settings** tab in the console and click on **Change backup configuration**.
 
 <Image img={backup_settings} size="lg" alt="Configure backup settings" border/>

docs/cloud/manage/backups/configurable-backups.md

@@ -15,7 +15,7 @@ For details of how ClickHouse Cloud backups work, including "full" vs. "incremen
 Here we show examples of how to take full and incremental backups to AWS, GCP, Azure object storage as well as how to restore from the backups.
 
 :::note
-Users should be aware that any usage where backups are being exported to a different region in the same cloud provider, or to another cloud provider (in the same or different region) will incur [data transfer](../network-data-transfer.mdx) charges.
+Users should be aware that any usage where backups are being exported to a different region in the same cloud provider, will incur [data transfer](../network-data-transfer.mdx) charges.  Currently we do not support cross cloud backups.
 :::
 
 ## Requirements {#requirements}
@@ -26,19 +26,23 @@ You will need the following details to export/restore backups to your own CSP st
 
 1. AWS S3 endpoint, in the format:
 
-    ```text
-    s3://<bucket_name>.s3.amazonaws.com/<directory>
-    ```
+  ```text
+  s3://<bucket_name>.s3.amazonaws.com/<directory>
+  ```
 
-    For example: 
-    ```text
-    s3://testchbackups.s3.amazonaws.com/backups/
-   ```
-    Where:
-   - `testchbackups` is the name of the S3 bucket to export backups to.
-   - `backups` is an optional subdirectory.
+  For example: 
+  ```text
+  s3://testchbackups.s3.amazonaws.com/backups/
+  ```
+  Where:
+    - `testchbackups` is the name of the S3 bucket to export backups to.
+    - `backups` is an optional subdirectory.
 
-2. AWS access key and secret.
+2. AWS access key and secret. AWS role based authentication is also supported and can be used in place of AWS access key and secret.
+
+:::note
+In order to use role based authentication, please follow the Secure s3 [setup](https://clickhouse.com/docs/cloud/security/secure-s3). In addition, you will need to add `s3:PutObject`, and `s3:DeleteObject` permissions to the IAM policy decribed [here.](https://clickhouse.com/docs/cloud/security/secure-s3#option-2-manually-create-iam-role)
+:::
 
 ### Azure {#azure}
 

docs/cloud/manage/backups/export-backups-to-own-cloud-account.md

@@ -223,6 +223,10 @@ ClickHouse Cloud supports the following billing options:
 - Direct-sales annual / multi-year (through pre-paid "ClickHouse Credits", in USD, with additional payment options).
 - Through the AWS, GCP, and Azure marketplaces (either pay-as-you-go (PAYG) or commit to a contract with ClickHouse Cloud through the marketplace).
 
+:::note
+ClickHouse Cloud credits for PAYG are invoiced in \$0.01 units, allowing us to charge customers for partial ClickHouse credits based on their usage. This differs from committed spend ClickHouse credits, which are purchased in advance in whole \$1 units.
+:::
+
 ### How long is the billing cycle? {#how-long-is-the-billing-cycle}
 
 Billing follows a monthly billing cycle and the start date is tracked as the date when the ClickHouse Cloud organization was created.
@@ -454,12 +458,12 @@ This section outlines the pricing model of ClickPipes for streaming and object s
 
 #### What does the ClickPipes pricing structure look like? {#what-does-the-clickpipes-pricing-structure-look-like}
 
-It consists of two dimensions
+It consists of two dimensions:
 
-- **Compute**: Price per unit per hour
+- **Compute**: Price **per unit per hour**.
   Compute represents the cost of running the ClickPipes replica pods whether they actively ingest data or not.
   It applies to all ClickPipes types.
-- **Ingested data**: per GB pricing
+- **Ingested data**: Price **per GB**.
   The ingested data rate applies to all streaming ClickPipes
   (Kafka, Confluent, Amazon MSK, Amazon Kinesis, Redpanda, WarpStream, Azure Event Hubs)
   for the data transferred via the replica pods. The ingested data size (GB) is charged based on bytes received from the source (uncompressed or compressed).
@@ -472,17 +476,27 @@ For this reason, it uses dedicated compute replicas.
 
 #### What is the default number of replicas and their size? {#what-is-the-default-number-of-replicas-and-their-size}
 
-Each ClickPipe defaults to 1 replica that is provided with 2 GiB of RAM and 0.5 vCPU.
-This corresponds to **0.25** ClickHouse compute units (1 unit = 8 GiB RAM, 2 vCPUs).
+Each ClickPipe defaults to 1 replica that is provided with 512 MiB of RAM and 0.125 vCPU (XS).
+This corresponds to **0.0625** ClickHouse compute units (1 unit = 8 GiB RAM, 2 vCPUs).
 
 #### What are the ClickPipes public prices? {#what-are-the-clickpipes-public-prices}
 
-- Compute: \$0.20 per unit per hour (\$0.05 per replica per hour)
+- Compute: \$0.20 per unit per hour (\$0.0125 per replica per hour for the default replica size)
 - Ingested data: \$0.04 per GB
 
+The price for the Compute dimension depends on the **number** and **size** of replica(s) in a ClickPipe. The default replica size can be adjusted using vertical scaling, and each replica size is priced as follows:
+
+| Replica Size               | Compute Units | RAM     | vCPU   | Price per Hour |
+|----------------------------|---------------|---------|--------|----------------|
+| Extra Small (XS) (default) | 0.0625        | 512 MiB | 0.125. | $0.0125        |
+| Small (S)                  | 0.125         | 1 GiB   | 0.25   | $0.025         |
+| Medium (M)                 | 0.25          | 2 GiB   | 0.5    | $0.05          |
+| Large (L)                  | 0.5           | 4 GiB   | 1.0    | $0.10          |
+| Extra Large (XL)           | 1.0           | 8 GiB   | 2.0    | $0.20          |
+
 #### How does it look in an illustrative example? {#how-does-it-look-in-an-illustrative-example}
 
-The following examples assume a single replica unless explicitly mentioned.
+The following examples assume a single M-sized replica, unless explicitly mentioned.
 
 <table><thead>
   <tr>

docs/cloud/manage/billing.md

@@ -11,5 +11,5 @@ This section of the documentation covers topics related to billing, and contains
 |---------------------------------------|----------------------------------------------------------------------|
 | [Overview](/cloud/marketplace/marketplace-billing)                       | Overview and FAQ pages for marketplace billing.                      | 
 | [Payment Thresholds](/cloud/billing/payment-thresholds)             | Learn more about how payment thresholds work and how to adjust them. |
-| [Troubleshooting Billing Issues](/manage/troubleshooting-billing-issues) | Troubleshoot common billing issues.                                  |
+| [Troubleshooting Billing Issues](/manage/clickhouse-cloud-billing-compliance) | Troubleshoot common billing issues.                                  |
 | [Marketplace](/cloud/manage/)                    | Landing page for further marketplace related topics.                 |

docs/cloud/manage/billing/index.md

@@ -20,6 +20,11 @@ Get started with ClickHouse Cloud on the [AWS Marketplace](https://aws.amazon.co
 ## Prerequisites {#prerequisites}
 
 - A Private Offer from ClickHouse based on specific contract terms.
+- To connect a ClickHouse organization to your committed spend offer, you must be an admin of that organization.
+
+[Required permissions to view and accept your committed contract in AWS](https://docs.aws.amazon.com/marketplace/latest/buyerguide/private-offers-page.html#private-offers-page-permissions):
+- If you use AWS managed policies it is required to have the following permissions: `AWSMarketplaceRead-only`, `AWSMarketplaceManageSubscriptions`, or `AWSMarketplaceFullAccess`.
+- If you aren't using AWS managed policies it is required to have the following permissions: IAM action `aws-marketplace:ListPrivateListings` and `aws-marketplace:ViewSubscriptions`.
 
 ## Steps to sign up {#steps-to-sign-up}
 

docs/cloud/manage/billing/marketplace/aws-marketplace-committed.md

@@ -52,9 +52,9 @@ This corresponds to **0.25** ClickHouse compute units (1 unit = 8 GiB RAM, 2 vCP
 
 <summary>Can ClickPipes replicas be scaled?</summary>
 
-ClickPipes for streaming can be scaled horizontally
-by adding more replicas each with a base unit of **0.25** ClickHouse compute units.
-Vertical scaling is also available on demand for specific use cases (adding more CPU and RAM per replica).
+Yes, ClickPipes for streaming can be scaled both horizontally and vertically.
+Horizontal scaling adds more replicas to increase throughput, while vertical scaling increases the resources (CPU and RAM) allocated to each replica to handle more intensive workloads.
+This can be configured during ClickPipe creation, or at any other point under **Settings** -> **Advanced Settings** -> **Scaling**.
 
 </details>
 
@@ -142,4 +142,4 @@ The philosophy behind ClickPipes pricing is
 to cover the operating costs of the platform while offering an easy and reliable way to move data to ClickHouse Cloud.
 From that angle, our market analysis revealed that we are positioned competitively.
 
-</details>
+</details>

docs/cloud/manage/jan2025_faq/_snippets/_clickpipes_faq.md

@@ -33,4 +33,4 @@ Customers need to manually add a DNS entry to make name resolution work for the
 
 ## Configuring replica-aware routing {#configuring-replica-aware-routing}
 
-To enable Replica-aware routing, please contact [our support team](https://clickhouse.com/support).
+To enable Replica-aware routing, please contact [our support team](https://clickhouse.com/support/program).