Merge branch 'main' into issue-2110-threshold-rule-grouping

Author: nastasha-solomon

deploy-manage/deploy/cloud-enterprise/ece-install-offline-images.md

@@ -17,13 +17,13 @@ The first table contains the stack versions shipped with the current {{version.e
 | Docker images included with {{ece}} {{version.ece}} |
 | --- |
 | docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:{{version.ece}} |
-| docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.8 |
-| docker.elastic.co/cloud-release/kibana-cloud:8.18.8 |
-| docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.8 |
-| docker.elastic.co/cloud-release/enterprise-search-cloud:8.18.8 |
-| docker.elastic.co/cloud-release/elasticsearch-cloud-ess:9.0.8 |
-| docker.elastic.co/cloud-release/kibana-cloud:9.0.8 |
-| docker.elastic.co/cloud-release/elastic-agent-cloud:9.0.8 |
+| docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-8}} |
+| docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-8}} |
+| docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-8}} |
+| docker.elastic.co/cloud-release/enterprise-search-cloud:{{ece-docker-images-8}} |
+| docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-9}} |
+| docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-9}} |
+| docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-9}} |
 
 $$$ece-all-stacks$$$Additional {{stack}} versions are available as Docker images that you can use with ECE. For offline installations, you need to download both the {{stack}} pack and the Docker images for the same version.
 

deploy-manage/deploy/cloud-enterprise/ece-install-offline-no-registry.md

@@ -19,13 +19,13 @@ To perform an offline installation without a private Docker registry, you have t
 
     ```sh subs=true
     docker pull docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:{{version.ece}}
-    docker pull docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.8
-    docker pull docker.elastic.co/cloud-release/kibana-cloud:8.18.8
-    docker pull docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.8
-    docker pull docker.elastic.co/cloud-release/enterprise-search-cloud:8.18.8
-    docker pull docker.elastic.co/cloud-release/elasticsearch-cloud-ess:9.0.8
-    docker pull docker.elastic.co/cloud-release/kibana-cloud:9.0.8
-    docker pull docker.elastic.co/cloud-release/elastic-agent-cloud:9.0.8
+    docker pull docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-8}}
+    docker pull docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-8}}
+    docker pull docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-8}}
+    docker pull docker.elastic.co/cloud-release/enterprise-search-cloud:{{ece-docker-images-8}}
+    docker pull docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-9}}
+    docker pull docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-9}}
+    docker pull docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-9}}
     ```
 
     ::::{note}
@@ -36,27 +36,27 @@ To perform an offline installation without a private Docker registry, you have t
 
     ```sh subs=true
     docker save -o ece.{{version.ece}}.tar docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:{{version.ece}}
-    docker save -o es.8.18.2.tar docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.8
-    docker save -o kibana.8.18.2.tar docker.elastic.co/cloud-release/kibana-cloud:8.18.8
-    docker save -o apm.8.18.2.tar docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.8
-    docker save -o enterprise-search.8.18.2.tar docker.elastic.co/cloud-release/enterprise-search-cloud:8.18.8
-    docker save -o es.9.0.1.tar docker.elastic.co/cloud-release/elasticsearch-cloud-ess:9.0.8
-    docker save -o kibana.9.0.1.tar docker.elastic.co/cloud-release/kibana-cloud:9.0.8
-    docker save -o apm.9.0.1.tar docker.elastic.co/cloud-release/elastic-agent-cloud:9.0.8
+    docker save -o es.8.18.2.tar docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-8}}
+    docker save -o kibana.8.18.2.tar docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-8}}
+    docker save -o apm.8.18.2.tar docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-8}}
+    docker save -o enterprise-search.8.18.2.tar docker.elastic.co/cloud-release/enterprise-search-cloud:{{ece-docker-images-8}}
+    docker save -o es.9.0.1.tar docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-9}}
+    docker save -o kibana.9.0.1.tar docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-9}}
+    docker save -o apm.9.0.1.tar docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-9}}
     ```
 
 3. Copy the .tar files to a location on your network where they are available to each host where you plan to install {{ece}}. Alternatively, you can copy the .tar files to each host directly.
 4. On each host, load the images into Docker, replacing `FILE_PATH` with the correct path to the .tar files:
 
     ```sh subs=true
     docker load < FILE_PATH/ece.{{version.ece}}.tar
-    docker load < FILE_PATH/es.8.18.8.tar
-    docker load < FILE_PATH/kibana.8.18.8.tar
-    docker load < FILE_PATH/apm.8.18.8.tar
-    docker load < FILE_PATH/enterprise-search.8.18.8.tar
-    docker load < FILE_PATH/es.9.0.8.tar
-    docker load < FILE_PATH/kibana.9.0.8.tar
-    docker load < FILE_PATH/apm.9.0.8.tar
+    docker load < FILE_PATH/es.{{ece-docker-images-8}}.tar
+    docker load < FILE_PATH/kibana.{{ece-docker-images-8}}.tar
+    docker load < FILE_PATH/apm.{{ece-docker-images-8}}.tar
+    docker load < FILE_PATH/enterprise-search.{{ece-docker-images-8}}.tar
+    docker load < FILE_PATH/es.{{ece-docker-images-9}}.tar
+    docker load < FILE_PATH/kibana.{{ece-docker-images-9}}.tar
+    docker load < FILE_PATH/apm.{{ece-docker-images-9}}.tar
     ```
 
 5. Optional: Remove the .tar files after installation.

