Merge branch 'main' into update-ccs-support-for-9.2-release

Author: ketkee-aryamane

deploy-manage/monitor/autoops/ec-autoops-regions.md

@@ -29,27 +29,27 @@ AutoOps for {{ECH}} is currently available in the following regions for AWS:
 
 | Region | Name |
 | --- | --- | --- | --- |
-| us-east-1 | N. Virginia |
-| us-east-2 | Ohio |
-| us-west-1 | N. California |
-| us-west-2 | Oregon |
-| ca-central-1 | Canada |
-| eu-west-1 | Ireland |
-| eu-west-2 | London |
-| eu-west-3 | Paris |
-| eu-north-1 | Stockholm |
-| eu-central-1 | Frankfurt |
-| eu-central-2 | Zurich |
-| eu-south-1 | Milan |
-| me-south-1 | Bahrain |
-| ap-east-1 | Hong Kong |
-| ap-northeast-1 | Tokyo |
-| ap-northeast-2 | Seoul |
-| ap-southeast-1 | Singapore |
-| ap-southeast-2 | Sydney |
-| ap-south-1 | Mumbai |
-| sa-east-1 | Sao Paulo |
-| af-south-1 | Cape Town |
+| us-east-1 | US East (N. Virginia) |
+| us-east-2 | US East (Ohio) |
+| us-west-1 | US West (N. California) |
+| us-west-2 | US West (Oregon) |
+| ca-central-1 | Canada (Central) |
+| eu-west-1 | Europe (Ireland) |
+| eu-west-2 | Europe (London) |
+| eu-west-3 | Europe (Paris) |
+| eu-north-1 | Europe (Stockholm) |
+| eu-central-1 | Europe (Frankfurt) |
+| eu-central-2 | Europe (Zurich) |
+| eu-south-1 | Europe (Milan) |
+| me-south-1 | Middle East (Bahrain) |
+| ap-east-1 | Asia Pacific (Hong Kong) |
+| ap-northeast-1 | Asia Pacific (Tokyo) |
+| ap-northeast-2 | Asia Pacific (Seoul) |
+| ap-southeast-1 | Asia Pacific (Singapore) |
+| ap-southeast-2 | Asia Pacific (Sydney) |
+| ap-south-1 | Asia Pacific (Mumbai) |
+| sa-east-1 | South America (Sao Paulo) |
+| af-south-1 | Africa (Cape Town) |
 
 Regions for Azure and GCP are coming soon.
 
@@ -68,9 +68,9 @@ AutoOps for serverless projects is currently available in the following regions
 
 | Region | Name |
 | --- | --- | --- | --- |
-| us-east-1 | N. Virginia |
-| eu-west-1 | Ireland |
-| ap-southeast-1 | Singapore |
-| us-west-2 | Oregon |
+| us-east-1 | US East (N. Virginia) |
+| eu-west-1 | Europe (Ireland) |
+| ap-southeast-1 | Asia Pacific (Singapore) |
+| us-west-2 | US West (Oregon) |
 
 The only exception is the **Search AI Lake** view, which is available in all CSP regions across AWS, Azure and GCP.

deploy-manage/tools/snapshot-and-restore/_snippets/restore-snapshot-common-prerequisites.md

