Merge branch 'main' into leemthompo-patch-1

leemthompo · web-flow · commit 98f626b4ea38 · 2025-04-23T16:06:08.000+02:00
diff --git a/deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md b/deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md
@@ -40,7 +40,7 @@ For detailed {{es-serverless}} project rates, see the [{{es-serverless}} pricing
 You can control costs using the following strategies:
 
 * **Search Power setting:** [Search Power](../../deploy/elastic-cloud/project-settings.md#elasticsearch-manage-project-search-power-settings) controls the speed of searches against your data. With Search Power, you can improve search performance by adding more resources for querying, or you can reduce provisioned resources to cut costs.
-* **Time series data retention:** By limiting the number of days of [time series data](../../../solutions/search/ingest-for-search.md#elasticsearch-ingest-time-series-data) that are available for caching, you can reduce the number of search VCUs required.
+* **Search boost window**: By limiting the number of days of [time series data](../../../solutions/search/ingest-for-search.md#elasticsearch-ingest-time-series-data) that are available for caching, you can reduce the number of search VCUs required.
 * **Machine learning trained model autoscaling:** Configure your trained model deployment to allow it to scale down to zero allocations when there are no active inference requests:
 
     * When starting or updating a trained model deployment, [Enable adaptive resources](../../autoscaling/trained-model-autoscaling.md#enabling-autoscaling-in-kibana-adaptive-resources) and set the VCU usage level to **Low**.
diff --git a/deploy-manage/deploy/self-managed/_snippets/check-es-running.md b/deploy-manage/deploy/self-managed/_snippets/check-es-running.md
@@ -1,7 +1,7 @@
 You can test that your {{es}} node is running by sending an HTTPS request to port `9200` on `localhost`:
 
 ```sh subs=true
-curl --cacert {{es-conf}}{{slash}}certs{{slash}}http_ca.crt {{escape}} <1>
+curl --cacert {{es-conf}}{{slash}}certs{{slash}}http_ca.crt <1>
 -u elastic:$ELASTIC_PASSWORD https://localhost:9200 <2>
 ```
 1. `--cacert`: Path to the generated `http_ca.crt` certificate for the HTTP layer.
@@ -29,4 +29,4 @@ The call returns a response like this:
   },
   "tagline" : "You Know, for Search"
 }
-```
+```
diff --git a/deploy-manage/deploy/self-managed/_snippets/pw-env-var.md b/deploy-manage/deploy/self-managed/_snippets/pw-env-var.md
@@ -1,9 +1,9 @@
 We recommend storing the `elastic` password as an environment variable in your shell. For example:
 
 ```sh subs=true
-{{export}}ELASTIC_PASSWORD="your_password"
+{{export}} ELASTIC_PASSWORD="your_password"
 ```
 
 If you have password-protected the {{es}} keystore, you will be prompted to enter the keystore’s password. See [Secure settings](/deploy-manage/security/secure-settings.md) for more details.
 
-To learn how to reset this password, refer to [](/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-sm.md).
+To learn how to reset this password, refer to [](/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-sm.md).
diff --git a/deploy-manage/security/supported-ssltls-versions-by-jdk-version.md b/deploy-manage/security/supported-ssltls-versions-by-jdk-version.md
@@ -24,20 +24,16 @@ Check your security provider’s release notes for information on TLS support.
 :   SSL v3 is supported on all {{es}} [compatible JDKs](../deploy/self-managed/installing-elasticsearch.md#jvm-version) but is disabled by default. See [Enabling additional SSL/TLS versions on your JDK](#jdk-enable-tls-protocol).
 
 `TLSv1`
-:   TLS v1.0 is supported on all {{es}} [compatible JDKs](../deploy/self-managed/installing-elasticsearch.md#jvm-version). Some newer JDKs, including the JDK bundled with {{es}}, disable TLS v1.0 by default. See [Enabling additional SSL/TLS versions on your JDK](#jdk-enable-tls-protocol).
+:   TLS v1.0 is supported on all {{es}} [compatible JDKs](../deploy/self-managed/installing-elasticsearch.md#jvm-version) but is disabled by default. See [Enabling additional SSL/TLS versions on your JDK](#jdk-enable-tls-protocol).
 
 `TLSv1.1`
-:   TLS v1.1 is supported on all {{es}} [compatible JDKs](../deploy/self-managed/installing-elasticsearch.md#jvm-version). Some newer JDKs, including the JDK bundled with {{es}}, disable TLS v1.1 by default. See [Enabling additional SSL/TLS versions on your JDK](#jdk-enable-tls-protocol).
+:   TLS v1.1 is supported on all {{es}} [compatible JDKs](../deploy/self-managed/installing-elasticsearch.md#jvm-version) but is disabled by default. See [Enabling additional SSL/TLS versions on your JDK](#jdk-enable-tls-protocol).
 
 `TLSv1.2`
 :   TLS v1.2 is supported on all {{es}} [compatible JDKs](../deploy/self-managed/installing-elasticsearch.md#jvm-version). It is enabled by default on all JDKs that are supported by {{es}}, including the bundled JDK.
 
 `TLSv1.3`
-:   TLS v1.3 is supported on JDK11 and later, and JDK8 builds newer than 8u261 (including the most recent release of each JDK8 distribution that {{es}} supports). TLS v1.3 is supported and enabled by default on the JDK that is bundled with {{es}}.
-
-    ::::{note}
-    Although {{es}} supports running on older JDK8 builds without TLS v1.3, we recommend upgrading to a JDK version that includes TLS v1.3 for better support and updates.
-    ::::
+:   TLS v1.3 is supported on all {{es}} [compatible JDKs](../deploy/self-managed/installing-elasticsearch.md#jvm-version). It is enabled by default on all JDKs that are supported by {{es}}, including the bundled JDK.
 
 
 ## Enabling additional SSL/TLS versions on your JDK [jdk-enable-tls-protocol]
@@ -59,10 +55,6 @@ For the {{es}} **bundled JDK**, the configuration file is in a sub directory of
 * Windows: `$ES_HOME/jdk/conf/security/java.security`
 * macOS:`$ES_HOME/jdk.app/Contents/Home/conf/security/java.security`
 
-For **JDK8**, the configuration file is within the `jre/lib/security` directory of the Java installation. If `$JAVA_HOME` points to the home directory of the JDK that you use to run {{es}}, then the configuration file will be in:
-
-* `$JAVA_HOME/jre/lib/security/java.security`
-
 For **JDK11 or later**, the configuration file is within the `conf/security` directory of the Java installation. If `$JAVA_HOME` points to the home directory of the JDK that you use to run {{es}}, then the configuration file will be in:
 
 * `$JAVA_HOME/conf/security/java.security`
@@ -72,11 +64,12 @@ For **JDK11 or later**, the configuration file is within the `conf/security` dir
 
 Within the JDK configuration file is a line that starts with `jdk.tls.disabledAlgorithms=`. This setting controls which protocols and algorithms are *disabled* in your JDK. The value of that setting will typically span multiple lines.
 
-For example, in OpenJDK 16 the setting is:
+For example, in OpenJDK 21 the setting is:
 
 ```text
-jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, RC4, DES, MD5withRSA, \
-    DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL
+jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, DTLSv1.0, RC4, DES, \
+    MD5withRSA, DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL, \
+    ECDH
 ```
 
 Create a new file in your in your {{es}} configuration directory named `es.java.security`. Copy the `jdk.tls.disabledAlgorithms` setting from the JDK’s default configuration file into `es.java.security`. You do not need to copy any other settings.
@@ -86,11 +79,12 @@ Create a new file in your in your {{es}} configuration directory named `es.java.
 
 Edit the `es.java.security` file in your {{es}} configuration directory, and modify the `jdk.tls.disabledAlgorithms` setting so that any SSL or TLS versions that you wish to use are no longer listed.
 
-For example, to enable TLSv1.1 on OpenJDK 16 (which uses the `jdk.tls.disabledAlgorithms` settings shown previously), the `es.java.security` file would contain the previously disabled TLS algorithms *except* `TLSv1.1`:
+For example, to enable TLSv1.1 on OpenJDK 21 (which uses the `jdk.tls.disabledAlgorithms` settings shown previously), the `es.java.security` file would contain the previously disabled TLS algorithms *except* `TLSv1.1`:
 
 ```text
-jdk.tls.disabledAlgorithms=SSLv3, TLSv1, RC4, DES, MD5withRSA, \
-    DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL
+jdk.tls.disabledAlgorithms=SSLv3, TLSv1, DTLSv1.0, RC4, DES, \
+    MD5withRSA, DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL, \
+    ECDH
 ```
 
 
diff --git a/deploy-manage/tools/snapshot-and-restore/read-only-url-repository.md b/deploy-manage/tools/snapshot-and-restore/read-only-url-repository.md
@@ -42,7 +42,7 @@ PUT _snapshot/my_read_only_url_repository
 :   (Optional, Boolean) If `true`, metadata files, such as index mappings and settings, are compressed in snapshots. Data files are not compressed. Defaults to `true`.
 
 `max_number_of_snapshots`
-:   (Optional, integer) Maximum number of snapshots the repository can contain. Defaults to `Integer.MAX_VALUE`, which is `2^31-1` or `2147483647`.
+:   (Optional, integer) Maximum number of snapshots the repository can contain. Defaults to `Integer.MAX_VALUE`, which is `2`^`31`^`-1` or `2147483647`.
 
 `max_restore_bytes_per_sec`
 :   (Optional, [byte value](elasticsearch://reference/elasticsearch/rest-apis/api-conventions.md#byte-units)) Maximum snapshot restore rate per node. Defaults to unlimited. Note that restores are also throttled through [recovery settings](elasticsearch://reference/elasticsearch/configuration-reference/index-recovery-settings.md).
diff --git a/deploy-manage/tools/snapshot-and-restore/shared-file-system-repository.md b/deploy-manage/tools/snapshot-and-restore/shared-file-system-repository.md
@@ -148,7 +148,7 @@ PUT _snapshot/my_fs_backup
 :   (Required, string) Location of the shared filesystem used to store and retrieve snapshots. This location must be registered in the `path.repo` setting on all master and data nodes in the cluster. Unlike `path.repo`, this setting supports only a single file path.
 
 `max_number_of_snapshots`
-:   (Optional, integer) Maximum number of snapshots the repository can contain. Defaults to `Integer.MAX_VALUE`, which is `2^31-1` or `2147483647`.
+:   (Optional, integer) Maximum number of snapshots the repository can contain. Defaults to `Integer.MAX_VALUE`, which is `2`^`31`^`-1` or `2147483647`.
 
 `max_restore_bytes_per_sec`
 :   (Optional, [byte value](elasticsearch://reference/elasticsearch/rest-apis/api-conventions.md#byte-units)) Maximum snapshot restore rate per node. Defaults to unlimited. Note that restores are also throttled through [recovery settings](elasticsearch://reference/elasticsearch/configuration-reference/index-recovery-settings.md).
diff --git a/deploy-manage/tools/snapshot-and-restore/source-only-repository.md b/deploy-manage/tools/snapshot-and-restore/source-only-repository.md
@@ -53,7 +53,7 @@ PUT _snapshot/my_src_only_repository
 
 
 `max_number_of_snapshots`
-:   (Optional, integer) Maximum number of snapshots the repository can contain. Defaults to `Integer.MAX_VALUE`, which is `2^31-1` or `2147483647`.
+:   (Optional, integer) Maximum number of snapshots the repository can contain. Defaults to `Integer.MAX_VALUE`, which is `2`^`31`^`-1` or `2147483647`.
 
 `max_restore_bytes_per_sec`
 :   (Optional, [byte value](elasticsearch://reference/elasticsearch/rest-apis/api-conventions.md#byte-units)) Maximum snapshot restore rate per node. Defaults to unlimited. Note that restores are also throttled through [recovery settings](elasticsearch://reference/elasticsearch/configuration-reference/index-recovery-settings.md).
diff --git a/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md b/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md
@@ -20,7 +20,7 @@ Periodically, you might need to upgrade an {{ece}} installation as new versions
 Before initiating the ECE upgrade process, review the [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise) to ensure the operating system (OS), Docker, or Podman versions you're running are compatible with the ECE version you’re upgrading to. We recommend that Docker, Podman, and the operating system are at the target version before starting the ECE upgrade.
 
 :::{note}
-During the upgrade window, there might be a short time period when you run a combination of versions that is not explicitly supported. For example, if you are on ECE 3.5 with Docker version 20.10 on Ubuntu 20.04 and plan to upgrade to ECE 3.7 on the same OS, you will need to upgrade Docker to version 24.0 first. In this case, and only during your upgrade window, we will support the mixed OS and container engine versions. In general, this won’t be a problem. However, should anything become a blocker for the upgrade, [reach out to support for help](/troubleshoot/index.md#contact-us).
+During the upgrade window, there might be a short period of time during which you run a combination of versions that is not explicitly supported. For example, if you are on ECE 3.5 with Docker version 18.09 on SLES 12 and plan to upgrade to ECE 3.8 on the same OS, you will need to upgrade Docker to version 24.0 or 25.0 first. In this case, and only during your upgrade window, we will support the mixed OS and container engine versions. In general, this won’t be a problem. However, should anything become a blocker for the upgrade, [reach out to support for help](/troubleshoot/index.md#contact-us).
 :::
 
 ## The upgrade version matrix [ece-upgrade-version-matrix]
diff --git a/explore-analyze/query-filter/aggregations.md b/explore-analyze/query-filter/aggregations.md
@@ -294,4 +294,4 @@ For faster responses, {{es}} caches the results of frequently run aggregations i
 
 ## Limits for `long` values [limits-for-long-values]
 
-When running aggregations, {{es}} uses [`double`](elasticsearch://reference/elasticsearch/mapping-reference/number.md) values to hold and represent numeric data. As a result, aggregations on [`long`](elasticsearch://reference/elasticsearch/mapping-reference/number.md) numbers greater than `253` are approximate.
+When running aggregations, {{es}} uses [`double`](elasticsearch://reference/elasticsearch/mapping-reference/number.md) values to hold and represent numeric data. As a result, aggregations on [`long`](elasticsearch://reference/elasticsearch/mapping-reference/number.md) numbers greater than `2`^`53`^ are approximate.
diff --git a/explore-analyze/query-filter/languages/esql-cross-clusters.md b/explore-analyze/query-filter/languages/esql-cross-clusters.md
@@ -1,15 +1,15 @@
 ---
 applies_to:
   stack: ga
-  serverless: ga
-navigation_title: "Using {{esql}} across clusters"
+  serverless: unavailable
+navigation_title: "Query across clusters"
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/esql-cross-clusters.html
 ---
 
 
 
-# Using ES|QL across clusters [esql-cross-clusters]
+# Use ES|QL across clusters [esql-cross-clusters]
 
 
 ::::{warning}
diff --git a/explore-analyze/query-filter/languages/esql-elastic-security.md b/explore-analyze/query-filter/languages/esql-elastic-security.md
@@ -2,15 +2,12 @@
 applies_to:
   stack: ga
   serverless: ga
-navigation_title: "Using {{esql}} in {{elastic-sec}}"
+navigation_title: "{{elastic-sec}}"
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/esql-elastic-security.html
 ---
 
-
-
-# Using ES|QL in Elastic Security [esql-elastic-security]
-
+# Use ES|QL in {{elastic-sec}} [esql-elastic-security]
 
 You can use {{esql}} in {{elastic-sec}} to investigate events in Timeline and create detection rules. Use the Elastic AI Assistant to build {{esql}} queries, or answer questions about the {{esql}} query language.
 
diff --git a/explore-analyze/query-filter/languages/esql-examples.md b/explore-analyze/query-filter/languages/esql-examples.md
@@ -7,8 +7,6 @@ navigation_title: "Examples"
 
 # {{esql}} examples [esql-examples]
 
-
-
 ## Aggregating and enriching windows event logs [_aggregating_and_enriching_windows_event_logs] 
 
 ```esql
diff --git a/explore-analyze/query-filter/languages/esql-getting-started.md b/explore-analyze/query-filter/languages/esql-getting-started.md
@@ -2,11 +2,10 @@
 applies_to:
   stack: ga
   serverless: ga
-navigation_title: "Getting started"
+navigation_title: "Get started"
 ---
 
-# Getting started with {{esql}} queries [esql-getting-started]
-
+# Get started with {{esql}} queries [esql-getting-started]
 
 This guide shows how you can use {{esql}} to query and aggregate your data.
 
diff --git a/explore-analyze/query-filter/languages/esql-kibana.md b/explore-analyze/query-filter/languages/esql-kibana.md
@@ -2,12 +2,12 @@
 applies_to:
   stack: ga
   serverless: ga
-navigation_title: "Using {{esql}} in {{kib}}"
+navigation_title: "{{kib}}"
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/esql-kibana.html
 ---
 
-# Using ES|QL in Kibana [esql-kibana]
+# Use ES|QL in Kibana [esql-kibana]
 
 You can use {{esql}} in {{kib}} to query and aggregate your data, create visualizations, and set up alerts.
 
diff --git a/explore-analyze/query-filter/languages/esql-multi-index.md b/explore-analyze/query-filter/languages/esql-multi-index.md
@@ -2,15 +2,12 @@
 applies_to:
   stack: ga
   serverless: ga
-navigation_title: "Using {{esql}} to query multiple indices"
+navigation_title: "Query multiple indices"
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/esql-multi-index.html
 ---
 
-
-
-# Using ES|QL to query multiple indices [esql-multi-index]
-
+# Use ES|QL to query multiple indices [esql-multi-index]
 
 With {{esql}}, you can execute a single query across multiple indices, data streams, or aliases. To do so, use wildcards and date arithmetic. The following example uses a comma-separated list and a wildcard:
 
diff --git a/explore-analyze/query-filter/languages/esql-multi.md b/explore-analyze/query-filter/languages/esql-multi.md
@@ -0,0 +1,13 @@
+---
+applies_to:
+  stack: ga
+  serverless: ga
+navigation_title: "Query multiple sources"
+---
+
+# Query multiple indices or clusters with {{esql}}
+
+{{esql}} allows you to query across multiple indices or clusters. Learn more in the following sections:
+
+* [Query multiple indices](esql-multi-index.md)
+* [Query across clusters](esql-cross-clusters.md)
diff --git a/explore-analyze/query-filter/languages/esql-rest.md b/explore-analyze/query-filter/languages/esql-rest.md
@@ -2,16 +2,16 @@
 applies_to:
   stack: ga
   serverless: ga
-navigation_title: "{{esql}} query API"
+navigation_title: "{{esql}} `_query` API"
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/esql-rest.html
 ---
 
+# Use the {{esql}} `_query` API [esql-rest]
 
-
-# {{esql}} query API [esql-rest]
-
-
+::::{tip}
+The [Search and filter with {{esql}}](/solutions/search/esql-search-tutorial.md) tutorial provides a hands-on introduction to the {{esql}} query API.
+::::
 
 ## Overview [esql-rest-overview]
 
diff --git a/explore-analyze/query-filter/languages/esql-where.md b/explore-analyze/query-filter/languages/esql-where.md
@@ -0,0 +1,14 @@
+---
+applies_to:
+  stack: ga
+  serverless: ga
+navigation_title: "Interfaces"
+---
+
+# Where can I use {{esql}}?
+
+You can use {{esql}} in the following contexts:
+
+* [REST API](esql-rest.md)
+* [Kibana](esql-kibana.md)
+* [Elastic Security](esql-elastic-security.md)
diff --git a/explore-analyze/query-filter/languages/esql.md b/explore-analyze/query-filter/languages/esql.md
diff --git a/explore-analyze/toc.yml b/explore-analyze/toc.yml
diff --git a/manage-data/ingest/transform-enrich.md b/manage-data/ingest/transform-enrich.md
diff --git a/manage-data/migrate/migrate-from-a-self-managed-cluster-with-a-self-signed-certificate-using-remote-reindex.md b/manage-data/migrate/migrate-from-a-self-managed-cluster-with-a-self-signed-certificate-using-remote-reindex.md
diff --git a/reference/fleet/secure-connections.md b/reference/fleet/secure-connections.md
diff --git a/release-notes/elastic-cloud-serverless/index.md b/release-notes/elastic-cloud-serverless/index.md
diff --git a/troubleshoot/deployments/cloud-enterprise/verify-zookeeper-sync-status.md b/troubleshoot/deployments/cloud-enterprise/verify-zookeeper-sync-status.md

Original file line number	Diff line number	Diff line change
`@@ -294,4 +294,4 @@ For faster responses, {{es}} caches the results of frequently run aggregations i`
`294`	`294`
`295`	`295`	## Limits for `long` values [limits-for-long-values]
`296`	`296`
`297`		-When running aggregations, {{es}} uses [`double`](elasticsearch://reference/elasticsearch/mapping-reference/number.md) values to hold and represent numeric data. As a result, aggregations on [`long`](elasticsearch://reference/elasticsearch/mapping-reference/number.md) numbers greater than `253` are approximate.
	`297`	+When running aggregations, {{es}} uses [`double`](elasticsearch://reference/elasticsearch/mapping-reference/number.md) values to hold and represent numeric data. As a result, aggregations on [`long`](elasticsearch://reference/elasticsearch/mapping-reference/number.md) numbers greater than `2`^`53`^ are approximate.