deploy-manage/deploy/cloud-enterprise/ece-install-offline-with-registry.md

@@ -25,13 +25,13 @@ Installing ECE on multiple hosts with your own registry server is simpler, becau
 
     ```sh subs=true
     docker pull docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:{{version.ece}}
-    docker pull docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.8
-    docker pull docker.elastic.co/cloud-release/kibana-cloud:8.18.8
-    docker pull docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.8
-    docker pull docker.elastic.co/cloud-release/enterprise-search-cloud:8.18.8
-    docker pull docker.elastic.co/cloud-release/elasticsearch-cloud-ess:9.0.8
-    docker pull docker.elastic.co/cloud-release/kibana-cloud:9.0.8
-    docker pull docker.elastic.co/cloud-release/elastic-agent-cloud:9.0.8
+    docker pull docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-8}}
+    docker pull docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-8}}
+    docker pull docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-8}}
+    docker pull docker.elastic.co/cloud-release/enterprise-search-cloud:{{ece-docker-images-8}}
+    docker pull docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-9}}
+    docker pull docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-9}}
+    docker pull docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-9}}
     ```
 
     ::::{note}
@@ -42,26 +42,26 @@ Installing ECE on multiple hosts with your own registry server is simpler, becau
 
     ```sh subs=true
     docker tag docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:{{version.ece}} REGISTRY/cloud-enterprise/elastic-cloud-enterprise:{{version.ece}}
-    docker tag docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.2 REGISTRY/cloud-release/elasticsearch-cloud-ess:8.18.8
-    docker tag docker.elastic.co/cloud-release/kibana-cloud:8.18.2 REGISTRY/cloud-release/kibana-cloud:8.18.8
-    docker tag docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.2 REGISTRY/cloud-release/elastic-agent-cloud:8.18.8
-    docker tag docker.elastic.co/cloud-release/enterprise-search-cloud:8.18.2 REGISTRY/cloud-release/enterprise-search-cloud:8.18.8
-    docker tag docker.elastic.co/cloud-release/elasticsearch-cloud-ess:9.0.1 REGISTRY/cloud-release/elasticsearch-cloud-ess:9.0.8
-    docker tag docker.elastic.co/cloud-release/kibana-cloud:9.0.1 REGISTRY/cloud-release/kibana-cloud:9.0.8
-    docker tag docker.elastic.co/cloud-release/elastic-agent-cloud:9.0.1 REGISTRY/cloud-release/elastic-agent-cloud:9.0.8
+    docker tag docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.2 REGISTRY/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-8}}
+    docker tag docker.elastic.co/cloud-release/kibana-cloud:8.18.2 REGISTRY/cloud-release/kibana-cloud:{{ece-docker-images-8}}
+    docker tag docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.2 REGISTRY/cloud-release/elastic-agent-cloud:{{ece-docker-images-8}}
+    docker tag docker.elastic.co/cloud-release/enterprise-search-cloud:8.18.2 REGISTRY/cloud-release/enterprise-search-cloud:{{ece-docker-images-8}}
+    docker tag docker.elastic.co/cloud-release/elasticsearch-cloud-ess:9.0.1 REGISTRY/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-9}}
+    docker tag docker.elastic.co/cloud-release/kibana-cloud:9.0.1 REGISTRY/cloud-release/kibana-cloud:{{ece-docker-images-9}}
+    docker tag docker.elastic.co/cloud-release/elastic-agent-cloud:9.0.1 REGISTRY/cloud-release/elastic-agent-cloud:{{ece-docker-images-9}}
     ```
 
 4. Push the Docker images to your private Docker registry, using the same tags from the previous step. Replace `REGISTRY` with your actual registry URL, for example `my.private.repo:5000`:
 
     ```sh subs=true
     docker push REGISTRY/cloud-enterprise/elastic-cloud-enterprise:{{version.ece}}
-    docker push REGISTRY/cloud-release/elasticsearch-cloud-ess:8.18.8
-    docker push REGISTRY/cloud-release/kibana-cloud:8.18.8
-    docker push REGISTRY/cloud-release/elastic-agent-cloud:8.18.8
-    docker push REGISTRY/cloud-release/enterprise-search-cloud:8.18.8
-    docker push REGISTRY/cloud-release/elasticsearch-cloud-ess:9.0.8
-    docker push REGISTRY/cloud-release/kibana-cloud:9.0.8
-    docker push REGISTRY/cloud-release/elastic-agent-cloud:9.0.8
+    docker push REGISTRY/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-8}}
+    docker push REGISTRY/cloud-release/kibana-cloud:{{ece-docker-images-8}}
+    docker push REGISTRY/cloud-release/elastic-agent-cloud:{{ece-docker-images-8}}
+    docker push REGISTRY/cloud-release/enterprise-search-cloud:{{ece-docker-images-8}}
+    docker push REGISTRY/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-9}}
+    docker push REGISTRY/cloud-release/kibana-cloud:{{ece-docker-images-9}}
+    docker push REGISTRY/cloud-release/elastic-agent-cloud:{{ece-docker-images-9}}
     ```
 
 5. On an internet-connected host, download the installation script:

