Merge pull request #3150 from ClickHouse/change_cloud_link

gingerwizard · web-flow · commit 3b7ac789041a · 2025-01-27T16:33:26.000Z
updated cloud link
diff --git a/docs/en/about-us/cloud.md b/docs/en/about-us/cloud.md
@@ -8,7 +8,7 @@ description: ClickHouse Cloud
 # ClickHouse Cloud
 
 ClickHouse Cloud is the cloud offering created by the original creators of the popular open-source OLAP database ClickHouse. 
-You can experience ClickHouse Cloud by [starting a free trial](https://clickhouse.cloud/signUp).
+You can experience ClickHouse Cloud by [starting a free trial](https://console.clickhouse.cloud/signUp).
 
 ### ClickHouse Cloud benefits:
 
diff --git a/docs/en/about-us/support.md b/docs/en/about-us/support.md
@@ -7,7 +7,7 @@ sidebar_position: 30
 
 ClickHouse provides Support Services for our ClickHouse Cloud users and customers. Our objective is a Support Services team that represents the ClickHouse product – unparalleled performance, ease of use, and exceptionally fast, high-quality results. For details, [visit our Support Services](https://clickhouse.com/support/program/) page.
 
-[Login to the Cloud console](https://clickhouse.cloud/support) and select **Help -> Support** from the menu options to open a new support case and view the status of your submitted cases. 
+[Login to the Cloud console](https://console.clickhouse.cloud/support) and select **Help -> Support** from the menu options to open a new support case and view the status of your submitted cases. 
 
 **Service level agreements ("SLA")**
 Classification of severity levels for issues reported and response times.
diff --git a/docs/en/cloud/get-started/cloud-quick-start.md b/docs/en/cloud/get-started/cloud-quick-start.md
@@ -10,13 +10,13 @@ import SQLConsoleDetail from '@site/docs/en/_snippets/_launch_sql_console.md';
 # ClickHouse Cloud Quick Start
 
 The quickest and easiest way to get up and running with ClickHouse is to create a new
-service in [ClickHouse Cloud](https://clickhouse.cloud).
+service in [ClickHouse Cloud](https://console.clickhouse.cloud).
 
 ## 1. Create a ClickHouse service 
 
-To create a free ClickHouse service in [ClickHouse Cloud](https://clickhouse.cloud), you just need to sign up by completing the following steps:
+To create a free ClickHouse service in [ClickHouse Cloud](https://console.clickhouse.cloud), you just need to sign up by completing the following steps:
 
-  - Create an account on the [sign-up page](https://clickhouse.cloud/signUp)
+  - Create an account on the [sign-up page](https://console.clickhouse.cloud/signUp)
   - You can choose to sign up using your email or via Google SSO, Microsoft SSO, AWS Marketplace, Google Cloud or Microsoft Azure
   - If you sign up using an email and password, remember to verify your email address within the next 24h via the link you receive in your email
   - Login using the username and password you just created
diff --git a/docs/en/cloud/manage/api/api-overview.md b/docs/en/cloud/manage/api/api-overview.md
@@ -29,4 +29,4 @@ The ClickHouse Cloud API is built on the open-source [OpenAPI specification](htt
 
 ## Support
 
-We recommend visiting [our Slack channel](https://clickhouse.com/slack) first to get quick support. If you'd like additional help or more info about our API and its capabilities, please contact ClickHouse Support at https://clickhouse.cloud/support
+We recommend visiting [our Slack channel](https://clickhouse.com/slack) first to get quick support. If you'd like additional help or more info about our API and its capabilities, please contact ClickHouse Support at https://console.clickhouse.cloud/support
diff --git a/docs/en/cloud/manage/billing.md b/docs/en/cloud/manage/billing.md
@@ -46,7 +46,7 @@ WHERE name = <your table name>
 ### What tools does ClickHouse offer to estimate the cost of running a service in the cloud if I have a self-managed deployment?
 
 The ClickHouse query log captures [key metrics](/docs/en/operations/system-tables/query_log) that can be used to estimate the cost of running a workload in ClickHouse Cloud. 
-For details on migrating from self-managed to ClickHouse Cloud please refer to the [migration documentation](/docs/en/cloud/migration/clickhouse-to-cloud), and contact [ClickHouse Cloud support](https://clickhouse.cloud/support) if you have further questions.
+For details on migrating from self-managed to ClickHouse Cloud please refer to the [migration documentation](/docs/en/cloud/migration/clickhouse-to-cloud), and contact [ClickHouse Cloud support](https://console.clickhouse.cloud/support) if you have further questions.
 
 ### What billing options are available for ClickHouse Cloud?
 
diff --git a/docs/en/cloud/manage/billing/marketplace/aws-marketplace-committed.md b/docs/en/cloud/manage/billing/marketplace/aws-marketplace-committed.md
@@ -42,7 +42,7 @@ It is critical to redirect to ClickHouse Cloud at this point and either register
 
 <br />
 
-If you are a new ClickHouse Cloud user, click **Register** at the bottom of the page. You will be prompted to create a new user and verify the email. After verifying your email, you can leave the ClickHouse Cloud login page and login using the new username at the [https://clickhouse.cloud](https://clickhouse.cloud).
+If you are a new ClickHouse Cloud user, click **Register** at the bottom of the page. You will be prompted to create a new user and verify the email. After verifying your email, you can leave the ClickHouse Cloud login page and login using the new username at the [https://console.clickhouse.cloud](https://console.clickhouse.cloud).
 
 <br />
 
diff --git a/docs/en/cloud/manage/billing/marketplace/aws-marketplace-payg.md b/docs/en/cloud/manage/billing/marketplace/aws-marketplace-payg.md
@@ -97,7 +97,7 @@ After filling out the above information, click on **Create Contract**. You can c
 
 <br />
 
-If you are a new ClickHouse Cloud user, click **Register** at the bottom of the page. You will be prompted to create a new user and verify the email. After verifying your email, you can leave the ClickHouse Cloud login page and login using the new username at the [https://clickhouse.cloud](https://clickhouse.cloud).
+If you are a new ClickHouse Cloud user, click **Register** at the bottom of the page. You will be prompted to create a new user and verify the email. After verifying your email, you can leave the ClickHouse Cloud login page and login using the new username at the [https://console.clickhouse.cloud](https://console.clickhouse.cloud).
 
 <br />
 
diff --git a/docs/en/cloud/manage/billing/marketplace/gcp-marketplace-committed.md b/docs/en/cloud/manage/billing/marketplace/gcp-marketplace-committed.md
@@ -105,7 +105,7 @@ It is critical to redirect to ClickHouse Cloud at this point and sign up or sign
 
 <br />
 
-If you are a new ClickHouse Cloud user, click **Register** at the bottom of the page. You will be prompted to create a new user and verify the email. After verifying your email, you can leave the ClickHouse Cloud login page and login using the new username at the [https://clickhouse.cloud](https://clickhouse.cloud).
+If you are a new ClickHouse Cloud user, click **Register** at the bottom of the page. You will be prompted to create a new user and verify the email. After verifying your email, you can leave the ClickHouse Cloud login page and login using the new username at the [https://console.clickhouse.cloud](https://console.clickhouse.cloud).
 
 <br />
 
diff --git a/docs/en/cloud/manage/billing/marketplace/gcp-marketplace-payg.md b/docs/en/cloud/manage/billing/marketplace/gcp-marketplace-payg.md
@@ -81,7 +81,7 @@ Get started with ClickHouse Cloud on the [GCP Marketplace](https://console.cloud
 
 <br />
 
-If you are a new ClickHouse Cloud user, click **Register** at the bottom of the page. You will be prompted to create a new user and verify the email. After verifying your email, you can leave the ClickHouse Cloud login page and login using the new username at the [https://clickhouse.cloud](https://clickhouse.cloud).
+If you are a new ClickHouse Cloud user, click **Register** at the bottom of the page. You will be prompted to create a new user and verify the email. After verifying your email, you can leave the ClickHouse Cloud login page and login using the new username at the [https://console.clickhouse.cloud](https://console.clickhouse.cloud).
 
 <br />
 
diff --git a/docs/en/cloud/manage/jan2025_faq/dimensions.md b/docs/en/cloud/manage/jan2025_faq/dimensions.md
@@ -59,7 +59,7 @@ For object storage connectors (S3 and GCS), only the ClickPipes compute cost is
 
 ### When does the new pricing model take effect?
 
-The new pricing model will take effect for all organizations created after **January 23rd, 2025**.
+The new pricing model will take effect for all organizations created after **January 27th, 2025**.
 
 ### What happens to current users?
 
diff --git a/docs/en/cloud/manage/jan2025_faq/summary.md b/docs/en/cloud/manage/jan2025_faq/summary.md
@@ -78,7 +78,7 @@ While changes are effective immediately for new customers, existing customers wi
 
 Detailed breakdown of effective dates is below:
 
-* **New Customers**: The new plans will take effect on **January 23, 2025** for new customers of ClickHouse Cloud. 
+* **New Customers**: The new plans will take effect on **January 27, 2025** for new customers of ClickHouse Cloud. 
 * **Existing PAYG Customers**: Pay-as-you-go (PAYG) customers will have 6 months until **July 23, 2025** to migrate to new plans.
 * **Existing Committed Spend Customers**: Customers with committed spend agreements can renegotiate their terms at the end of their current contract.
 * **New usage dimensions** for Data Transfer and ClickPipes are effective for both PAYG and Committed Spend customers 8 weeks following this announcement on **March 24, 2025**. 
diff --git a/docs/en/cloud/reference/changelog.md b/docs/en/cloud/reference/changelog.md
@@ -739,7 +739,7 @@ This release brings general availability of ClickPipes for Kafka, Confluent Clou
 
 ### Console changes
 - Added a self-service workflow to secure [access to Amazon S3 via IAM roles](/docs/en/cloud/security/secure-s3)
-- Introduced AI-assisted query suggestions in private preview (please [contact ClickHouse Cloud support](https://clickhouse.cloud/support) to try it out!)
+- Introduced AI-assisted query suggestions in private preview (please [contact ClickHouse Cloud support](https://console.clickhouse.cloud/support) to try it out!)
 
 ### Integrations changes 
 - Announced general availability of ClickPipes - a turnkey data ingestion service - for Kafka, Confluent Cloud, and Amazon MSK (see the [release blog](https://clickhouse.com/blog/clickpipes-is-generally-available))
@@ -809,8 +809,8 @@ This release brings the ability to spin up Dedicated Services, a new AWS region
 
 ### General updates
 - New AWS Australia region: Sydney (ap-southeast-2)
-- Dedicated tier services for demanding latency-sensitive workloads (please contact [support](https://clickhouse.cloud/support) to set it up)
-- Bring your own key (BYOK) for encrypting data on disk (please contact [support](https://clickhouse.cloud/support) to set it up)
+- Dedicated tier services for demanding latency-sensitive workloads (please contact [support](https://console.clickhouse.cloud/support) to set it up)
+- Bring your own key (BYOK) for encrypting data on disk (please contact [support](https://console.clickhouse.cloud/support) to set it up)
 
 ### Console changes
 - Improvements to observability metrics dashboard for asynchronous inserts
@@ -841,7 +841,7 @@ This release makes ClickHouse Cloud on GCP generally available, brings a Terrafo
 - Kafka Connector: It can be uploaded and installed on Confluent Cloud, added retry for interim connection problems, reset the incorrect connector state automatically
 
 ### ClickHouse 23.4 version upgrade 
-- Added JOIN support for parallel replicas (please contact [support](https://clickhouse.cloud/support) to set it up)
+- Added JOIN support for parallel replicas (please contact [support](https://console.clickhouse.cloud/support) to set it up)
 - Improved performance of lightweight deletes
 - Improved caching while processing large inserts
 
diff --git a/docs/en/cloud/security/saml-sso-setup.md b/docs/en/cloud/security/saml-sso-setup.md
@@ -104,7 +104,7 @@ We recommend setting up a **direct link to your organization** in addition to yo
    3. Log out of the ClickHouse organization. 
 
    4. Log in with your original authentication method to assign the Admin role to your new SSO account.
-   - For email + password accounts, please use `https://clickhouse.cloud/?with=email`.
+   - For email + password accounts, please use `https://console.clickhouse.cloud/?with=email`.
    - For social logins, please click the appropriate button (**Continue with Google** or **Continue with Microsoft**)
 
    5. Log out with your original authentication method and log back in via https://console.clickhouse.cloud OR the direct link you configured in 'Configure your SAML integration' above.
@@ -322,11 +322,11 @@ We only utilize service provider initiated SSO. This means users go to `https://
 
 ### Assigning User Roles
 
-Users will appear in your ClickHouse Cloud console after they are assigned to your IdP application and log in for the first time. At least one SSO user should be assigned the Admin role in your organization. Use social login or `https://clickhouse.cloud?with=email` to log in with your original authentication method to update your SSO role.
+Users will appear in your ClickHouse Cloud console after they are assigned to your IdP application and log in for the first time. At least one SSO user should be assigned the Admin role in your organization. Use social login or `https://console.clickhouse.cloud?with=email` to log in with your original authentication method to update your SSO role.
 
 ### Removing Non-SSO Users
 
-Once you have SSO users set up and have assigned at least one user the Admin role, the Admin can remove users using other methods (e.g. social authentication or user ID + password). Google authentication will continue to work after SSO is set up. User ID + password users will be automatically redirected to SSO based on their email domain unless users use `https://clickhouse.cloud?with=email`.
+Once you have SSO users set up and have assigned at least one user the Admin role, the Admin can remove users using other methods (e.g. social authentication or user ID + password). Google authentication will continue to work after SSO is set up. User ID + password users will be automatically redirected to SSO based on their email domain unless users use `https://console.clickhouse.cloud?with=email`.
 
 ### Managing Users
 
diff --git a/docs/en/engines/table-engines/integrations/s3queue.md b/docs/en/engines/table-engines/integrations/s3queue.md
@@ -4,8 +4,6 @@ sidebar_position: 181
 sidebar_label: S3Queue
 ---
 
-import ScalePlanFeatureBadge from '@theme/badges/ScalePlanFeatureBadge'
-
 # S3Queue Table Engine
 
 This engine provides integration with [Amazon S3](https://aws.amazon.com/s3/) ecosystem and allows streaming import. This engine is similar to the [Kafka](../../../engines/table-engines/integrations/kafka.md), [RabbitMQ](../../../engines/table-engines/integrations/rabbitmq.md) engines, but provides S3-specific features.
@@ -196,8 +194,6 @@ Engine supports all s3 related settings. For more information about S3 settings
 
 ## S3 role-based access
 
-<ScalePlanFeatureBadge feature="S3 role-based access"/>
-
 The s3Queue table engine supports role-based access.
 Refer to the documentation [here](https://clickhouse.com/docs/en/cloud/security/secure-s3) for steps to configure a role to access your bucket.
 
diff --git a/docs/en/migrations/bigquery/equivalent-concepts.md b/docs/en/migrations/bigquery/equivalent-concepts.md
@@ -50,7 +50,7 @@ Lastly, I/O scheduling allows users to restrict local and remote disk accesses f
 
 ### Permissions
 
-ClickHouse Cloud [controls user access](/en/cloud/security/cloud-access-management) in two places, via the [cloud console](/en/cloud/get-started/sql-console) and via the database. Console access is managed via the [clickhouse.cloud](https://clickhouse.cloud) user interface. Database access is managed via database user accounts and roles. Additionally, console users can be granted roles within the database that enable the console user to interact with the database via our [SQL console](/en/integrations/sql-clients/sql-console).
+ClickHouse Cloud [controls user access](/en/cloud/security/cloud-access-management) in two places, via the [cloud console](/en/cloud/get-started/sql-console) and via the database. Console access is managed via the [clickhouse.cloud](https://console.clickhouse.cloud) user interface. Database access is managed via database user accounts and roles. Additionally, console users can be granted roles within the database that enable the console user to interact with the database via our [SQL console](/en/integrations/sql-clients/sql-console).
 
 ## Data types
 
diff --git a/docs/en/whats-new/changelog/2022.md b/docs/en/whats-new/changelog/2022.md
@@ -310,7 +310,7 @@ Refer to this issue on GitHub for more details: https://github.com/ClickHouse/Cl
 
 #### Build/Testing/Packaging Improvement
 * Add fuzzer for table definitions [#40096](https://github.com/ClickHouse/ClickHouse/pull/40096) ([Anton Popov](https://github.com/CurtizJ)). This represents the biggest advancement for ClickHouse testing in this year so far.
-* Beta version of the ClickHouse Cloud service is released: [https://clickhouse.cloud/](https://clickhouse.cloud/). It provides the easiest way to use ClickHouse (even slightly easier than the single-command installation).
+* Beta version of the ClickHouse Cloud service is released: [https://console.clickhouse.cloud/](https://console.clickhouse.cloud/). It provides the easiest way to use ClickHouse (even slightly easier than the single-command installation).
 * Added support of WHERE clause generation to AST Fuzzer and possibility to add or remove ORDER BY and WHERE clause. [#38519](https://github.com/ClickHouse/ClickHouse/pull/38519) ([Ilya Yatsishin](https://github.com/qoega)).
 * Aarch64 binaries now require at least ARMv8.2, released in 2016. Most notably, this enables use of ARM LSE, i.e. native atomic operations. Also, CMake build option "NO_ARMV81_OR_HIGHER" has been added to allow compilation of binaries for older ARMv8.0 hardware, e.g. Raspberry Pi 4. [#41610](https://github.com/ClickHouse/ClickHouse/pull/41610) ([Robert Schulze](https://github.com/rschu1ze)).
 * Allow building ClickHouse with Musl (small changes after it was already supported but broken). [#41987](https://github.com/ClickHouse/ClickHouse/pull/41987) ([Alexey Milovidov](https://github.com/alexey-milovidov)).
diff --git a/docs/en/whats-new/changelog/2023.md b/docs/en/whats-new/changelog/2023.md
@@ -2033,7 +2033,7 @@ Add settings input_format_tsv/csv/custom_detect_header that enable this behaviou
 * Add fast path for: - `col like '%%'`; - `col like '%'`; - `col not like '%'`; - `col not like '%'`; - `match(col, '.*')`. [#45244](https://github.com/ClickHouse/ClickHouse/pull/45244) ([李扬](https://github.com/taiyang-li)).
 * Slightly improve happy path optimisation in filtering (WHERE clause). [#45289](https://github.com/ClickHouse/ClickHouse/pull/45289) ([Nikita Taranov](https://github.com/nickitat)).
 * Provide monotonicity info for `toUnixTimestamp64*` to enable more algebraic optimizations for index analysis. [#44116](https://github.com/ClickHouse/ClickHouse/pull/44116) ([Nikita Taranov](https://github.com/nickitat)).
-* Allow the configuration of temporary data for query processing (spilling to disk) to cooperate with the filesystem cache (taking up the space from the cache disk) [#43972](https://github.com/ClickHouse/ClickHouse/pull/43972) ([Vladimir C](https://github.com/vdimir)). This mainly improves [ClickHouse Cloud](https://clickhouse.cloud/), but can be used for self-managed setups as well, if you know what to do.
+* Allow the configuration of temporary data for query processing (spilling to disk) to cooperate with the filesystem cache (taking up the space from the cache disk) [#43972](https://github.com/ClickHouse/ClickHouse/pull/43972) ([Vladimir C](https://github.com/vdimir)). This mainly improves [ClickHouse Cloud](https://console.clickhouse.cloud/), but can be used for self-managed setups as well, if you know what to do.
 * Make `system.replicas` table do parallel fetches of replicas statuses. Closes [#43918](https://github.com/ClickHouse/ClickHouse/issues/43918). [#43998](https://github.com/ClickHouse/ClickHouse/pull/43998) ([Nikolay Degterinsky](https://github.com/evillique)).
 * Optimize memory consumption during backup to S3: files to S3 now will be copied directly without using `WriteBufferFromS3` (which could use a lot of memory). [#45188](https://github.com/ClickHouse/ClickHouse/pull/45188) ([Vitaly Baranov](https://github.com/vitlibar)).
 * Add a cache for async block ids. This will reduce the number of requests of ZooKeeper when we enable async inserts deduplication. [#45106](https://github.com/ClickHouse/ClickHouse/pull/45106) ([Han Fei](https://github.com/hanfei1991)).
diff --git a/knowledgebase/finding_expensive_queries_by_memory_usage.mdx b/knowledgebase/finding_expensive_queries_by_memory_usage.mdx
@@ -16,7 +16,7 @@ The following useful query shows which of your executed queries used the most me
 A couple of comments about this query:
 
 - the results are computed from the past day (`now() - toIntervalDay(1))`) but you can easily modify the time interval
-- it assumes you have a cluster named `default`, which is the name of your cluster in [ClickHouse Cloud](https://clickhouse.cloud). Change `default` to the name of your cluster
+- it assumes you have a cluster named `default`, which is the name of your cluster in [ClickHouse Cloud](https://console.clickhouse.cloud). Change `default` to the name of your cluster
 - if you do not have a cluster, see the query listed at the end of this article
 
 
diff --git a/knowledgebase/how-to-check-my-clickhouse-cloud-sevice-state.mdx b/knowledgebase/how-to-check-my-clickhouse-cloud-sevice-state.mdx
diff --git a/knowledgebase/why_recommend_clickhouse_keeper_over_zookeeper.mdx b/knowledgebase/why_recommend_clickhouse_keeper_over_zookeeper.mdx
diff --git a/plugins/menuItems.json b/plugins/menuItems.json
diff --git a/src/theme/DocItem/TOC/Desktop/index.js b/src/theme/DocItem/TOC/Desktop/index.js
diff --git a/src/theme/Navbar/Content/index.js b/src/theme/Navbar/Content/index.js
diff --git a/src/theme/Navbar/MobileSidebar/PrimaryMenu/index.js b/src/theme/Navbar/MobileSidebar/PrimaryMenu/index.js

Original file line number	Diff line number	Diff line change
`@@ -29,4 +29,4 @@ The ClickHouse Cloud API is built on the open-source [OpenAPI specification](htt`
`29`	`29`
`30`	`30`	`## Support`
`31`	`31`
`32`		`-We recommend visiting [our Slack channel](https://clickhouse.com/slack) first to get quick support. If you'd like additional help or more info about our API and its capabilities, please contact ClickHouse Support at https://clickhouse.cloud/support`
	`32`	`+We recommend visiting [our Slack channel](https://clickhouse.com/slack) first to get quick support. If you'd like additional help or more info about our API and its capabilities, please contact ClickHouse Support at https://console.clickhouse.cloud/support`