Merge branch 'main' into llm-note-partition

Author: mdbirnstiehl

deploy-manage/_snippets/field-doc-sec-limitations.md

@@ -40,5 +40,5 @@ When a user’s role enables document or [field level security](/deploy-manage/u
 
 * The request cache is disabled for search requests if either of the following are true:
 
-    * The role query that defines document level security is [templated](/deploy-manage/users-roles/cluster-or-deployment-auth/controlling-access-at-document-field-level.md#templating-role-query) using a [stored script](/explore-analyze/scripting/modules-scripting-using.md#script-stored-scripts).
+    * The role query that defines document level security is [templated](/deploy-manage/users-roles/cluster-or-deployment-auth/controlling-access-at-document-field-level.md#templating-role-query) using a [stored script](/explore-analyze/scripting/modules-scripting-store-and-retrieve.md).
     * The target indices are a mix of local and remote indices.

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

@@ -70,7 +70,8 @@ If you don’t have an existing {{ecloud}} account:
 :sync: existing
 
 If you already have an {{ecloud}} account:
-1. Log in to [{{ecloud}}](https://cloud.elastic.co?page=docs&placement=docs-body).
+1. Log in to [{{ecloud}}](https://cloud.elastic.co/login?redirectTo=%2Fconnect-cluster-services).
+    - The link provided should take you directly to the **Connect your self-managed cluster** page
 2. On your home page, in the **Connected clusters** section, select **Connect self-managed cluster**. 
 3. On the **Connect your self-managed cluster** page, in the **AutoOps** section, select **Connect**.
 4. Go through the installation wizard as detailed in the following sections.

deploy-manage/tools/snapshot-and-restore.md

@@ -91,7 +91,7 @@ By default, a snapshot of a cluster contains the cluster state, all regular data
 - [Legacy index templates](https://www.elastic.co/guide/en/elasticsearch/reference/8.18/indices-templates-v1.html)
 - [Ingest pipelines](/manage-data/ingest/transform-enrich/ingest-pipelines.md)
 - [ILM policies](/manage-data/lifecycle/index-lifecycle-management.md)
-- [Stored scripts](/explore-analyze/scripting/modules-scripting-using.md#script-stored-scripts)
+- [Stored scripts](/explore-analyze/scripting/modules-scripting-store-and-retrieve.md)
 - For snapshots taken after 7.12.0, [feature states](#feature-state)
 
 You can also take snapshots of only specific data streams or indices in the cluster. A snapshot that includes a data stream or index automatically includes its aliases. When you restore a snapshot, you can choose whether to restore these aliases.

explore-analyze/alerts-cases/watcher/how-watcher-works.md

@@ -184,7 +184,7 @@ Deactivating a watch also enables you to keep it around for future use without d
 
 You can use scripts and templates when defining a watch. Scripts and templates can reference elements in the watch execution context, including the watch payload. The execution context defines variables you can use in a script and parameter placeholders in a template.
 
-{{watcher}} uses the Elasticsearch script infrastructure, which supports [inline](#inline-templates-scripts) and [stored](#stored-templates-scripts). Scripts and templates are compiled and cached by Elasticsearch to optimize recurring execution. Autoloading is also supported. For more information, see [Scripting](../../scripting.md) and [*How to write scripts*](../../scripting/modules-scripting-using.md).
+{{watcher}} uses the Elasticsearch script infrastructure, which supports [inline](#inline-templates-scripts) and [stored](#stored-templates-scripts). Scripts and templates are compiled and cached by Elasticsearch to optimize recurring execution. Autoloading is also supported. For more information, see [Scripting](../../scripting.md) and [*How to write Painless scripts*](../../scripting/modules-scripting-using.md).
 
 
 ### Watch execution context [watch-execution-context]

explore-analyze/elastic-inference/ml-node-vs-eis.md

@@ -0,0 +1,55 @@
+---
+navigation_title: ML-nodes vs EIS
+applies_to:
+  stack: ga
+  serverless: ga
+  deployment:
+    self: unavailable
+---
+
+# Using ML-nodes or Elastic {{infer-cap}} Service (EIS) [ml-nodes-vs-eis]
+
+## When to use EIS?
+
+The Elastic Inference Service (EIS) requires zero setup or management. It's always-on, has excellent ingest throughput, and uses simple token-based billing.
+
+Use EIS if you're getting started with [semantic search](/solutions/search/semantic-search.md) or [hybrid search](/solutions/search/hybrid-search.md) and want a smooth experience. Under the hood, EIS uses GPUs for ML {{infer}}, which are more efficient and allow a faster, more cost-effective experience for most usecases.
+
+## When to use {{ml}} nodes?
+
+ML nodes are a more configurable solution than EIS where you can set up specific nodes using CPUs to execute [ML {{infer}}](/explore-analyze/elastic-inference/inference-api.md). {{ml-cap}} nodes tend to give more fine-grained control.
+
+Use ML nodes if you want to decide how your models run, you want to run custom models, or you have a self-managed setup.
+
+## How do I switch from using ML nodes to EIS on an existing index?
+
+```{applies_to}
+stack: ga 9.3
+serverless: ga
+```
+
+```console
+PUT /my-ml-node-index/_mapping
+{
+  "properties": {
+    "text": {
+      "type": "semantic_text",
+      "inference_id": ".elser-2-elastic"
+    }
+  }
+}
+```
+
+You can also switch an EIS-based index to use ML nodes:
+
+```console
+PUT /my-eis-index/_mapping
+{
+  "properties": {
+    "text": {
+      "type": "semantic_text",
+      "inference_id": ".elser-2-elasticsearch"
+    }
+  }
+}
+```

explore-analyze/scripting/common-script-uses.md

@@ -8,10 +8,19 @@ products:
   - id: elasticsearch
 ---
 
-# Common scripting use cases [common-script-uses]
+# Painless script tutorials [common-script-uses]
 
-You can write a script to do almost anything, and sometimes, that’s the trouble. It’s challenging to know what’s possible with scripts, so the following examples address common uses cases where scripts are really helpful.
-
-* [Field extraction](scripting-field-extraction.md)
+You can write a script to do almost anything, and sometimes, that’s the challenge. It’s difficult to know what’s possible with scripts, so these tutorials address common use cases where scripts are particularly helpful.
 
+Painless scripting becomes powerful when applied to real-world scenarios. These tutorials walk you through essential patterns and operations, providing working examples you can modify for your specific use cases.
 
+* [Accessing document fields and special variables](/explore-analyze/scripting/modules-scripting-fields.md)
+* [Accessing fields in a document](/explore-analyze/scripting/script-fields-api.md)
+* [Converting data types](/explore-analyze/scripting/modules-scripting-type-casting-tutorial.md)
+* [Dissecting data](/explore-analyze/scripting/dissect.md)
+* [Extracting fields](/explore-analyze/scripting/scripting-field-extraction.md)
+* [Grokking grok](/explore-analyze/scripting/grok.md)
+* [Scripts, caching, and search speed](/explore-analyze/scripting/scripts-search-speed.md)
+* [Updating documents](/explore-analyze/scripting/modules-scripting-document-update-tutorial.md)
+* [Using Painless regular expressions](/explore-analyze/scripting/modules-scripting-regular-expressions-tutorial.md)
+* [Working with dates](/explore-analyze/scripting/modules-scripting-datetime-tutorial.md)