Merge branch 'main' into background-search

Author: florent-leborgne

deploy-manage/api-keys/elasticsearch-api-keys.md

@@ -15,7 +15,7 @@ Several types of {{es}} API keys exist:
 * **Cross-cluster** API key: allows other clusters to connect to this cluster.
 * **Managed** API key: created and managed by {{kib}} to run background tasks.
 
-To manage API keys in {{kib}}, go to **Management > Stack Management > API Keys** from the navigation menu or use the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md).
+To manage API keys in {{kib}}, 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).
 
 ![API Keys UI](/deploy-manage/images/kibana-api-keys.png "")
 
@@ -42,10 +42,13 @@ Two methods are available to create an API key:
 
   Your personal API key is created with a default expiration of 90 days from the time of creation. You can manage the key from the **API Keys** page.
 
-* To create a personal or cross-cluster API key with configurable options, go to **Management > Stack Management > API Keys** from the navigation menu or use the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md), and select **Create API key**.
+* To create a personal or cross-cluster API key with configurable options: 
+  1. 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).
+  2. Select **Create API key**.
 
-  ![Create API Key UI](/deploy-manage/images/kibana-create-user-api-key.png "")
+![Create API Key UI](/deploy-manage/images/kibana-create-user-api-key.png "")
 
+From the **Create API key** pane, you can configure your new key:
   1. Choose to create either a user or a cross-cluster API key.
   2. Optionally, set an expiry date. By default the API key will not expire, but it's a good security practice to give the key a limited lifespan.
   3. Configure access:
@@ -55,7 +58,9 @@ Two methods are available to create an API key:
 
 ## Update an API key [update-api-key]
 
-To update an API key, go to **Management > Stack Management > API Keys** from the navigation menu or use the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md), and then click on the name of the key. You cannot update the name or the type of an API key.
+To update an API key, 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). From the **API keys** page, click on the name of the key you want to update. 
+
+You can't update the name or the type of an API key.
 
 * For a user API key, you can update:
   * The API key's access to {{es}} APIs and resources.
@@ -71,7 +76,7 @@ To update an API key, go to **Management > Stack Management > API Keys** from th
 
 ## View and delete API keys [view-api-keys]
 
-The **API Keys** feature in {{kib}} lists your API keys, including the name, date created, and status. If an API key expires, its status changes from `Active` to `Expired`.
+The **API Keys** management page in {{kib}} lists your API keys, including the name, date created, and status. If an API key expires, its status changes from `Active` to `Expired`.
 
 If you have `manage_security` or `manage_api_key` permissions, you can view the API keys of all users, and see which API key was created by which user in which realm. If you have only the `manage_own_api_key` permission, you see only a list of your own keys.
 

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

@@ -26,9 +26,11 @@ The following AWS regions are currently available:
 
 | Region | Name |
 | :--- | :--- |
+| ap-northeast-1 | Asia Pacific (Tokyo) |
 | ap-southeast-1 | Asia Pacific (Singapore) |
 | eu-central-1 | Europe (Frankfurt) |
 | eu-west-1 | Europe (Ireland) |
+| eu-west-2 | Europe (London) |
 | us-east-1 | US East (N. Virginia) |
 | us-east-2 | US East (Ohio) |
 | us-west-2 | US West (Oregon) |

deploy-manage/kibana-reporting-configuration.md

@@ -121,7 +121,9 @@ When security is enabled, you grant users access to {{report-features}} with [{{
     4. Click **Update user**.
 
 
-Granting the privilege to generate reports also grants the user the privilege to view their reports in **Stack Management > Reporting**. Users can only access their own reports.
+Granting the privilege to generate reports also grants the user the privilege to view their reports in **Reporting**. Users can only access their own reports.
+
+To view reports, go to the **Reporting** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 
 
 ::::

deploy-manage/license/manage-your-license-in-self-managed-cluster.md

@@ -36,5 +36,5 @@ If your license expires, your subscription level reverts to Basic and you will n
 
 Licenses are provided as a *JSON* file and have an effective date and an expiration date. You cannot install a new license before its effective date. License updates take effect immediately and do not require restarting {{es}}.
 
-You can update your license from **Stack Management > License Management** or through the [update license API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-license-post).
+To update your license from {{kib}}, go to the **License Management** management page using the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). You can also use the [update license API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-license-post).
 

deploy-manage/manage-connectors.md

@@ -12,7 +12,9 @@ products:
 
 # Connectors [connector-management]
 
-Connectors serve as a central place to store connection information for both Elastic and third-party systems. They enable the linking of actions to rules, which execute as background tasks on the {{kib}} server when rule conditions are met. This allows rules to route actions to various destinations such as log files, ticketing systems, and messaging tools. Different {{kib}} apps may have their own rule types, but they typically share connectors. The **{{stack-manage-app}} > {{connectors-ui}}** provides a central location to view and manage all connectors in the current space.
+Connectors serve as a central place to store connection information for both Elastic and third-party systems. They enable the linking of actions to rules, which execute as background tasks on the {{kib}} server when rule conditions are met. This allows rules to route actions to various destinations such as log files, ticketing systems, and messaging tools. Different {{kib}} apps may have their own rule types, but they typically share connectors. The **{{connectors-ui}}** provides a central location to view and manage all connectors in the current space. 
+
+You can find the **{{connectors-ui}}** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 
 ::::{note}
 This page is about {{kib}} connectors that integrate with services like generative AI model providers. If you’re looking for content connectors that synchronize third-party data into {{es}}, refer to [Connector clients](elasticsearch://reference/search-connectors/index.md).
@@ -33,7 +35,7 @@ If you're using {{stack}}, use the [action configuration settings](kibana://refe
 
 ## Connector list [connectors-list]
 
-In **{{stack-manage-app}} > {{connectors-ui}}**, you can find a list of the connectors in the current space. You can use the search bar to find specific connectors by name and type. The **Type** dropdown also enables you to filter to a subset of connector types.
+In **{{connectors-ui}}**, you can find a list of the connectors in the current space. You can use the search bar to find specific connectors by name and type. The **Type** dropdown also enables you to filter to a subset of connector types.
 
 :::{image} /deploy-manage/images/kibana-connector-filter-by-type.png
 :alt: Filtering the connector list by types of connectors

deploy-manage/manage-spaces.md

@@ -25,7 +25,7 @@ products:
 :screenshot:
 :::
 
-To go to **Spaces**, find **Stack Management** in the navigation menu or use the [global search bar](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+You can find the **Spaces** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 
 For more info on working with spaces, check out: 
 - [Create a space](#spaces-managing)
@@ -127,7 +127,9 @@ serverless: unavailable
 
 You can create a custom experience for users by configuring the {{kib}} landing page on a per-space basis. The landing page can route users to a specific dashboard, application, or saved object as they enter each space.
 
-To configure the landing page, use the default route setting in [Stack Management > {{kib}} > Advanced settings](kibana://reference/advanced-settings.md#kibana-general-settings). For example, you might set the default route to `/app/dashboards`.
+To configure the landing page, use the default route setting in the [{{kib}} advanced settings](kibana://reference/advanced-settings.md#kibana-general-settings). For example, you might set the default route to `/app/dashboards`.
+
+You can access the **Advanced Settings** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 
 
 :::{image} /deploy-manage/images/kibana-spaces-configure-landing-page.png
 :alt: Configure space-level landing page

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

@@ -122,9 +122,10 @@ 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.
-2. Go to **Stack management** > **API keys** and select **Create API key**.
-3. In the flyout, enter a name for your key and select **User API key**.
-4. Enable **Control security privileges** and enter the following script:
+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**.
+5. Enable **Control security privileges** and enter the following script:
 ```json
 {
  "autoops": {

deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-elastic-agent.md

@@ -35,7 +35,9 @@ metrics-elasticsearch.stack_monitoring.shard
 
 To change the settings of each data stream, edit the `metrics-{{product}}.stack_monitoring.{{dataset}}@custom` component template that already exists. You can do this in {{kib}}:
 
-* Navigate to **Stack Management** > **Index Management** > **Component Templates**.
+
+* Go to the **Index Management** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+* Select **Component Templates**.
 * Search for the component template.
 * Select the **Edit** action.
 

deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-metricbeat-8.md

@@ -44,7 +44,8 @@ You need to repeat this procedure when upgrading the {{stack}} to get the latest
 
 You can clone index templates in {{kib}}:
 
-* Navigate to **Stack Management** > **Index Management** > **Index Templates**.
+* go to the **Index Management** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+* Select **Index Templates**, 
 * From the **View** dropdown, select **System templates**.
 * Search for the index template.
 * Select the **Clone** action.

deploy-manage/monitor/monitoring-data/config-monitoring-indices-metricbeat-7-internal-collection.md

@@ -15,7 +15,11 @@ When monitoring [using {{metricbeat}} 7](../stack-monitoring/collecting-monitori
 * `.monitoring-{{product}}-7-mb-{{date}}`, when using {{metricbeat}} 7.
 * `.monitoring-{{product}}-7-{{date}}`, when using internal collection.
 
-The settings and mappings for these indices are determined by [legacy index templates](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-put-template) named `.monitoring-{{product}}`. You can retrieve these templates in {{kib}} by navigating to **Stack Management** > **Index Management** > **Index Templates**, or by using the {{es}} `_template` API:
+The settings and mappings for these indices are determined by [legacy index templates](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-put-template) named `.monitoring-{{product}}`. 
+
+You can retrieve these templates in {{kib}}. To manage index templates, go to the **Index Management** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), and then select **Index Templates**, 
+
+You can also use the {{es}} `_template` API:
 
 ```console
 GET /_template/.monitoring-*