deploy-manage/deploy/elastic-cloud/serverless.md

@@ -65,6 +65,8 @@ To learn more about serverless status, see [Service status](../../cloud-organiza
 
 The following FAQ addresses common questions about using {{serverless-full}} projects.
 
+For information about upcoming features, refer to our [roadmap](https://www.elastic.co/cloud/serverless/roadmap).
+
 ### Pricing and availability
 **Q: Where can I learn about pricing for {{serverless-short}}?**  
 A: See pricing information for [{{es-serverless}}](https://www.elastic.co/pricing/serverless-search), [{{observability}}](https://www.elastic.co/pricing/serverless-observability), and [{{sec-serverless}}](https://www.elastic.co/pricing/serverless-security).
@@ -73,6 +75,7 @@ A: See pricing information for [{{es-serverless}}](https://www.elastic.co/pricin
 A: {{serverless-full}} is available in select AWS, GCP, and Azure regions, with plans to expand to more regions. For more information, refer to [](/deploy-manage/deploy/elastic-cloud/regions.md).
 
 ### Data management
+
 **Q: How can I move data to or from {{serverless-short}} projects?**  
 A: We are working on data migration tools. In the interim, [use Logstash](logstash://reference/index.md) with {{es}} input and output plugins to move data to and from {{serverless-short}} projects.
 
@@ -83,6 +86,9 @@ A: Request for project backups or restores is currently unsupported, and we are
 **Q: How can I create {{serverless-full}} service accounts?**  
 A: Create API keys for service accounts in your {{serverless-short}} projects. Options to automate the creation of API keys with tools such as Terraform will be available in the future.
 
+**Q: What compliance and privacy standards does {{serverless-full}} adhere to?**  
+A: Alongside the entire Elastic platform, {{serverless-full}} is independently audited and certified to meet industry-leading compliance and privacy standards. Refer to the [Elastic Trust Center](https://www.elastic.co/trust) for more information. Further details about specific standards are available on our [roadmap](https://www.elastic.co/cloud/serverless/roadmap).
+
 ### Project lifecycle and support
 **Q: How does {{serverless-full}} ensure compatibility between software versions?**  
 A: Connections and configurations are unaffected by upgrades. To ensure compatibility between software versions, quality testing and API versioning are used.

deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md

@@ -121,7 +121,7 @@ Depending on your selected installation method, you may have to provide the foll
 
 With this authentication method, you need to create an API key to grant access to your cluster. Complete the following steps:
 
-1. From your {{ecloud}} home page, select a deployment.
+1. Open your self-managed cluster's Kibana
 2. Go to the **API keys** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 3.  Select **Create API key**.
 4. In the flyout, enter a name for your key and select **User API key**.
@@ -167,7 +167,7 @@ With this authentication method, you need to create an API key to grant access t
 
 With this authentication method, you need the username and password of a user with the necessary privileges to grant access to your cluster. There are two ways to set up a user with the these privileges:
 
-* (Recommended) From your {{ecloud}} home page, select a deployment and go to **Developer tools**. In **Console**, run the following command:
+* (Recommended) Open your self-managed cluster's Kibana and go to **Developer tools**. In **Console**, run the following command:
 ```js
 POST /_security/role/autoops
 {

deploy-manage/remote-clusters/_snippets/rcs-elasticsearch-api-snippet-self.md

@@ -0,0 +1,42 @@
+<!--
+This snippet is in use in the following locations:
+- ece-remote-cluster-self-managed.md
+- ec-remote-cluster-self-managed.md
+-->
+To configure a self-managed cluster as a remote cluster, use the [cluster update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings). Configure the following fields:
+
+* `mode`: `proxy`
+* `proxy_address`: Enter the endpoint of the remote self-managed cluster, including the hostname, FQDN, or IP address, and the port. Both IPv4 and IPv6 addresses are supported.
+
+  Make sure you use the correct port for your authentication method:
+  * **API keys**: Use the port configured in the remote cluster interface of the remote cluster (defaults to `9443`).  
+  * **TLS Certificates**: Use the {{es}} transport port (defaults to `9300`).
+
+  When using an IPv6 address, enclose it in square brackets followed by the port number. For example: `[2001:db8::1]:9443`.
+
+* `server_name`: Specify a value if the certificate presented by the remote cluster is signed for a different name than the proxy_address.
+
+This is an example of the API call to `_cluster/settings`:
+
+```json
+PUT /_cluster/settings
+{
+  "persistent": {
+    "cluster": {
+      "remote": {
+        "alias-for-my-remote-cluster": {
+          "mode":"proxy",
+          "proxy_address": "a542184a7a7d45b88b83f95392f450ab.192.168.44.10.ip.es.io:9300",
+          "server_name": "a542184a7a7d45b88b83f95392f450ab.192.168.44.10.ip.es.io"
+        }
+      }
+    }
+  }
+}
+```
+
+::::{note}
+When using API key authentication, the cluster alias must match the one you configured when adding the API key in the Cloud UI.
+::::
+
+For a full list of available client connection settings in proxy mode, refer to [remote cluster settings reference](elasticsearch://reference/elasticsearch/configuration-reference/remote-clusters.md#remote-cluster-proxy-settings).

deploy-manage/remote-clusters/_snippets/rcs-kibana-api-snippet-self.md

@@ -0,0 +1,28 @@
+<!--
+This snippet is in use in the following locations:
+- ece-remote-cluster-self-managed.md
+- ec-remote-cluster-self-managed.md
+-->
+1. Go to the **Remote Clusters** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+2. Select **Add a remote cluster**.
+2. In **Select connection type**, choose the authentication mechanism you prepared earlier (**API keys** or **Certificates**), and click **Next**.
+
+3. In **Add connection information**, fill in the following fields:
+
+    * **Remote cluster name**: This *cluster alias* is a unique identifier that represents the connection to the remote cluster and is used to distinguish local and remote indices.
+
+      When using API key authentication, this alias must match the **Remote cluster name** you configured when adding the API key in the Cloud UI.
+    * **Remote address**: Enter the endpoint of the remote self-managed cluster, including the hostname, FQDN, or IP address, and the port.
+
+      Make sure you use the correct port for your authentication method:
+      * **API keys**: Use the port configured in the remote cluster interface of the remote cluster (defaults to `9443`).  
+      * **TLS Certificates**: Use the {{es}} transport port (defaults to `9300`).
+
+      Starting with {{kib}} 9.2, this field also supports IPv6 addresses. When using an IPv6 address, enclose it in square brackets followed by the port number. For example: `[2001:db8::1]:9443`.
+
+    * **Configure advanced options** (optional): Expand this section if you need to customize additional settings.
+      * **TLS server name**: Specify a value if the certificate presented by the remote cluster is signed for a different name than the remote address.
+      * **Socket connections**: Define the number of connections to open with the remote cluster.
+
+4. Click **Next**.
+5. In **Confirm setup**, click **Add remote cluster** (you have already established trust in a previous step).

deploy-manage/remote-clusters/ec-migrate-ccs.md

@@ -9,9 +9,9 @@ products:
   - id: cloud-hosted
 ---
 
-# Migrate from the cross-cluster search deployment template in {{ech}} [ec-migrate-ccs]
+# Migrate from the legacy cross-cluster search deployment template in {{ech}} [ec-migrate-ccs]
 
-The cross-cluster search deployment template is now deprecated and has been removed from the {{ecloud}} Console. You no longer need to use the dedicated cross-cluster template to search across deployments. Instead, you can now use any template to [configure remote clusters](ec-enable-ccs.md) and search across them. Existing deployments created using this template are not affected, but they are required to migrate to another template before upgrading to {{stack}} 8.x.
+The legacy cross-cluster search deployment template has been removed from the {{ecloud}} Console. You no longer need a dedicated template to search across deployments. Instead, you can now use any template to [configure remote clusters](ec-enable-ccs.md) and search across them. Existing deployments created using this template are not affected, but they are required to migrate to another template before upgrading to {{stack}} 8.x.
 
 There are two different approaches to do this migration: