From 8335cc346d508f42942bb0d49ee2275de2d94ee0 Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Wed, 6 Aug 2025 14:37:44 -0400 Subject: [PATCH 1/6] first edit --- .../monitor/autoops/cc-connect-self-managed-to-autoops.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 5dc430f652..a0b84f2c4b 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 @@ -156,7 +156,7 @@ The wizard will generate an installation command based on your configuration. De * Windows :::{tip} -We recommend installing the agent on a separate machine from the one where your self-managed cluster is running. +To ensure optimum resource usage, we recommend installing the agent on a different machine from the one where your self-managed cluster is running. ::: Complete the following steps to run the command: From 435a704cfbf7e4cd2729335d9cbc12c96b4bd299 Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Thu, 7 Aug 2025 19:26:51 -0400 Subject: [PATCH 2/6] [Private preview] Update AutoOps for self-managed clusters docs --- deploy-manage/_snippets/autoops-cc-ech-faq.md | 4 + deploy-manage/cloud-connect.md | 10 +-- .../autoops/cc-cloud-connect-autoops-faq.md | 10 ++- ...c-cloud-connect-autoops-troubleshooting.md | 6 +- .../cc-connect-self-managed-to-autoops.md | 86 ++++++++++++++++--- 5 files changed, 94 insertions(+), 22 deletions(-) create mode 100644 deploy-manage/_snippets/autoops-cc-ech-faq.md diff --git a/deploy-manage/_snippets/autoops-cc-ech-faq.md b/deploy-manage/_snippets/autoops-cc-ech-faq.md new file mode 100644 index 0000000000..21c4c9bc36 --- /dev/null +++ b/deploy-manage/_snippets/autoops-cc-ech-faq.md @@ -0,0 +1,4 @@ +:::{dropdown} Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps? + +This path is not supported. Currently, we only support using Cloud Connect to connect self-managed clusters to AutoOps. +::: \ No newline at end of file diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index f925620f62..25ad6b0c86 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -13,9 +13,9 @@ Cloud Connect enables you to use {{ecloud}} services in your self-managed cluste AutoOps is the first service available for use with Cloud Connect. More services are coming soon. -### AutoOps +### AutoOps for self-managed clusters -[AutoOps](/deploy-manage/monitor/autoops.md) is a monitoring tool that helps you manage your cluster with real-time issue detection, performance recommendations, and resolution paths. By analyzing hundreds of {{es}} metrics, your configuration, and usage patterns, AutoOps recommends operational and monitoring insights that deliver real savings in administration time and hardware cost. +[AutoOps](/deploy-manage/monitor/autoops.md) is a monitoring tool that helps you manage your cluster with real-time issue detection, performance recommendations, and resolution paths. By analyzing hundreds of {{es}} metrics, your configuration, and your usage patterns, AutoOps recommends operational and monitoring insights that deliver real savings in administration time and hardware cost. Learn how to set up and use [](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md). @@ -32,13 +32,9 @@ Each cloud connected service has its own licensing and payment requirements. :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md ::: +:::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md ::: -:::{dropdown} Will my data be safe when using Cloud Connect? - -$$$cc-data$$$ - -Yes. For AutoOps, {{agent}} only sends cluster metrics to {{ecloud}}, not the underlying data within your cluster. Learn more in [](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md). ::: :::{dropdown} Are more services going to be available with Cloud Connect? diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md index fe49a7b0fd..667cfba45a 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md @@ -11,7 +11,7 @@ navigation_title: FAQ Find answers to your questions about AutoOps for self-managed clusters. -:::{dropdown} Why should I use AutoOps for my self-managed cluster? +:::{dropdown} Why should I use AutoOps for my self-managed clusters? AutoOps simplifies the operation of your {{es}} clusters by providing real-time monitoring, performance insights, and issue detection. It helps you identify and resolve problems like ingestion bottlenecks and unbalanced shards, reducing manual effort and preventing performance issues. @@ -20,6 +20,9 @@ When you need support, AutoOps gives the Elastic team real-time visibility into Using AutoOps for your self-managed cluster lets you access all these features without the operational overhead of managing their infrastructure. ::: +:::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md +::: + :::{dropdown} Does AutoOps for self-managed clusters require additional payment? :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md @@ -42,6 +45,11 @@ You can connect to AutoOps on a standalone {{stack}}, ECE ({{ece}}), or ECK ({{e Not at this time. AutoOps is currently only available as a cloud service and you need an internet connection to send metrics to {{ecloud}}. For air-gapped environments, we plan to offer a locally deployable version in the future. ::: +:::{dropdown} Can I use macOS to install {{agent}}? + +macOS is not a supported platform for installing the agent and connecting your self-managed cluster to AutoOps. +::: + :::{dropdown} Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}? You may need to define an IP address if your organization’s settings will block the agent from sending out data. diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md index c250ab4460..164936ced7 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md @@ -53,8 +53,8 @@ The following table shows the errors you might encounter if something goes wrong | `HTTP_504` | Request timed out | Did not receive a response from the cluster within the expected time frame. Check the cluster's performance or consider changing your connection timeout settings. | | `CLUSTER_ALREADY_CONNECTED` | Cluster connected to another account | This cluster is already connected to another {{ecloud}} organization. Disconnect it and then try again. | | `CLUSTER_NOT_READY` | {{es}} cluster is still connecting | Your {{es}} cluster is not yet ready to connect. Wait a few moments for it to finish starting up and then try again. | -| `HTTP_0` | Connection error | {{agent}} couldn't connect to the cluster. There may be various reasons for this issue. Review the [documentation](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) or contact [Elastic support](https://cloud.elastic.co/login?source=support&fromURI=https%3A%2F%2Fauth.elastic.co%2Fapp%2Felastic-customer_dreammachinecustomer_1%2Fexkgw653gkKlRTQXQ1t7%2Fsso%2Fsaml) if the issue persists. | +| `HTTP_0` | Connection error | {{agent}} couldn't connect to the cluster. There may be various reasons for this issue. Review the [documentation](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) or contact [Elastic support](https://support.elastic.co/) if the issue persists. | | `LICENSE_EXPIRED` | Elastic license is expired | Contact [sales](https://www.elastic.co/contact#sales) to renew your license. | -| `LICENSE_USED_BY_ANOTHER_ACCOUNT` | License key connected to another account | A license key can only be connected to one {{ecloud}} organization. Contact [Elastic support](https://cloud.elastic.co/login?source=support&fromURI=https%3A%2F%2Fauth.elastic.co%2Fapp%2Felastic-customer_dreammachinecustomer_1%2Fexkgw653gkKlRTQXQ1t7%2Fsso%2Fsaml) for help. | +| `LICENSE_USED_BY_ANOTHER_ACCOUNT` | License key connected to another account | A license key can only be connected to one {{ecloud}} organization. Contact [Elastic support](https://support.elastic.co/) for help. | | `VERSION_MISMATCH` | {{es}} version is unsupported | Upgrade your cluster to a [supported version](https://www.elastic.co/support/eol). | -| `UNKNOWN_ERROR` | Installation failed | {{agent}} couldn't be installed due to an unknown issue. Consult the troubleshooting guide or contact [Elastic support](https://cloud.elastic.co/login?source=support&fromURI=https%3A%2F%2Fauth.elastic.co%2Fapp%2Felastic-customer_dreammachinecustomer_1%2Fexkgw653gkKlRTQXQ1t7%2Fsso%2Fsaml) for more help. | \ No newline at end of file +| `UNKNOWN_ERROR` | Installation failed | {{agent}} couldn't be installed due to an unknown issue. Consult the troubleshooting guide or contact [Elastic support](https://support.elastic.co/) for more help. | \ No newline at end of file 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 a0b84f2c4b..a4f8252299 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 @@ -18,7 +18,7 @@ Complete the steps in the following subsections to connect your cluster to AutoO Ensure your system meets the following requirements before proceeding: * Your cluster is on a [supported {{es}} version](https://www.elastic.co/support/eol). -* You have an [Enterprise self-managed license](https://www.elastic.co/subscriptions) or an active self-managed [free trial](https://cloud.elastic.co/registration). +* You have an [Enterprise self-managed license](https://www.elastic.co/subscriptions) or an active ECE, ECK, or self-managed [trial](https://cloud.elastic.co/registration). * The agent you install for the connection is allowed to send metrics outside your organization to {{ecloud}}. ## Connect to AutoOps @@ -28,6 +28,34 @@ Ensure your system meets the following requirements before proceeding: ::: ::: +The following steps describe how to connect to AutoOps during the private preview of AutoOps for self-managed clusters. + +:::::{tab-set} +:group: existing-or-new-cloud-account + +::::{tab-item} Existing account +:sync: existing + +If you already have an {{ecloud}} account: +1. Go to the [Cloud Connected Services](https://cloud.elastic.co/connect-cluster-services) page for private preview. +2. Log in to your account. +3. On the **Cloud Connected Services** page, in the **AutoOps** section, select **Connect**. +4. Go through the installation wizard as detailed in the following sections. +:::: + +::::{tab-item} New account +:sync: new + +If you don’t have an existing {{ecloud}} account: +1. Go to the [Cloud Connected Services sign up](https://cloud.elastic.co/registration?onboarding_service_type=ccm) page for private preview. +2. Follow the prompts on your screen to sign up for an account and create an organization. +3. Go through the installation wizard as detailed in the following sections. +:::: + +::::: + + 2. Follow the prompts on your screen to create an organization. 3. Go through the installation wizard as detailed in the following sections. :::: ::::: +--> ### Select installation method @@ -63,8 +88,10 @@ Select one of the following methods to install {{agent}}: * Kubernetes * Docker + :::{important} Using AutoOps for your self-managed cluster requires a new, dedicated {{agent}}. You must install an agent even if you already have an existing one for other purposes. @@ -82,12 +109,45 @@ Depending on your selected installation method, you may have to provide the foll ::::{tab-item} API key :sync: api-key -With this authentication method, you need to [create an API key](/solutions/observability/apm/grant-access-using-api-keys.md) with the following privileges to grant access to your cluster: +With this authentication method, you need to create an API key to grant access to your cluster. Complete the following steps: -| Setting | Privileges | - | --- | --- | - | Cluster privileges | `monitor`, `read_ilm`, and `read_slm` | - | Index privileges | Indices: `*`
`monitor`, `view_index_metadata`, `allow_restricted_indices: true` | +1. From your {{ecloud}} home page, select a deployment. +2. Go to **Stack management** > **API keys** and 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": { + "cluster": [ + "monitor", + "read_ilm", + "read_slm" + ], + "indices": [ + { + "names": [ + "*" + ], + "privileges": [ + "monitor", + "view_index_metadata" + ], + "allow_restricted_indices": true + } + ], + "applications": [], + "run_as": [], + "metadata": {}, + "transient_metadata": { + "enabled": true + } + } +} + +``` +5. Select **Create API key**. +6. When prompted to copy the key, select **Beats** from the dropdown. +7. Copy the key and save it for later. You will need it when you [install the agent](#install-agent). :::: @@ -152,8 +212,10 @@ The wizard will generate an installation command based on your configuration. De * Docker * Docker * Docker compose + :::{tip} To ensure optimum resource usage, we recommend installing the agent on a different machine from the one where your self-managed cluster is running. @@ -183,6 +245,8 @@ If the connection is unsuccessful, an error message will appear with a possible Sometimes, an exact reason for the failure cannot be determined. In this case, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us). +To uninstall the agent, refer to [](/solutions/security/configure-elastic-defend/uninstall-elastic-agent.md). + ### Launch AutoOps If the connection is successful, AutoOps will start analyzing your metrics and reporting on any issues found. Depending on the size of your cluster, this process can take up to 30 minutes. From 8bbd5763bf829722984ccbec87b6c370173f2776 Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Fri, 8 Aug 2025 12:11:24 -0400 Subject: [PATCH 3/6] PR feedback --- deploy-manage/cloud-connect.md | 2 +- deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index 25ad6b0c86..c3ad8716b8 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -32,9 +32,9 @@ Each cloud connected service has its own licensing and payment requirements. :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md ::: -:::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md ::: +:::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md ::: :::{dropdown} Are more services going to be available with Cloud Connect? diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md index 667cfba45a..97aaa1375b 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md @@ -47,7 +47,7 @@ Not at this time. AutoOps is currently only available as a cloud service and you :::{dropdown} Can I use macOS to install {{agent}}? -macOS is not a supported platform for installing the agent and connecting your self-managed cluster to AutoOps. +macOS is not a supported platform for installing {{agent}} and connecting your self-managed cluster to AutoOps. ::: :::{dropdown} Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}? From abe0a186ea1ba6dff430d5d00ab65c71aaa230a5 Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Fri, 8 Aug 2025 12:44:59 -0400 Subject: [PATCH 4/6] updating prereqs --- .../monitor/autoops/cc-connect-self-managed-to-autoops.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) 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 a4f8252299..c3fd8519a0 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 @@ -9,7 +9,7 @@ navigation_title: Connect your self-managed cluster # Connect your self-managed cluster to AutoOps -To use AutoOps with your self-managed cluster, you first need to create an {{ecloud}} account or log in to your existing account. An installation wizard will then guide you through the steps of installing {{agent}} to send metrics from your self-managed cluster to AutoOps in {{ecloud}}. +To use AutoOps with your ECE, ECK, or self-managed cluster, you first need to create an {{ecloud}} account or log in to your existing account. An installation wizard will then guide you through the steps of installing {{agent}} to send metrics from your cluster to AutoOps in {{ecloud}}. Complete the steps in the following subsections to connect your cluster to AutoOps. The connection process takes about 10 minutes. @@ -18,8 +18,8 @@ Complete the steps in the following subsections to connect your cluster to AutoO Ensure your system meets the following requirements before proceeding: * Your cluster is on a [supported {{es}} version](https://www.elastic.co/support/eol). -* You have an [Enterprise self-managed license](https://www.elastic.co/subscriptions) or an active ECE, ECK, or self-managed [trial](https://cloud.elastic.co/registration). -* The agent you install for the connection is allowed to send metrics outside your organization to {{ecloud}}. +* Your cluster is on an [Enterprise self-managed license](https://www.elastic.co/subscriptions) or an active self-managed [trial](https://cloud.elastic.co/registration). +* The agent you install for the connection is allowed to send metrics to {{ecloud}}. ## Connect to AutoOps From f09bf2603b961ff22572f671ded0b28f7297edb4 Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Fri, 8 Aug 2025 14:17:51 -0400 Subject: [PATCH 5/6] clarifying self-managed --- deploy-manage/_snippets/autoops-cc-ech-faq.md | 2 +- .../_snippets/autoops-cc-payment-faq.md | 2 +- deploy-manage/cloud-connect.md | 6 +----- .../autoops/cc-autoops-as-cloud-connected.md | 8 ++++---- .../autoops/cc-cloud-connect-autoops-faq.md | 20 +++++++++---------- ...c-cloud-connect-autoops-troubleshooting.md | 6 +++--- .../cc-connect-self-managed-to-autoops.md | 16 +++++++-------- .../monitor/autoops/cc-manage-users.md | 4 ++-- 8 files changed, 30 insertions(+), 34 deletions(-) diff --git a/deploy-manage/_snippets/autoops-cc-ech-faq.md b/deploy-manage/_snippets/autoops-cc-ech-faq.md index 21c4c9bc36..8e0605bf60 100644 --- a/deploy-manage/_snippets/autoops-cc-ech-faq.md +++ b/deploy-manage/_snippets/autoops-cc-ech-faq.md @@ -1,4 +1,4 @@ :::{dropdown} Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps? -This path is not supported. Currently, we only support using Cloud Connect to connect self-managed clusters to AutoOps. +This path is not supported. Currently, we only support using Cloud Connect to connect ECE, ECK, and self-managed clusters to AutoOps. ::: \ No newline at end of file diff --git a/deploy-manage/_snippets/autoops-cc-payment-faq.md b/deploy-manage/_snippets/autoops-cc-payment-faq.md index 6ae6bc960b..68127729af 100644 --- a/deploy-manage/_snippets/autoops-cc-payment-faq.md +++ b/deploy-manage/_snippets/autoops-cc-payment-faq.md @@ -1 +1 @@ -Using [AutoOps for self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) through Cloud Connect is included with your [self-managed Enterprise license](https://www.elastic.co/subscriptions). \ No newline at end of file +Using [AutoOps for ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) through Cloud Connect is included with your [self-managed Enterprise license](https://www.elastic.co/subscriptions). \ No newline at end of file diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index c3ad8716b8..ee6c130b3d 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -9,7 +9,7 @@ navigation_title: Cloud Connect # Cloud Connect -Cloud Connect enables you to use {{ecloud}} services in your self-managed cluster without having to install and maintain their infrastructure yourself. In this way, you can get faster access to new features while significantly reducing your operational overhead. +Cloud Connect enables you to use {{ecloud}} services in your ECE, ECK, or self-managed cluster without having to install and maintain their infrastructure yourself. In this way, you can get faster access to new features while significantly reducing your operational overhead. AutoOps is the first service available for use with Cloud Connect. More services are coming soon. @@ -25,8 +25,6 @@ Find answers to your questions about Cloud Connect. :::{dropdown} Does using Cloud Connect require additional payment? -$$$cc-payment$$$ - Each cloud connected service has its own licensing and payment requirements. :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md @@ -39,8 +37,6 @@ Each cloud connected service has its own licensing and payment requirements. :::{dropdown} Are more services going to be available with Cloud Connect? -$$$cc-more-services$$$ - Yes. AutoOps is the first of many cloud connected services to come. The next planned service is the Elastic Inference Service (EIS), which will provide GPU-powered inference for use cases like semantic search and text embeddings. ::: diff --git a/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md b/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md index a68182d229..8e3a077bd1 100644 --- a/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md +++ b/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md @@ -9,15 +9,15 @@ navigation_title: AutoOps for self-managed clusters # AutoOps for self-managed clusters -Use [AutoOps](/deploy-manage/monitor/autoops.md) with your self-managed cluster through [Cloud Connect](/deploy-manage/cloud-connect.md). +Use [AutoOps](/deploy-manage/monitor/autoops.md) with your ECE ({{ece}}), ECK ({{eck}}), or self-managed clusters through [Cloud Connect](/deploy-manage/cloud-connect.md). -Cloud Connect enables users of self-managed clusters to use {{ecloud}} services. This means you can take advantage of the simplified cluster monitoring, real-time issue detection, and performance recommendations of AutoOps without having to run and manage the underlying infrastructure. +Cloud Connect enables users of ECE, ECK, and self-managed clusters to use {{ecloud}} services. This means you can take advantage of the simplified cluster monitoring, real-time issue detection, and performance recommendations of AutoOps without having to run and manage the underlying infrastructure. ## Section overview In this section, you'll find the following information: -* How to [connect your self-managed cluster to AutoOps](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) +* How to [connect your cluster to AutoOps](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) * How to [manage users of your connected clusters](/deploy-manage/monitor/autoops/cc-manage-users.md) -* [FAQs](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md) about AutoOps for self-managed clusters +* [FAQs](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md) about AutoOps for your clusters * A [troubleshooting guide](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md) to help you with any issues you may encounter \ No newline at end of file diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md index 97aaa1375b..c4623b7d39 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md @@ -9,21 +9,18 @@ navigation_title: FAQ # AutoOps for self-managed clusters FAQ -Find answers to your questions about AutoOps for self-managed clusters. +Find answers to your questions about AutoOps for ECE, ECK, and self-managed clusters. -:::{dropdown} Why should I use AutoOps for my self-managed clusters? +:::{dropdown} Why should I use AutoOps for my clusters? AutoOps simplifies the operation of your {{es}} clusters by providing real-time monitoring, performance insights, and issue detection. It helps you identify and resolve problems like ingestion bottlenecks and unbalanced shards, reducing manual effort and preventing performance issues. When you need support, AutoOps gives the Elastic team real-time visibility into your cluster, leading to faster resolutions. -Using AutoOps for your self-managed cluster lets you access all these features without the operational overhead of managing their infrastructure. +Using AutoOps for your ECE, ECK, and self-managed clusters lets you access all these capabilities without the operational overhead of managing their infrastructure. ::: -:::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md -::: - -:::{dropdown} Does AutoOps for self-managed clusters require additional payment? +:::{dropdown} Does this feature require additional payment? :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md ::: @@ -40,14 +37,17 @@ AutoOps is compatible with all [supported {{es}} versions](https://www.elastic.c You can connect to AutoOps on a standalone {{stack}}, ECE ({{ece}}), or ECK ({{eck}}) deployment. ::: -:::{dropdown} Can I use AutoOps for self-managed clusters if my environment is air-gapped? +:::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md +::: + +:::{dropdown} Can I use AutoOps for my clusters if my environment is air-gapped? Not at this time. AutoOps is currently only available as a cloud service and you need an internet connection to send metrics to {{ecloud}}. For air-gapped environments, we plan to offer a locally deployable version in the future. ::: -:::{dropdown} Can I use macOS to install {{agent}}? +:::{dropdown} Can I use macOS to install {{agent}} for this feature? -macOS is not a supported platform for installing {{agent}} and connecting your self-managed cluster to AutoOps. +macOS is not a supported platform for installing {{agent}} and connecting your clusters to AutoOps. ::: :::{dropdown} Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}? diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md index 164936ced7..612bbebac2 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md @@ -9,7 +9,7 @@ navigation_title: Troubleshooting # AutoOps for self-managed clusters troubleshooting -Learn about issues that might come up when using AutoOps with your self-managed cluster. +Learn about issues that might come up when connecting your clusters and using AutoOps. ## Troubleshoot issues @@ -27,7 +27,7 @@ Use this guide to troubleshoot any issues you may encounter. Refer to [](/solutions/security/configure-elastic-defend/uninstall-elastic-agent.md) for instructions. ::: -:::{dropdown} My self-managed cluster was disconnected from {{ecloud}} and I want to reconnect it. +:::{dropdown} My cluster was disconnected from {{ecloud}} and I want to reconnect it. If the cluster was disconnected by one of the users in your Cloud organization, you can repeat the [installation process](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) to reconnect. If not, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us). @@ -43,7 +43,7 @@ If an error appears on the screen, follow the suggestion in the error message an ## Potential errors -The following table shows the errors you might encounter if something goes wrong while you set up and use AutoOps for self-managed clusters. +The following table shows the errors you might encounter if something goes wrong while you set up and use AutoOps on your clusters. | Error code | Error message | Description | | :--- | :--- | :--- | 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 c3fd8519a0..78691bff3b 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 @@ -4,10 +4,10 @@ applies_to: self: ece: eck: -navigation_title: Connect your self-managed cluster +navigation_title: Connect your cluster --- -# Connect your self-managed cluster to AutoOps +# Connect your cluster to AutoOps To use AutoOps with your ECE, ECK, or self-managed cluster, you first need to create an {{ecloud}} account or log in to your existing account. An installation wizard will then guide you through the steps of installing {{agent}} to send metrics from your cluster to AutoOps in {{ecloud}}. @@ -94,7 +94,7 @@ Select one of the following methods to install {{agent}}: --> :::{important} -Using AutoOps for your self-managed cluster requires a new, dedicated {{agent}}. You must install an agent even if you already have an existing one for other purposes. +Using AutoOps for your ECE, ECK, and self-managed clusters requires a new, dedicated {{agent}}. You must install an agent even if you already have an existing one for other purposes. ::: ### Configure agent @@ -156,7 +156,7 @@ With this authentication method, you need to create an API key to grant access t With this authentication method, you need the username and password of a user with the necessary privileges to grant access to your cluster. There are two ways to set up a user with the these privileges: -* (Recommended) On your self-managed cluster, go to **Developer tools** from the navigation menu. In **Console**, run the following command: +* (Recommended) From your {{ecloud}} home page, select a deployment and go to **Developer tools**. In **Console**, run the following command: ```js POST /_security/role/autoops { @@ -218,7 +218,7 @@ The wizard will generate an installation command based on your configuration. De --> :::{tip} -To ensure optimum resource usage, we recommend installing the agent on a different machine from the one where your self-managed cluster is running. +To ensure optimum resource usage, we recommend installing the agent on a different machine from the one where your cluster is running. ::: Complete the following steps to run the command: @@ -257,7 +257,7 @@ Learn more about [AutoOps](/deploy-manage/monitor/autoops.md). ## Access AutoOps -After you've completed the setup, you can access AutoOps for your self-managed cluster at any time. +After you've completed the setup, you can access AutoOps for your cluster at any time. 1. Log in to [{{ecloud}}](https://cloud.elastic.co/home). 2. In the **Connected clusters** section, locate the cluster you want to work on. @@ -265,13 +265,13 @@ After you've completed the setup, you can access AutoOps for your self-managed c ## Connect additional clusters -To connect more self-managed clusters, we recommend repeating the steps to [connect to AutoOps](#connect-to-autoops). +To connect more clusters, we recommend repeating the steps to [connect to AutoOps](#connect-to-autoops). You can use the same installation command to connect multiple clusters, but each cluster needs a separate, dedicated {{agent}}. ## Disconnect a cluster -Complete the following steps to disconnect your self-managed cluster from your Cloud organization. You need the **Organization owner** [role](/deploy-manage/monitor/autoops/cc-manage-users.md#assign-roles) to perform this action. +Complete the following steps to disconnect your cluster from your Cloud organization. You need the **Organization owner** [role](/deploy-manage/monitor/autoops/cc-manage-users.md#assign-roles) to perform this action. 1. Log in to [{{ecloud}}](https://cloud.elastic.co/home). 2. In the **Connected clusters** section, locate the cluster you want to disconnect. diff --git a/deploy-manage/monitor/autoops/cc-manage-users.md b/deploy-manage/monitor/autoops/cc-manage-users.md index 1e4dd22fab..3cd358e979 100644 --- a/deploy-manage/monitor/autoops/cc-manage-users.md +++ b/deploy-manage/monitor/autoops/cc-manage-users.md @@ -18,7 +18,7 @@ Learn how to invite users to your {{ecloud}} organization and give them access t ::: ::: -To invite users to your organization and give them access to your self-managed cluster: +To invite users to your organization and give them access to your cluster: 1. Log in to [{{ecloud}}](https://cloud.elastic.co/home). 2. In the **Connected clusters** section, select a cluster. @@ -28,7 +28,7 @@ To invite users to your organization and give them access to your self-managed c To add multiple users, enter their email addresses separated by a space. 6. In the **Assign roles** section, enable **Connected cluster access**. -7. Set roles for the users on all or selected self-managed clusters so that they have the appropriate permissions when they accept the invitation and sign in to {{ecloud}}. +7. Set roles for the users on all or selected clusters so that they have the appropriate permissions when they accept the invitation and sign in to {{ecloud}}. Learn more about roles and their levels of access to AutoOps in [Assign roles](#assign-roles). 8. Click **Send invites**. From 888ddbf4f49b99f67cd3ddb35a402ef939ea9f0a Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Fri, 8 Aug 2025 14:19:20 -0400 Subject: [PATCH 6/6] fixing heading --- deploy-manage/cloud-connect.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index ee6c130b3d..0b4d4f6d74 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -13,7 +13,7 @@ Cloud Connect enables you to use {{ecloud}} services in your ECE, ECK, or self-m AutoOps is the first service available for use with Cloud Connect. More services are coming soon. -### AutoOps for self-managed clusters +### AutoOps [AutoOps](/deploy-manage/monitor/autoops.md) is a monitoring tool that helps you manage your cluster with real-time issue detection, performance recommendations, and resolution paths. By analyzing hundreds of {{es}} metrics, your configuration, and your usage patterns, AutoOps recommends operational and monitoring insights that deliver real savings in administration time and hardware cost.