@@ -0,0 +1,6 @@
+* To use {{kib}}'s **Snapshot and Restore** feature, you must have the following permissions:
+
+    * [Cluster privileges](elasticsearch://reference/elasticsearch/security-privileges.md#privileges-list-cluster): `monitor`, `manage_slm`, `cluster:admin/snapshot`, and `cluster:admin/repository`
+    * [Index privilege](elasticsearch://reference/elasticsearch/security-privileges.md#privileges-list-indices): `monitor` privilege on all the indices
+
+* To register a snapshot repository or restore a snapshot, the cluster’s global metadata must be writeable. Ensure there aren’t any [cluster blocks](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-read-only) that prevent write access. The restore operation ignores index blocks.

deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.md

@@ -26,12 +26,8 @@ From within {{ech}}, you can restore a snapshot from a different deployment in t
 
 ## Prerequisites for {{ech}}
 
-To use Kibana's Snapshot and Restore feature, you must have the following permissions:
-
-- Cluster privileges: `monitor`, `manage_slm`, `cluster:admin/snapshot`, and `cluster:admin/repository`
-- Index privilege: `all` on the monitor index
-
-To register a snapshot repository, the cluster’s global metadata must be writable. Ensure there aren’t any cluster blocks that prevent write access.
+:::{include} _snippets/restore-snapshot-common-prerequisites.md
+:::
 
 ## Considerations
 

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

@@ -27,12 +27,11 @@ In this guide, you’ll learn how to:
 This guide also provides tips for [restoring to another cluster](#restore-different-cluster) and [troubleshooting common restore errors](#troubleshoot-restore).
 
 ## Prerequisites
-- To use Kibana’s Snapshot and Restore feature, you must have the following permissions:
-  - [Cluster privileges](elasticsearch://reference/elasticsearch/security-privileges.md#privileges-list-cluster): `monitor`, `manage_slm`, `cluster:admin/snapshot`, and `cluster:admin/repository`
-  - [Index privilege](elasticsearch://reference/elasticsearch/security-privileges.md#privileges-list-indices): `all` on the monitor index
+:::{include} _snippets/restore-snapshot-common-prerequisites.md
+:::
+
 - You can only restore a snapshot to a running cluster with an elected [master node](/deploy-manage/distributed-architecture/clusters-nodes-shards/node-roles.md#master-node-role). The snapshot’s repository must be registered and available to the cluster.
 - The snapshot and cluster versions must be compatible. See [Snapshot compatibility](/deploy-manage/tools/snapshot-and-restore.md#snapshot-compatibility).
-- To restore a snapshot, the cluster’s global metadata must be writable. Ensure there aren’t any cluster blocks that prevent writes. The restore operation ignores index blocks.
 - Before you restore a data stream, ensure the cluster contains a [matching index template](/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md#create-ts-index-template) with data stream enabled. To check, use [Kibana’s Index Management](/manage-data/data-store/index-basics.md#index-management-manage-index-templates) feature or the get index template API:
 
   ```console

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

@@ -21,12 +21,8 @@ In this guide, you’ll learn how to:
 
 ## Prerequisites [snapshot-repo-prereqs]
 
-* To use {{kib}}'s **Snapshot and Restore** feature, you must have the following permissions:
-
-    * [Cluster privileges](elasticsearch://reference/elasticsearch/security-privileges.md#privileges-list-cluster): `monitor`, `manage_slm`, `cluster:admin/snapshot`, and `cluster:admin/repository`
-    * [Index privilege](elasticsearch://reference/elasticsearch/security-privileges.md#privileges-list-indices): `all` on the `monitor` index
-
-* To register a snapshot repository, the cluster’s global metadata must be writeable. Ensure there aren’t any [cluster blocks](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-read-only) that prevent write access.
+:::{include} _snippets/restore-snapshot-common-prerequisites.md
+:::
 
 ## Considerations [snapshot-repo-considerations]
 

explore-analyze/elastic-inference/eis.md

@@ -9,64 +9,48 @@ applies_to:
 
 # Elastic {{infer-cap}} Service [elastic-inference-service-eis]
 
-The Elastic {{infer-cap}} Service (EIS) enables you to leverage AI-powered search as a service without deploying a model in your cluster.
+The Elastic {{infer-cap}} Service (EIS) enables you to leverage AI-powered search as a service without deploying a model in your environment.
 With EIS, you don't need to manage the infrastructure and resources required for {{ml}} {{infer}} by adding, configuring, and scaling {{ml}} nodes.
 Instead, you can use {{ml}} models for ingest, search, and chat independently of your {{es}} infrastructure.
 
 ## AI features powered by EIS [ai-features-powered-by-eis]
 
 * Your Elastic deployment or project comes with a default [`Elastic Managed LLM` connector](https://www.elastic.co/docs/reference/kibana/connectors-kibana/elastic-managed-llm). This connector is used in the AI Assistant, Attack Discovery, Automatic Import and Search Playground.
 
-* You can use [ELSER](/explore-analyze/machine-learning/nlp/ml-nlp-elser.md) to perform semantic search as a service (ELSER on EIS). {applies_to}`stack: preview 9.1` {applies_to}`serverless: preview`
+* You can use [ELSER](/explore-analyze/machine-learning/nlp/ml-nlp-elser.md) to perform semantic search as a service (ELSER on EIS). {applies_to}`stack: preview 9.1, ga 9.2` {applies_to}`serverless: ga`
 
 ## Region and hosting [eis-regions]
 
 Requests through the `Elastic Managed LLM` are currently proxying to AWS Bedrock in AWS US regions, beginning with `us-east-1`.
 The request routing does not restrict the location of your deployments.
 
-ELSER requests are managed by Elastic's own EIS infrastructure and are also hosted in AWS US regions, beginning with `us-east-1`. All Elastic Cloud hosted deployments and serverless projects in any CSP and region can access the endpoint. As we expand the service to Azure and GCP and more regions, we will automatically route requests to the same CSP and closest region the Elaticsearch cluster is hosted on. 
 
+ELSER requests are managed by Elastic's own EIS infrastructure and are also hosted in AWS US regions, beginning with `us-east-1`. All Elastic Cloud hosted deployments and serverless projects in any CSP and region can access the endpoint. As we expand the service to Azure and GCP and more regions, we will automatically route requests to the same CSP and closest region the Elaticsearch cluster is hosted on. 
 
 ## ELSER via Elastic {{infer-cap}} Service (ELSER on EIS) [elser-on-eis]
 
 ```{applies_to}
-stack: preview 9.1
-serverless: preview
+stack: preview 9.1, ga 9.2
+serverless: ga
 ```
 
-ELSER on EIS enables you to use the ELSER model on GPUs, without having to manage your own ML nodes. We expect significantly better performance for throughput and consistent search latency as compared to ML nodes, and will continue to benchmark, remove limitations and address concerns as we move towards General Availability.
+ELSER on EIS enables you to use the ELSER model on GPUs, without having to manage your own ML nodes. We expect better performance for ingest throughput than ML nodes and equivalent performance for search latency. We will continue to benchmark, remove limitations and address concerns.
 
 ### Using the ELSER on EIS endpoint
 
 You can now use `semantic_text` with the new ELSER endpoint on EIS. To learn how to use the `.elser-2-elastic` inference endpoint, refer to [Using ELSER on EIS](elasticsearch://reference/elasticsearch/mapping-reference/semantic-text.md#using-elser-on-eis).
 
 #### Get started with semantic search with ELSER on EIS
-[Semantic Search with `semantic_text`](/solutions/search/semantic-search/semantic-search-semantic-text.md) has a detailed tutorial on using the `semantic_text` field and using the ELSER endpoint on EIS instead of the default endpoint. This is a great way to get started and try the new endpoint.
-
-### Limitations
-
-While we do encourage experimentation, we do not recommend implementing production use cases on top of this feature while it is in Technical Preview.
 
-#### Uptime
-
-There are no uptime guarantees during the Technical Preview.
-While Elastic will address issues promptly, the feature may be unavailable for extended periods.
-
-#### Throughput and latency
+[Semantic Search with `semantic_text`](/solutions/search/semantic-search/semantic-search-semantic-text.md) has a detailed tutorial on using the `semantic_text` field and using the ELSER endpoint on EIS instead of the default endpoint. This is a great way to get started and try the new endpoint.
 
-{{infer-cap}} throughput via this endpoint is expected to exceed that of {{infer}} operations on an ML node.
-However, throughput and latency are not guaranteed.
-Performance may vary during the Technical Preview.
+### Limitations 
 
 #### Batch size
 
 Batches are limited to a maximum of 16 documents.
 This is particularly relevant when using the [_bulk API](https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-bulk) for data ingestion.
 
-#### Rate limits 
-
-Rate limit for search and ingest is currently at 500 requests per minute. This allows you to ingest approximately 8000 documents per minute at 16 documents per request.
-
 ## Pricing 
 
 All models on EIS incur a charge per million tokens. The pricing details are at our [Pricing page](https://www.elastic.co/pricing/serverless-search) for the Elastic Managed LLM and ELSER. 

explore-analyze/elastic-inference/inference-api.md

@@ -88,7 +88,7 @@ The behavior of allocations depends on several factors:
 If you enable adaptive allocations and set the `min_number_of_allocations` to a value greater than `0`, you will be charged for the machine learning resources, even if no inference requests are sent.
 
 However, setting the `min_number_of_allocations` to a value greater than `0` keeps the model always available without scaling delays. Choose the configuration that best fits your workload and availability needs.
-:::: 
+::::
 
 For more information about adaptive allocations and resources, refer to the [trained model autoscaling](/deploy-manage/autoscaling/trained-model-autoscaling.md) documentation.
 
@@ -105,9 +105,9 @@ By default, documents are split into sentences and grouped in sections up to 250
 
 ### Chunking strategies
 
-Several strategies are available for chunking: 
+Several strategies are available for chunking:
 
-#### `sentence` 
+#### `sentence`
 
 The `sentence` strategy splits the input text at sentence boundaries. Each chunk contains one or more complete sentences ensuring that the integrity of sentence-level context is preserved, except when a sentence causes a chunk to exceed a word count of `max_chunk_size`, in which case it will be split across chunks. The `sentence_overlap` option defines the number of sentences from the previous chunk to include in the current chunk which is either `0` or `1`.
 
@@ -134,7 +134,7 @@ The default chunking strategy is `sentence`.
 
 #### `word`
 
-The `word` strategy splits the input text on individual words up to the `max_chunk_size` limit. The `overlap` option is the number of words from the previous chunk to include in the current chunk. 
+The `word` strategy splits the input text on individual words up to the `max_chunk_size` limit. The `overlap` option is the number of words from the previous chunk to include in the current chunk.
 
 The following example creates an {{infer}} endpoint with the `elasticsearch` service that deploys the ELSER model and configures the chunking behavior with the `word` strategy, setting a maximum of 120 words per chunk and an overlap of 40 words between chunks.
 
@@ -158,7 +158,7 @@ PUT _inference/sparse_embedding/word_chunks
 #### `recursive`
 
 ```{applies_to}
-stack: ga 9.1`
+stack: ga 9.1
 ```
 
 The `recursive` strategy splits the input text based on a configurable list of separator patterns (for example, newlines or Markdown headers). The chunker applies these separators in order, recursively splitting any chunk that exceeds the `max_chunk_size` word limit. If no separator produces a small enough chunk, the strategy falls back to sentence-level splitting.
@@ -215,7 +215,7 @@ PUT _inference/sparse_embedding/recursive_custom_chunks
 #### `none`
 
 ```{applies_to}
-stack: ga 9.1`
+stack: ga 9.1
 ```
 
 The `none` strategy disables chunking and processes the entire input text as a single block, without any splitting or overlap. When using this strategy, you can instead [pre-chunk](https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/semantic-text#auto-text-chunking) the input by providing an array of strings, where each element acts as a separate chunk to be sent directly to the inference service without further chunking.

explore-analyze/images/ai-assistant-settings-page-serverless.png

@@ -0,0 +1,59 @@
+---
+applies_to:
+  stack: ga 9.2
+  serverless: ga
+products:
+  - id: kibana
+  - id: observability
+  - id: security
+  - id: cloud-serverless
+---
+
+# Manage access to AI Features
+
+This page describes how to use the GenAI Settings page to control access to AI-powered features in your deployments in the following ways:
+
+
+- Manage which AI connectors are available in your environment. 
+- Enable or disable AI Assistant and other AI-powered features in your environment.
+- {applies_to}`stack: ga 9.2` {applies_to}`serverless: unavailable` Specify in which Elastic solutions the `AI Assistant for Observability and Search` and the `AI Assistant for Security` appear.
+
+
+## Requirements
+
+- To access the **GenAI Settings** page, you need the `Actions and connectors: all` or `Actions and connectors: read` [{{kib}} privilege](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md).
+- To modify the settings on this page, you need the `Advanced Settings: all` {{kib}} privilege.
+
+## The GenAI Settings page
+
+To manage these settings, go to the **GenAI Settings** page by using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+
+::::{applies-switch}
+
+:::{applies-item} stack: ga 9.2
+
+![GenAI Settings page for Stack](/explore-analyze/images/ai-assistant-settings-page.png "")
+
+
+The **GenAI Settings** page has the following settings:
+
+- **Default AI Connector**: Use this setting to specify which connector is selected by default. This affects all AI-powered features, not just AI Assistant. 
+- **Disallow all other connectors**: Enable this setting to prevent connectors other than the default connector specified above from being used in your space. This affects all AI-powered features, not just AI Assistant. 
+- **AI feature visibility**: This button opens the current Space's settings page. Here you can specify which features should appear in your environment, including AI-powered features. 
+- **AI Assistant visibility**: This setting allows you to choose which AI Assistants are available to use and where. You can choose to only show the AI Assistants in their native solutions, in other {{kib}} pages (for example, Discover, Dashboards, and Stack Management), or select **Hide all assistants** to disable AI Assistant throughout {{kib}}.
+
+:::
+
+:::{applies-item} serverless:
+
+![GenAI Settings page for Serverless](/explore-analyze/images/ai-assistant-settings-page-serverless.png "")
+
+The **GenAI Settings** page has the following settings:
+
+- **Default AI Connector**: Click **Manage connectors** to open the **Connectors** page, where you can create or delete AI connectors. To update these settings, you need the `Actions and connectors: all` [{{kib}} privilege](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md).
+- **AI feature visibility**: Click **Go to Permissions tab** to access the active {{kib}} space's settings page, where you can specify which features each custom user role has access to in your environment. This includes AI-powered features such as AI Assistant. 
+
+:::
+
+::::
+