---
title: Connect your self-managed cluster to AutoOps
description: To use AutoOps with your ECE, ECK, or self-managed cluster, you first need to create an Elastic Cloud account or log in to your existing account. An installation...
url: https://www.elastic.co/elastic/docs-builder/assembled-docs/2379/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud on Kubernetes
---

# Connect your self-managed cluster to AutoOps
To use AutoOps with your ECE, ECK, or self-managed cluster, you first need to create an Elastic Cloud account or log in to your existing account. An installation wizard then guides you through the steps of installing Elastic Agent to send metrics from your cluster to AutoOps in Elastic Cloud.
Complete the steps in the following subsections to connect your cluster to AutoOps. The connection process takes about 10 minutes.
<note>
  If you have an Elasticsearch cluster set up for local development or testing, you can connect it to AutoOps using Docker. Refer to [Connect your local development cluster to AutoOps](https://www.elastic.co/elastic/docs-builder/assembled-docs/2379/deploy-manage/monitor/autoops/cc-connect-local-dev-to-autoops).
</note>


## Prerequisites

Ensure your system meets the following requirements before proceeding:
- Your cluster is on a [supported Elasticsearch version](https://www.elastic.co/support/eol) (7.17.x and above).
- 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 Elastic Cloud.


## Connect to AutoOps

<note>
  Users can only belong to one Elastic Cloud organization at a time. If you want to create or join another organization, you must [leave the previous one](/elastic/docs-builder/assembled-docs/2379/cloud-account/join-or-leave-an-organization#ec-leave-organization) or use a different email address.
</note>

The following steps describe how to connect your ECE, ECK, or self-managed cluster to AutoOps.
<tab-set>
  <tab-item title="Existing account">
    If you already have an Elastic Cloud account:
    1. Log in to [Elastic Cloud](https://cloud.elastic.co/login?redirectTo=%2Fconnect-cluster-services).
       - The link provided should take you directly to the **Connect your self-managed cluster** page
    2. On your home page, in the **Connected clusters** section, select **Connect self-managed cluster**.
    3. On the **Connect your self-managed cluster** page, in the **AutoOps** section, select **Connect**.
    4. Go through the installation wizard as detailed in the following sections.
  </tab-item>

  <tab-item title="New account">
    If you don’t have an existing Elastic Cloud account:
    1. Go to the [Cloud Connected Services sign up](https://cloud.elastic.co/registration?onboarding_service_type=ccm) page.
    2. Follow the prompts on your screen to sign up for Elastic Cloud and create an organization.
    3. Go through the installation wizard as detailed in the following sections.
  </tab-item>
</tab-set>


### Select installation method

This is the first step of the installation wizard. Your cluster ships metrics to AutoOps with the help of Elastic Agent.
Select one of the following methods to install Elastic Agent:
- **Kubernetes**
- **Docker**
- **Linux**

<note>
  macOS is not a supported platform for installing Elastic Agent to connect to AutoOps in a self-managed production environment. However, you can use macOS to [connect your local development cluster to AutoOps](https://www.elastic.co/elastic/docs-builder/assembled-docs/2379/deploy-manage/monitor/autoops/cc-connect-local-dev-to-autoops).
</note>

<important>
  Using AutoOps for your ECE, ECK, and self-managed clusters requires a new, dedicated Elastic Agent. You must install an agent even if you already have an existing one for other purposes.
</important>

To learn more about how AutoOps securely gathers data from your cluster, refer to our [FAQ](/elastic/docs-builder/assembled-docs/2379/deploy-manage/monitor/autoops/ec-autoops-faq#data-gathering).

### Configure agent

Depending on your selected installation method, you may have to provide the following information to create the installation command:
- **Elasticsearch endpoint URL**: Enter the URL for the Elasticsearch cluster you want to monitor by connecting to AutoOps.
- **Preferred authentication method**: Choose one of the following:

<tab-set>
  <tab-item title="API key">
    With this authentication method, you need to create an API key to grant access to your cluster. Complete the following steps:
    1. Go to Kibana in your self-managed cluster.
    2. Go to the **API keys** management page in the navigation menu or use the [global search field](https://www.elastic.co/elastic/docs-builder/assembled-docs/2379/explore-analyze/find-and-organize/find-apps-and-objects).
    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": {
       "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
       }
     }
    }
    ```

    1. Select **Create API key**.
    2. Copy the key and save it for later. You will need it when you [install the agent](#install-agent).
  </tab-item>

  <tab-item title="Basic">
    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) Go to Kibana in your self-managed cluster and then go to **Developer tools**. In **Console**, run the following command:

    ```js
    POST /_security/role/autoops
    {
      "cluster": [
        "monitor",
        "read_ilm",
        "read_slm"
      ],
      "indices": [
        {
          "names": [
            "*"
          ],
          "privileges": [
            "monitor",
            "view_index_metadata"
          ],
          "allow_restricted_indices": true
        }
      ],
      "applications": [],
      "run_as": [],
      "metadata": {
        "description": "Allows Elastic agent to pull cluster metrics for AutoOps."
      },
      "transient_metadata": {
        "enabled": true
      }
    }
    ```

    - Alternatively, manually assign the following privileges in your account:
      | Setting            | Privileges                                     |
      |--------------------|------------------------------------------------|
      | Cluster privileges | `monitor`, `read_ilm`, and `read_slm`          |
      | Index privileges   | Indices: `*`  `monitor`, `view_index_metadata` |

    <note>
      If you manually assign privileges, you won't be able to allow Elastic Agent to access restricted indices.
    </note>
  </tab-item>
</tab-set>

- **System architecture**: Select the system architecture of the machine running the agent.
- **Metrics storage location**: Select where to store your metrics data from the list of available AWS regions:
  | Region         | Name                     |
  |----------------|--------------------------|
  | us-east-1      | US East (N. Virginia)    |
  | us-east-2      | US East (Ohio)           |
  | us-west-2      | US West (Oregon)         |
  | eu-west-1      | EU (Ireland)             |
  | eu-west-2      | Europe (London)          |
  | eu-central-1   | Europe (Frankfurt)       |
  | ap-northeast-1 | Asia Pacific (Tokyo)     |
  | ap-southeast-1 | Asia Pacific (Singapore) |

  More regions are coming soon.


### Install agent

The wizard generates an installation command based on your configuration. Depending on your installation method, the following command formats are available:
- Kubernetes
  - YAML
  
- Docker
  - Docker
- Docker compose
- Linux

<tip>
  To ensure optimum resource usage, we recommend installing the agent on a different machine from the one where your cluster is running.
</tip>

Complete the following steps to run the command:
1. Copy the command.
2. Paste it into a text editor and update the placeholder values in the following environment variables:
   | Environment variable                   | Description                                                                                                                                                                                     |
   |----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
   | `AUTOOPS_OTEL_URL`                     | The Elastic Cloud URL to which Elastic Agent ships data. The URL is generated based on the CSP and region you pick.  This URL shouldn't be edited.                                              |
   | `AUTOOPS_ES_URL`                       | The URL Elastic Agent uses to communicate with Elasticsearch.                                                                                                                                   |
   | `AUTOOPS_ES_API_KEY`                   | The API key for API key authentication to access the cluster. It combines the `${id}:${api_key}` values.  This variable shouldn't be used with `AUTOOPS_ES_USERNAME` and `AUTOOPS_ES_PASSWORD`. |
   | `AUTOOPS_ES_USERNAME`                  | The username for basic authentication to access the cluster.  This variable should be used with `AUTOOPS_ES_PASSWORD`.                                                                          |
   | `AUTOOPS_ES_PASSWORD`                  | The password for basic authentication to access the cluster.  This variable should be used with `AUTOOPS_ES_USERNAME`.                                                                          |
   | `ELASTIC_CLOUD_CONNECTED_MODE_API_KEY` | The Elastic Cloud API Key used to register the cluster.  This key shouldn't be edited.                                                                                                          |
   | `AUTOOPS_TEMP_RESOURCE_ID`             | The temporary ID for the current installation wizard.                                                                                                                                           |
3. Run the command from the machine where you want to install the agent.
4. Return to the wizard and select **I have run the command**.

It might take a few minutes for your cluster details to be validated and the first metrics to be shipped to AutoOps.
If the connection is unsuccessful, an error message is displayed with a possible reason for the failure and recommended next steps. For a list of these errors, refer to [Potential errors](/elastic/docs-builder/assembled-docs/2379/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting#potential-errors).
Sometimes, an exact reason for the failure cannot be determined. In this case, explore [additional resources](/elastic/docs-builder/assembled-docs/2379/troubleshoot#troubleshoot-additional-resources) or [contact us](/elastic/docs-builder/assembled-docs/2379/troubleshoot#contact-us).
To uninstall the agent, refer to [Uninstall Elastic Agent](https://www.elastic.co/elastic/docs-builder/assembled-docs/2379/solutions/security/configure-elastic-defend/uninstall-elastic-agent).

### Launch AutoOps

If the connection is successful, AutoOps starts analyzing your metrics and reporting on any issues found. Depending on the size of your cluster, this process can take up to 30 minutes.
After the account is ready, the **Open AutoOps** button is displayed in the wizard. Select it to launch AutoOps.
Learn more about [AutoOps](https://www.elastic.co/elastic/docs-builder/assembled-docs/2379/deploy-manage/monitor/autoops).

## Access AutoOps

After completing the setup, you can access AutoOps for your cluster at any time.
1. Log in to [Elastic Cloud](https://cloud.elastic.co/home).
2. In the **Connected clusters** section, locate the cluster you want to work on.
3. In the **Services** column, select **AutoOps**.


## Manage connected clusters

Perform the actions described in the following sections to manage your connected cluster(s).

### Add an alias to a cluster

By default, each cluster has a name made up of a string of characters, but you can add a human-readable alias by completing the following steps. You need admin privileges to perform this action.
1. From the [Elastic Cloud home page](https://cloud.elastic.co/home), go to the **Connected clusters** section and select the cluster you want to work on.
2. On the cluster details page, select **Edit** in the **Cluster display name** field.
3. Enter the alias in the field that is displayed and then select the checkmark icon.


### Connect additional clusters

To connect more clusters, repeat 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 Elastic Agent.

### Disconnect a cluster

Complete the following steps to disconnect your cluster from your Cloud organization. You need the **Organization owner** [role](/elastic/docs-builder/assembled-docs/2379/deploy-manage/monitor/autoops/cc-manage-users#assign-roles) to perform this action.
1. Based on your [installation method](#select-installation-method), complete the steps to stop Elastic Agent from shipping metrics to Elastic Cloud.
2. Log in to [Elastic Cloud](https://cloud.elastic.co/home).
3. On the **Connected clusters** page or the **Connected clusters** section of the home page, locate the cluster you want to disconnect.
4. From that cluster’s actions menu, select **Disconnect cluster**.
5. Enter the cluster’s name in the field that is displayed and then select **Disconnect cluster**.

<warning>
  If you disconnect a cluster, its connection to your Elastic Cloud account will end and all metrics and AutoOps data will be permanently deleted.
</warning>