DOCS-7657 - Fix links (#1038)

ccloud-observability/docs/additional-resources.rst

@@ -9,7 +9,7 @@ Additional Resources
 
 -  See advanced options for working with `ccloud-stack <https://docs.confluent.io/platform/current/tutorials/examples/ccloud/docs/ccloud-stack.html#advanced-options>`__.
 
--  See `Developing Client Applications on Confluent Cloud <https://docs.confluent.io/cloud/best-practices/index.html>`__ for a guide to configuring, monitoring, and
+-  See `Developing Client Applications on Confluent Cloud <https://docs.confluent.io/cloud/current/client-apps/index.html>`__ for a guide to configuring, monitoring, and
    optimizing your |ak| client applications when using |ccloud|.
 
 -  See the source code for `ccloud-exporter <https://github.com/Dabz/ccloudexporter>`__.

ccloud/docs/ccloud-stack.rst

@@ -247,7 +247,7 @@ Re-use Existing Environment
 
 By default, a new ``ccloud-stack`` creates a new environment.
 This means that, by default, ``./ccloud_stack_create.sh`` creates a new environment and ``./ccloud_stack_destroy.sh`` deletes the environment specified in the configuration file.
-However, due to |ccloud| `environment limits per organization <https://docs.confluent.io/cloud/features.html#resource-limits-for-ccloud>`__, it may be desirable to work within an existing environment.
+However, due to |ccloud| `environment limits per organization <https://docs.confluent.io/cloud/current/client-apps/resource-limits.html>`__, it may be desirable to work within an existing environment.
 
 When you create a new stack, to reuse an existing environment, set the parameter ``ENVIRONMENT`` with an existing environment ID, as shown in the example:
 

ccloud/docs/index.rst

@@ -159,7 +159,7 @@ The script uses the |ccloud| CLI to dynamically do the following in |ccloud|:
 Auto-generate Configurations to connect to |ccloud|
 ---------------------------------------------------
 
-The `configuration generation script <https://docs.confluent.io/cloud/cp-component/auto-generate-configs.html>`__ reads a configuration file and auto-generates delta configurations for all |cp| components and clients.
+The `configuration generation script <https://docs.confluent.io/cloud/current/cp-component/auto-generate-configs.html>`__ reads a configuration file and auto-generates delta configurations for all |cp| components and clients.
 Use these per-component configurations for |cp| components and clients connecting to |ccloud|:
 
 * |cp| Components:
@@ -228,7 +228,7 @@ You can build any example with a mix of fully-managed services in |ccloud| and s
 
       ./ccloud_stack_create.sh
 
-#. Run the `configuration generation script <https://docs.confluent.io/cloud/cp-component/auto-generate-configs.html>`__ , passing in that local configuration file (created in previous step) as input. This script generates delta configuration files for all |cp| components and clients, including information for bootstrap servers, endpoints, and credentials required to connect to |ccloud|.
+#. Run the `configuration generation script <https://docs.confluent.io/cloud/current/cp-component/auto-generate-configs.html>`__ , passing in that local configuration file (created in previous step) as input. This script generates delta configuration files for all |cp| components and clients, including information for bootstrap servers, endpoints, and credentials required to connect to |ccloud|.
 
    .. sourcecode:: bash
 
@@ -252,7 +252,7 @@ You can build any example with a mix of fully-managed services in |ccloud| and s
 
       docker-compose up -d <service>
 
-   In the case of running a self-managed connector locally that connects to |ccloud|, first add your desired connector to the base |kconnect-long| Docker image as described in `Add Connectors or Software <https://docs.confluent.io/connect/extending.html>`__, and then substitute that Docker image in your Docker Compose file.
+   In the case of running a self-managed connector locally that connects to |ccloud|, first add your desired connector to the base |kconnect-long| Docker image as described in `Add Connectors or Software <https://docs.confluent.io/home/connect/extending.html>`__, and then substitute that Docker image in your Docker Compose file.
 
 #. Refer to the :devx-examples:`library of bash functions|utils/ccloud_library.sh` for examples on how to interact with |ccloud| via the |ccloud| CLI.
 
@@ -263,7 +263,7 @@ Additional Resources
 ====================
 
 -  For a practical guide to configuring, monitoring, and optimizing your |ak|
-   client applications, see `Developing Client Applications on Confluent Cloud <https://docs.confluent.io/cloud/best-practices/index.html>`__.
+   client applications, see `Developing Client Applications on Confluent Cloud <https://docs.confluent.io/cloud/current/client-apps/index.html>`__.
 -  Learn how to use |crep-full| to copy Kafka data to |ccloud|, in different
    configurations that allow |kconnect-long| to be backed to |ccloud| or to your
    origin Kafka cluster. See :ref:`replicator-to-cloud-configurations` for more

ccloud/docs/replicator-to-cloud-configuration-types.rst

@@ -222,7 +222,7 @@ Configure ACLs
 Additional Resources
 ====================
 
-- For additional considerations on running |crep| to |ccloud|, refer to `Migrate Topics on Confluent Cloud Clusters <https://docs.confluent.io/cloud/migrate-topics-on-cloud-clusters.html>`__.
+- For additional considerations on running |crep| to |ccloud|, refer to `Migrate Topics on Confluent Cloud Clusters <https://docs.confluent.io/cloud/current/clusters/migrate-topics-on-cloud-clusters.html>`__.
 - To run a |ccloud| demo that showcases a hybrid |ak| cluster: one cluster is a
   self-managed |ak| cluster running locally, the other is a |ccloud| cluster, see
   :ref:`cp-demo`.

clients/docs/includes/client-example-schema-registry-1.rst

@@ -1,4 +1,4 @@
-As described in the `Quick Start for Schema Management on Confluent Cloud <https://docs.confluent.io/cloud/quickstart/schema-registry.html>`__ in the |ccloud| Console, enable
+As described in the `Quick Start for Schema Management on Confluent Cloud <https://docs.confluent.io/cloud/current/get-started/schema-registry.html>`__ in the |ccloud| Console, enable
 |ccloud| |sr| and create an API key and secret to connect
 to it.
 

kubernetes/docs/includes/replicator-cc-demo/ccloud-setup-aks.rst

@@ -96,7 +96,7 @@ API Key and Secret Configuration
 
 The ``ccloud`` CLI allows you to create API Keys to be used with client applications.
 
-.. tip:: You can also create the API Key using the `Confluent Cloud Console <https://docs.confluent.io/cloud/using/api-keys.html#edit-resource-specific-api-key-descriptions-using-the-ui>`__.
+.. tip:: You can also create the API Key using the `Confluent Cloud Console <https://docs.confluent.io/cloud/current/access-management/authenticate/api-keys/api-keys.html#edit-resource-specific-api-key-descriptions-using-the-ui>`__.
 
 #.  To create a new API Key:
 

kubernetes/docs/includes/replicator-cc-demo/ccloud-setup.rst

@@ -89,7 +89,7 @@ API Key and Secret Configuration
 
 The ``ccloud`` CLI allows you to create API Keys to be used with client applications.
 
-.. tip:: You can also create the API Key using the `Confluent Cloud Console <https://docs.confluent.io/cloud/using/api-keys.html#edit-resource-specific-api-key-descriptions-using-the-ui>`__.
+.. tip:: You can also create the API Key using the `Confluent Cloud Console <https://docs.confluent.io/cloud/current/access-management/authenticate/api-keys/api-keys.html#edit-resource-specific-api-key-descriptions-using-the-ui>`__.
 
 #.  To create a new API Key: