diff --git a/deploy-manage/api-keys/elasticsearch-api-keys.md b/deploy-manage/api-keys/elasticsearch-api-keys.md index 83ba70ed33..c992ca1459 100644 --- a/deploy-manage/api-keys/elasticsearch-api-keys.md +++ b/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. diff --git a/deploy-manage/kibana-reporting-configuration.md b/deploy-manage/kibana-reporting-configuration.md index 29ded532fd..182c843d2c 100644 --- a/deploy-manage/kibana-reporting-configuration.md +++ b/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). :::: diff --git a/deploy-manage/license/manage-your-license-in-self-managed-cluster.md b/deploy-manage/license/manage-your-license-in-self-managed-cluster.md index 114fd38fda..839d300e6f 100644 --- a/deploy-manage/license/manage-your-license-in-self-managed-cluster.md +++ b/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). diff --git a/deploy-manage/manage-connectors.md b/deploy-manage/manage-connectors.md index 0f9c6d7946..270668b82e 100644 --- a/deploy-manage/manage-connectors.md +++ b/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 diff --git a/deploy-manage/manage-spaces.md b/deploy-manage/manage-spaces.md index 0754e9930a..bec7b7892a 100644 --- a/deploy-manage/manage-spaces.md +++ b/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 diff --git a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md index aca49e5a72..e4116b715b 100644 --- a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md +++ b/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": { diff --git a/deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-elastic-agent.md b/deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-elastic-agent.md index 466b85c6c3..666ff11616 100644 --- a/deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-elastic-agent.md +++ b/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. diff --git a/deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-metricbeat-8.md b/deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-metricbeat-8.md index cdcd2a710a..ea2da08e64 100644 --- a/deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-metricbeat-8.md +++ b/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. diff --git a/deploy-manage/monitor/monitoring-data/config-monitoring-indices-metricbeat-7-internal-collection.md b/deploy-manage/monitor/monitoring-data/config-monitoring-indices-metricbeat-7-internal-collection.md index 5f76c02446..5c271a5530 100644 --- a/deploy-manage/monitor/monitoring-data/config-monitoring-indices-metricbeat-7-internal-collection.md +++ b/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-* diff --git a/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md b/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md index ef8ae826a4..1cecdff528 100644 --- a/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md +++ b/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md @@ -43,7 +43,7 @@ Some action types are subscription features, while others are free. For a compar To review and modify existing **{{stack-monitor-app}}** rules, click **Enter setup mode** on the **Cluster overview** page. Cards with alerts configured are annotated with an indicator. :::{tip} -Alternatively, to manage all rules, including create and delete functionality go to **{{stack-manage-app}} > {{rules-ui}}**. +Alternatively, to manage all rules, including create and delete functionality, find the **{{rules-ui}}** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). ::: 1. On any card showing available alerts, select the **alerts** indicator. Use the menu to select the type of alert for which you’d like to be notified. diff --git a/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md index 6738aba40c..54d575b04c 100644 --- a/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md @@ -57,7 +57,7 @@ Logs and metrics that get sent to a dedicated monitoring {{es}} deployment [may ## Retention of logging and monitoring indices [logging-and-monitoring-retention] -When sending monitoring and logging data to a deployment, an ILM policy is pre-configured to control data retention. To view or edit the policies, open {{kib}} **Stack management > Data > Index Lifecycle Policies**. +When sending monitoring and logging data to a deployment, an ILM policy is pre-configured to control data retention. To view or edit the policies, Go to the **Index Lifecycle Policiess** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). For monitoring indices, the retention period is configured in the `.monitoring-8-ilm-policy` index lifecycle policy. diff --git a/deploy-manage/production-guidance/kibana-task-manager-scaling-considerations.md b/deploy-manage/production-guidance/kibana-task-manager-scaling-considerations.md index e2ea9e5b4d..7fa326367f 100644 --- a/deploy-manage/production-guidance/kibana-task-manager-scaling-considerations.md +++ b/deploy-manage/production-guidance/kibana-task-manager-scaling-considerations.md @@ -70,7 +70,7 @@ By default, {{kib}} polls for tasks at a rate of 10 tasks every 500 milliseconds - As of v8.15 a new task claim strategy was introduced: `mget`. And as of v8.18, `mget` has been made the default strategy -as part of some performance improvement efforts-, with a default polling interval of 500 milliseconds. Since these changes offers a better task execution performance, It is highly recommended you to upgrade to v8.18. -- Maximum number of concurrent tasks can be changed by using `xpack.task_manager.capacity`, The default value is 10, the minimum and maximum values ​​are 5 and 50 respectively. +- Maximum number of concurrent tasks can be changed by using `xpack.task_manager.capacity`, The default value is 10, the minimum and maximum values are 5 and 50 respectively. In practice, a {{kib}} instance will only achieve the upper bound of `1200/tpm` if the duration of task execution is below the polling rate of 500 milliseconds. But for the most part, the duration of tasks is above that threshold, it can vary greatly as {{es}} and {{kib}} usage grow and task complexity increases (such as alerts executing heavy queries across large datasets). Therefore you should find your the average execution time of your tasks to estimate the number of {{kib}} instances you need. diff --git a/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md b/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md index 287f02aa0c..70a782d342 100644 --- a/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md +++ b/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md @@ -35,8 +35,8 @@ With this method, you can only remove trusted environments relying exclusively o :alt: button for deleting a trusted environment ::: -4. In {{kib}}, go to **Stack Management** > **Remote Clusters**. -5. In the list of existing remote clusters, delete the ones corresponding to the trusted environment you removed earlier. +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. In the list of existing remote clusters, delete the ones corresponding to the trusted environment you removed earlier. ## Update a certificate-based trusted environment [ec_update_a_certificate_based_trusted_environment] diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md index 2b7cb6e9bd..30bb96e6a3 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md @@ -201,7 +201,8 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. ### Using {{kib}} [ec_using_kibana_3] -1. Open the {{kib}} main menu, and select **Stack Management > Data > Remote Clusters > Add a remote cluster**. +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. Enable **Manually enter proxy address and server name**. 3. Fill in the following fields: diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md index 17fb26bf50..2470851d81 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md @@ -139,7 +139,8 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. ### Using {{kib}} [ec_using_kibana_2] -1. Open the {{kib}} main menu, and select **Stack Management > Data > Remote Clusters > Add a remote cluster**. +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. Enable **Manually enter proxy address and server name**. 3. Fill in the following fields: diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md index f91b3343cc..7a5b0f33f7 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md @@ -168,7 +168,8 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. ### Using {{kib}} [ec_using_kibana] -1. Open the {{kib}} main menu, and select **Stack Management > Data > Remote Clusters > Add a remote cluster**. +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. Enable **Manually enter proxy address and server name**. 3. Fill in the following fields: diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md b/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md index ba88126f11..493933edac 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md @@ -221,7 +221,8 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. ### Using {{kib}} [ec_using_kibana_4] -1. Open the {{kib}} main menu, and select **Stack Management > Data > Remote Clusters > Add a remote cluster**. +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. Enable **Manually enter proxy address and server name**. 3. Fill in the following fields: diff --git a/deploy-manage/remote-clusters/ece-edit-remove-trusted-environment.md b/deploy-manage/remote-clusters/ece-edit-remove-trusted-environment.md index 6215fa4767..54b870ad44 100644 --- a/deploy-manage/remote-clusters/ece-edit-remove-trusted-environment.md +++ b/deploy-manage/remote-clusters/ece-edit-remove-trusted-environment.md @@ -35,8 +35,8 @@ With this method, you can only remove trusted environments relying exclusively o :alt: button for deleting a trusted environment ::: -4. In {{kib}}, go to **Stack Management** > **Remote Clusters**. -5. In the list of existing remote clusters, delete the ones corresponding to the trusted environment you removed earlier. +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. In the list of existing remote clusters, delete the ones corresponding to the trusted environment you removed earlier. ## Update a certificate-based trusted environment [ece_update_a_certificate_based_trusted_environment] diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md index d02ec683ab..e908c26948 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md @@ -144,7 +144,8 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. ### Using {{kib}} [ece_using_kibana_3] -1. Open the {{kib}} main menu, and select **Stack Management > Data > Remote Clusters > Add a remote cluster**. +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. Enable **Manually enter proxy address and server name**. 3. Fill in the following fields: diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md b/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md index 566281d8d7..6d068cbcd1 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md @@ -216,7 +216,8 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. ### Using {{kib}} [ece_using_kibana_2] -1. Open the {{kib}} main menu, and select **Stack Management > Data > Remote Clusters > Add a remote cluster**. +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. Enable **Manually enter proxy address and server name**. 3. Fill in the following fields: diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md index 41edb63242..ecfa325c36 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md @@ -172,7 +172,8 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. ### Using {{kib}} [ece_using_kibana] -1. Open the {{kib}} main menu, and select **Stack Management > Data > Remote Clusters > Add a remote cluster**. +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. Enable **Manually enter proxy address and server name**. 3. Fill in the following fields: diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md index cca11e1893..c2eb3a968d 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md @@ -220,7 +220,8 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. ### Using {{kib}} [ece_using_kibana_4] -1. Open the {{kib}} main menu, and select **Stack Management > Data > Remote Clusters > Add a remote cluster**. +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. Enable **Manually enter proxy address and server name**. 3. Fill in the following fields: diff --git a/deploy-manage/remote-clusters/remote-clusters-api-key.md b/deploy-manage/remote-clusters/remote-clusters-api-key.md index 9144ec25ad..24a0839a75 100644 --- a/deploy-manage/remote-clusters/remote-clusters-api-key.md +++ b/deploy-manage/remote-clusters/remote-clusters-api-key.md @@ -151,11 +151,13 @@ You must have the `manage` cluster privilege to connect remote clusters. The local cluster uses the [remote cluster interface](elasticsearch://reference/elasticsearch/configuration-reference/networking-settings.md) to establish communication with remote clusters. The coordinating nodes in the local cluster establish [long-lived](elasticsearch://reference/elasticsearch/configuration-reference/networking-settings.md#long-lived-connections) TCP connections with specific nodes in the remote cluster. {{es}} requires these connections to remain open, even if the connections are idle for an extended period. -To add a remote cluster from Stack Management in {{kib}}: +To add a remote cluster in {{kib}}: -1. Select **Remote Clusters** from the side navigation. -2. Enter a name (*cluster alias*) for the remote cluster. -3. Specify the {{es}} endpoint URL, or the IP address or host name of the remote cluster followed by the remote cluster port (defaults to `9443`). For example, `cluster.es.eastus2.staging.azure.foundit.no:9443` or `192.168.1.1:9443`. +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**. +3. Select **API keys** as the connection type. +4. Enter a name (*cluster alias*) for the remote cluster. +5. Specify the {{es}} endpoint URL, or the IP address or host name of the remote cluster followed by the remote cluster port (defaults to `9443`). For example, `cluster.es.eastus2.staging.azure.foundit.no:9443` or `192.168.1.1:9443`. ::::{note} If the remote cluster is part of an {{ech}}, {{ece}}, or {{eck}} deployment, configure the connection to use `proxy`. The default `sniff` mode doesn't work in these environments. Refer to the [connection modes](/deploy-manage/remote-clusters/remote-clusters-self-managed.md#sniff-proxy-modes) description for more information. @@ -337,7 +339,7 @@ cluster: To use a remote cluster for {{ccr}} or {{ccs}}, you need to create user roles with [remote indices privileges](/deploy-manage/users-roles/cluster-or-deployment-auth/role-structure.md#roles-remote-indices-priv) or [remote cluster privileges](/deploy-manage/users-roles/cluster-or-deployment-auth/role-structure.md#roles-remote-cluster-priv) on the local cluster. -You can manage users and roles from Stack Management in {{kib}} by selecting **Security > Roles** from the side navigation. You can also use the [role management APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-security) to add, update, remove, and retrieve roles dynamically. +To manage users and roles in {{kib}}, go to the **Roles** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). You can also use the [role management APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-security) to add, update, remove, and retrieve roles dynamically. The following examples use the [Create or update roles](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-put-role) API. You must have at least the `manage_security` cluster privilege to use this API. diff --git a/deploy-manage/remote-clusters/remote-clusters-cert.md b/deploy-manage/remote-clusters/remote-clusters-cert.md index 53591dfe9e..b9e82b435c 100644 --- a/deploy-manage/remote-clusters/remote-clusters-cert.md +++ b/deploy-manage/remote-clusters/remote-clusters-cert.md @@ -61,11 +61,13 @@ You must have the `manage` cluster privilege to connect remote clusters. The local cluster uses the [transport interface](elasticsearch://reference/elasticsearch/configuration-reference/networking-settings.md) to establish communication with remote clusters. The coordinating nodes in the local cluster establish [long-lived](elasticsearch://reference/elasticsearch/configuration-reference/networking-settings.md#long-lived-connections) TCP connections with specific nodes in the remote cluster. {{es}} requires these connections to remain open, even if the connections are idle for an extended period. -To add a remote cluster from Stack Management in {{kib}}: +To add a remote cluster in {{kib}}: -1. Select **Remote Clusters** from the side navigation. -2. Enter a name (*cluster alias*) for the remote cluster. -3. Specify the {{es}} endpoint URL, or the IP address or host name of the remote cluster followed by the transport port (defaults to `9300`). For example, `cluster.es.eastus2.staging.azure.foundit.no:9300` or `192.168.1.1:9300`. +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**. +3. Select **Certificates** as the connection type. +4. Enter a name (*cluster alias*) for the remote cluster. +5. Specify the {{es}} endpoint URL, or the IP address or host name of the remote cluster followed by the transport port (defaults to `9300`). For example, `cluster.es.eastus2.staging.azure.foundit.no:9300` or `192.168.1.1:9300`. Alternatively, use the [cluster update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings) to add a remote cluster. You can also use this API to dynamically configure remote clusters for *every* node in the local cluster. To configure remote clusters on individual nodes in the local cluster, define static settings in [`elasticsearch.yml`](/deploy-manage/stack-settings.md) for each node. @@ -246,7 +248,7 @@ You must use the same role names on both the local and remote clusters. For exam :::: -You can manage users and roles from Stack Management in {{kib}} by selecting **Security > Roles** from the side navigation. You can also use the [role management APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-security) to add, update, remove, and retrieve roles dynamically. When you use the APIs to manage roles in the `native` realm, the roles are stored in an internal {{es}} index. +To manage users and roles in {{kib}}, go to the **Roles** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). You can also use the [role management APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-security) to add, update, remove, and retrieve roles dynamically. When you use the APIs to manage roles in the `native` realm, the roles are stored in an internal {{es}} index. The following requests use the [create or update roles API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-put-role). You must have at least the `manage_security` cluster privilege to use this API. diff --git a/deploy-manage/tools/cross-cluster-replication/_connect_to_a_remote_cluster.md b/deploy-manage/tools/cross-cluster-replication/_connect_to_a_remote_cluster.md index 66018c5f2e..e3ecbf09d6 100644 --- a/deploy-manage/tools/cross-cluster-replication/_connect_to_a_remote_cluster.md +++ b/deploy-manage/tools/cross-cluster-replication/_connect_to_a_remote_cluster.md @@ -19,11 +19,12 @@ To replicate an index on a remote cluster (Cluster A) to a local cluster (Cluste :alt: ClusterA contains the leader index and ClusterB contains the follower index ::: -To configure a remote cluster from Stack Management in {{kib}}: +To configure a remote cluster in {{kib}}: 1. Set up a [secure connection](/deploy-manage/remote-clusters/remote-clusters-self-managed.md#add-remote-clusters) as needed. -2. Select **Remote Clusters** from the side navigation. -3. Specify the {{es}} endpoint URL, or the IP address or host name of the remote cluster (`ClusterA`) followed by the transport port (defaults to `9300`). For example, `cluster.es.eastus2.staging.azure.foundit.no:9400` or `192.168.1.1:9300`. +2. 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). +3. Select the appropriate connection type. +4. Specify the {{es}} endpoint URL, or the IP address or host name of the remote cluster (`ClusterA`) followed by the transport port (defaults to `9300`). For example, `cluster.es.eastus2.staging.azure.foundit.no:9400` or `192.168.1.1:9300`. ::::{dropdown} API example You can also use the [cluster update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings) to add a remote cluster: diff --git a/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-auto-follow.md b/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-auto-follow.md index f870729dc3..211fd67e2e 100644 --- a/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-auto-follow.md +++ b/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-auto-follow.md @@ -17,13 +17,14 @@ You use [auto-follow patterns](manage-auto-follow-patterns.md) to automatically An auto-follow pattern specifies the remote cluster you want to replicate from, and one or more index patterns that specify the rolling time series indices you want to replicate. -To create an auto-follow pattern from Stack Management in {{kib}}: - -1. Select **Cross Cluster Replication** in the side navigation and choose the **Auto-follow patterns** tab. -2. Enter a name for the auto-follow pattern, such as `beats`. -3. Choose the remote cluster that contains the index you want to replicate, which in the example scenario is Cluster A. -4. Enter one or more index patterns that identify the indices you want to replicate from the remote cluster. For example, enter `metricbeat-* packetbeat-*` to automatically create followers for {{metricbeat}} and {{packetbeat}} indices. -5. Enter **follower-** as the prefix to apply to the names of the follower indices so you can more easily identify replicated indices. +To create an auto-follow pattern from in {{kib}}: + +1. Go to the **Cross Cluster Replication** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). +2. Choose the **Auto-follow patterns** tab. +3. Enter a name for the auto-follow pattern, such as `beats`. +4. Choose the remote cluster that contains the index you want to replicate, which in the example scenario is Cluster A. +5. Enter one or more index patterns that identify the indices you want to replicate from the remote cluster. For example, enter `metricbeat-* packetbeat-*` to automatically create followers for {{metricbeat}} and {{packetbeat}} indices. +6. Enter **follower-** as the prefix to apply to the names of the follower indices so you can more easily identify replicated indices. As new indices matching these patterns are created on the remote, {{es}} automatically replicates them to local follower indices. diff --git a/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-follower-index.md b/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-follower-index.md index d607e7ddfc..14277112f2 100644 --- a/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-follower-index.md +++ b/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-follower-index.md @@ -15,12 +15,13 @@ products: When you create a follower index, you reference the remote cluster and the leader index in your remote cluster. -To create a follower index from Stack Management in {{kib}}: +To create a follower index in {{kib}}: -1. Select **Cross-Cluster Replication** in the side navigation and choose the **Follower Indices** tab. -2. Choose the cluster (ClusterA) containing the leader index you want to replicate. -3. Enter the name of the leader index, which is `kibana_sample_data_ecommerce` if you are following the tutorial. -4. Enter a name for your follower index, such as `follower-kibana-sample-data`. +1. Go to the **Cross Cluster Replication** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). +2. Choose the **Follower Indices** tab. +3. Choose the cluster (ClusterA) containing the leader index you want to replicate. +4. Enter the name of the leader index, which is `kibana_sample_data_ecommerce` if you are following the tutorial. +5. Enter a name for your follower index, such as `follower-kibana-sample-data`. {{es}} initializes the follower using the [remote recovery](../cross-cluster-replication.md#ccr-remote-recovery) process, which transfers the existing Lucene segment files from the leader index to the follower index. The index status changes to **Paused**. When the remote recovery process is complete, the index following begins and the status changes to **Active**. diff --git a/deploy-manage/tools/cross-cluster-replication/manage-auto-follow-patterns.md b/deploy-manage/tools/cross-cluster-replication/manage-auto-follow-patterns.md index e539913dd4..6382fb6665 100644 --- a/deploy-manage/tools/cross-cluster-replication/manage-auto-follow-patterns.md +++ b/deploy-manage/tools/cross-cluster-replication/manage-auto-follow-patterns.md @@ -27,7 +27,10 @@ The data streams replicated from a remote cluster by CCR are protected from loca Auto-follow patterns are especially useful with [{{ilm-cap}}](../../../manage-data/lifecycle/index-lifecycle-management.md), which might continually create new indices on the cluster containing the leader index. $$$ccr-access-ccr-auto-follow$$$ -To start using {{ccr}} auto-follow patterns from Stack Management in {{kib}}, select **Cross-Cluster Replication** from the side navigation and choose the **Auto-follow patterns** tab. +To start using {{ccr}} auto-follow patterns from {{kib}}: + +1. Go to the **Cross Cluster Replication** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). +2. Choose the **Follower Indices** tab. diff --git a/deploy-manage/tools/cross-cluster-replication/manage-cross-cluster-replication.md b/deploy-manage/tools/cross-cluster-replication/manage-cross-cluster-replication.md index aca47fccb8..20721ad6d2 100644 --- a/deploy-manage/tools/cross-cluster-replication/manage-cross-cluster-replication.md +++ b/deploy-manage/tools/cross-cluster-replication/manage-cross-cluster-replication.md @@ -16,7 +16,8 @@ products: Use the following information to manage {{ccr}} tasks, such as inspecting replication progress, pausing and resuming replication, recreating a follower index, and terminating replication. $$$ccr-access-ccr$$$ -To start using {{ccr}}, access {{kib}} and go to **Management > Stack Management**. In the side navigation, select **Cross-Cluster Replication**. +To start using {{ccr}} from {{kib}}, go to the **Cross Cluster Replication** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). + diff --git a/deploy-manage/tools/snapshot-and-restore/create-snapshots.md b/deploy-manage/tools/snapshot-and-restore/create-snapshots.md index 122a8225a6..728c20eb58 100644 --- a/deploy-manage/tools/snapshot-and-restore/create-snapshots.md +++ b/deploy-manage/tools/snapshot-and-restore/create-snapshots.md @@ -113,7 +113,11 @@ POST _security/role/slm-read-only ### Create an {{slm-init}} policy [create-slm-policy] -To manage {{slm-init}} in {{kib}}, go to the main menu and click **Stack Management** > **Snapshot and Restore** > **Policies**. To create a policy, click **Create policy**. +To manage {{slm-init}} in {{kib}}: + +1. Go to the **Snapshot and Restore** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). +2. Select the **Policies** tab. +3. To create a policy, click **Create policy**. You can also manage {{slm-init}} using the [{{slm-init}} APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-slm). To create a policy, use the [create {{slm-init}} policy API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-slm-put-lifecycle). @@ -189,7 +193,11 @@ A snapshot repository can safely scale to thousands of snapshots. However, to ma ### Update an existing {{slm-init}} policy [update-slm-policy] -You can update an existing {{slm-init}} policy after it's created. To manage {{slm-init}} in {{kib}}, go to the main menu and click **Stack Management** > **Snapshot and Restore** > **Policies**, click **Edit** `✎`, and make the desired change. +You can update an existing {{slm-init}} policy after it's created. To manage {{slm-init}} in {{kib}}: + +1. Go to the **Snapshot and Restore** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). +2. Select the **Policies** tab. +3. On the policy that you want to edit, click **Edit** `✎`, and make the desired change. For example, you can change the schedule, or snapshot retention-related configurations. diff --git a/deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.md b/deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.md index 8157caee89..8909bf21ef 100644 --- a/deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.md +++ b/deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.md @@ -62,7 +62,11 @@ In **{{ech}}**, snapshot repositories are automatically registered for you, but * {{kib}}'s **Snapshot and Restore** feature * {{es}}'s [snapshot repository management APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-snapshot) -To manage repositories in {{kib}}, go to the main menu and click **Stack Management** > **Snapshot and Restore** > **Repositories**. To register a snapshot repository, click **Register repository**. +To manage repositories in {{kib}}: + +1. Go to the **Snapshot and Restore** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). +2. Select the **Repositories** tab. +3. To register a snapshot repository, click **Register repository**. You can also register a repository using the [Create snapshot repository API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-snapshot-create-repository). diff --git a/deploy-manage/tools/snapshot-and-restore/restore-snapshot.md b/deploy-manage/tools/snapshot-and-restore/restore-snapshot.md index 89833e8097..c0e15ab7c9 100644 --- a/deploy-manage/tools/snapshot-and-restore/restore-snapshot.md +++ b/deploy-manage/tools/snapshot-and-restore/restore-snapshot.md @@ -37,6 +37,7 @@ This guide also provides tips for [restoring to another cluster](#restore-differ ```console GET _index_template/*?filter_path=index_templates.name,index_templates.index_template.index_patterns,index_templates.index_template.data_stream + ``` - If no such template exists, you can [matching index template](/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md#create-ts-index-template) or restore a cluster state that contains one. Without a matching index template, a data stream can’t roll over or create backing indices. - If your snapshot contains data from App Search or Workplace Search, ensure you’ve restored the Enterprise Search encryption key before restoring the snapshot. @@ -53,7 +54,10 @@ When restoring data from a snapshot, keep the following in mind: ## Get a list of available snapshots -To view a list of available snapshots in {{kib}}, go to **Stack Management > Snapshot and Restore**. +To view a list of available snapshots in {{kib}}: + +1. Go to the **Snapshot and Restore** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). +2. Select the **Snapshots** tab. You can also use the get repository API and the get snapshot API to find snapshots that are available to restore. First, use the get repository API to fetch a list of registered snapshot repositories. diff --git a/deploy-manage/tools/snapshot-and-restore/self-managed.md b/deploy-manage/tools/snapshot-and-restore/self-managed.md index e06c2b7fdc..98676e0c81 100644 --- a/deploy-manage/tools/snapshot-and-restore/self-managed.md +++ b/deploy-manage/tools/snapshot-and-restore/self-managed.md @@ -44,7 +44,12 @@ You can register and manage snapshot repositories in two ways: * {{kib}}'s **Snapshot and Restore** feature * {{es}}'s [snapshot repository management APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-snapshot) -To manage repositories in {{kib}}, go to the main menu and click **Stack Management** > **Snapshot and Restore** > **Repositories**. To register a snapshot repository, click **Register repository**. +To manage repositories in {{kib}}: + +1. Go to the **Snapshot and Restore** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). +2. Select the **Repositories** tab. + +To register a snapshot repository, click **Register repository**. You can also register a repository using the [Create snapshot repository API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-snapshot-create-repository). diff --git a/deploy-manage/upgrade/deployment-or-cluster/saved-object-migrations.md b/deploy-manage/upgrade/deployment-or-cluster/saved-object-migrations.md index 4bb3779c40..911975cc91 100644 --- a/deploy-manage/upgrade/deployment-or-cluster/saved-object-migrations.md +++ b/deploy-manage/upgrade/deployment-or-cluster/saved-object-migrations.md @@ -12,7 +12,7 @@ products: Each time you upgrade {{kib}}, an upgrade migration is performed to ensure that all [saved objects](/explore-analyze/find-and-organize/saved-objects.md) are compatible with the new version. ::::{note} -{{kib}} includes an [**Upgrade Assistant**](../prepare-to-upgrade/upgrade-assistant.md) to help you prepare to upgrade. To access the assistant, go to **Stack Management > Upgrade Assistant**. +{{kib}} includes an [**Upgrade Assistant**](../prepare-to-upgrade/upgrade-assistant.md) to help you prepare to upgrade. To access the assistant, go to the **Upgrade Assistant** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). :::: diff --git a/deploy-manage/upgrade/prepare-to-upgrade.md b/deploy-manage/upgrade/prepare-to-upgrade.md index 8f2f476121..fc77e40129 100644 --- a/deploy-manage/upgrade/prepare-to-upgrade.md +++ b/deploy-manage/upgrade/prepare-to-upgrade.md @@ -63,7 +63,7 @@ If you use {{ccs}}, versions 9.0.0 and later can search only remote clusters run If you use {{ccr}}, a cluster that contains follower indices must run the same or newer (compatible) version as the remote cluster. For more information and to view the version compatibility matrix, refer to [{{ccr-cap}}](/deploy-manage/tools/cross-cluster-replication.md). -To view your remote clusters in {{kib}}, go to **Stack Management > Remote Clusters**. +To view your remote clusters in {{kib}}, 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). :::: ::::{step} (Optional) Close machine learning jobs diff --git a/deploy-manage/upgrade/prepare-to-upgrade/upgrade-assistant.md b/deploy-manage/upgrade/prepare-to-upgrade/upgrade-assistant.md index e0df381ea4..4a25ed3f5a 100644 --- a/deploy-manage/upgrade/prepare-to-upgrade/upgrade-assistant.md +++ b/deploy-manage/upgrade/prepare-to-upgrade/upgrade-assistant.md @@ -13,7 +13,9 @@ products: # Upgrade Assistant [upgrade-assistant] -The Upgrade Assistant helps you [prepare to upgrade](/deploy-manage/upgrade/prepare-to-upgrade.md) to the next major version of the {{stack}}. To access the assistant, go to **{{stack-manage-app}} → Upgrade Assistant**. +The Upgrade Assistant helps you [prepare to upgrade](/deploy-manage/upgrade/prepare-to-upgrade.md) to the next major version of the {{stack}}. + +To access the assistant, go to the **Upgrade Assistant** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). ::::{tip} Upgrade assistant should be run from the latest minor release before a major upgrade. When upgrading to 9.x, ensure you run 8.19.latest, and run the assistant there. diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-sm.md b/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-sm.md index d76285e2e2..54e21522a7 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-sm.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-sm.md @@ -22,7 +22,9 @@ This topic describes resetting passwords after the initial bootstrap password is ## Using {{kib}} -Elastic enables you to easily manage users in {{kib}} on the **Stack Management > Security > Users** page. From this page, you can create users, edit users, assign roles to users, and change user passwords. You can also deactivate or delete existing users. +Elastic enables you to easily manage users in {{kib}} from the **Users** page. From this page, you can create users, edit users, assign roles to users, and change user passwords. You can also deactivate or delete existing users. + +You can access the **Users** management page in the navigation menu or find it using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). ## Using `elasticsearch-reset-password` diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-role-management.md b/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-role-management.md index c0f7c34f85..58c6fc09c0 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-role-management.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-role-management.md @@ -16,7 +16,10 @@ products: Roles are a collection of privileges that allow you to perform actions in {{kib}} and {{es}}. Users are not directly granted privileges, but are instead assigned one or more roles that describe the desired level of access. When you assign a user multiple roles, the user receives a union of the roles’ privileges. This means that you cannot reduce the privileges of a user by assigning them an additional role. You must instead remove or edit one of their existing roles. -To create a role, open the menu, then click **Stack Management > Roles** and click **Create role**. +To create a role: + +1. Go to the **Roles** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). +2. Click **Create role**. ## Required permissions [_required_permissions_7] @@ -38,8 +41,9 @@ Document-level and field-level security affords you even more granularity when i ### Example: Grant access to indices that match the `filebeat-*` pattern [index_privilege_example_1] -1. Go to **Stack Management > Roles**, and then click **Create role**. -2. In **Index privileges**, enter: +1. Go to the **Roles** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). +2. Click **Create role**. +3. In **Index privileges**, enter: 1. `filebeat-*` in the **Index** field. 2. `read` and `view_index_metadata` in the **Privileges** field. @@ -54,14 +58,15 @@ Document-level and field-level security affords you even more granularity when i [Document-level security](/deploy-manage/users-roles/cluster-or-deployment-auth/controlling-access-at-document-field-level.md) is a [subscription feature](https://www.elastic.co/subscriptions). -1. Go to **Stack Management > Roles**, and then click **Create role**. -2. In **Index privileges**, enter: +1. Go to the **Roles** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). +2. Click **Create role**. +3. In **Index privileges**, enter: 1. `filebeat-*` in the **Indices** field. 2. `read` and `view_index_metadata` in the **Privileges** field. -3. Select **Grant read privileges to specific documents**. -4. Enter an {{es}} query that matches the documents your users should access. This example writes a query that allows access to documents that have a `category` field equal to `click`: +4. Select **Grant read privileges to specific documents**. +5. Enter an {{es}} query that matches the documents your users should access. This example writes a query that allows access to documents that have a `category` field equal to `click`: ```sh { @@ -91,8 +96,9 @@ You can assign the same privileges, document-level, and field-level as for [loca ### Example: Grant access to indices in remote clusters [remote_index_privilege_example_1] -1. Go to **Stack Management > Roles**, and then click **Create role**. -2. In **Remote index privileges**, enter: +1. Go to the **Roles** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). +2. Click **Create role**. +3. In **Remote index privileges**, enter: 1. The name of your remote cluster in the **Remote clusters** field. 2. The name of the index in your remote cluster in the **Remote indices** field. diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/native.md b/deploy-manage/users-roles/cluster-or-deployment-auth/native.md index a03eeac3fa..a583a46956 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/native.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/native.md @@ -67,11 +67,13 @@ You can configure a `native` realm in the `xpack.security.authc.realms.native` n ## Manage native users using {{kib}} [managing-native-users] -Elastic enables you to easily manage users in {{kib}} on the **Stack Management > Security > Users** page. From this page, you can create users, edit users, assign roles to users, and change user passwords. You can also deactivate or delete existing users. +Elastic enables you to easily manage users in {{kib}}. To manage users in {{kib}}, go to the **Users** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). + +From this page, you can create users, edit users, assign roles to users, and change user passwords. You can also deactivate or delete existing users. ### Example: Create a user [_create_a_user] -1. Navigate to **Stack Management**, and under **Security**, select **Users**. +1. Go to the **Users** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create user**. 3. Give the user a descriptive username, and choose a secure password. 4. Optional: assign [roles](/deploy-manage/users-roles/cluster-or-deployment-auth/user-roles.md) to the user. diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md b/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md index 6efc10f6a3..b2c8ed0232 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md @@ -119,7 +119,7 @@ To create the role: Now that you created a role, create a user account. -1. Navigate to **Stack Management**, and under **Security**, select **Users**. +1. Go to the **Users** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 2. Click **Create user**. 3. Give this user a descriptive username, and choose a secure password. 4. Assign the **marketing_dashboards_role** that you previously created to this new user. diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/user-roles.md b/deploy-manage/users-roles/cluster-or-deployment-auth/user-roles.md index 94acd3661b..61956cd303 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/user-roles.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/user-roles.md @@ -77,7 +77,7 @@ The way that you assign roles to users depends on your authentication realm: * [Native realm](/deploy-manage/users-roles/cluster-or-deployment-auth/native.md): * Using {{es}} API [`_security` endpoints](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-security) - * [In {{kib}}](/deploy-manage/users-roles/cluster-or-deployment-auth/native.md#managing-native-users), using the **Stack Management > Security > Users** page + * [In {{kib}}](/deploy-manage/users-roles/cluster-or-deployment-auth/native.md#managing-native-users), from the **Users** management page. Find the page in the navigation menu, or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). * [File realm](/deploy-manage/users-roles/cluster-or-deployment-auth/file-based.md): * Using a [`user_roles` file](/deploy-manage/users-roles/cluster-or-deployment-auth/file-based.md#k8s-basic) * In ECK: As part of a [basic authentication secret](/deploy-manage/users-roles/cluster-or-deployment-auth/file-based.md#k8s-basic)