diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md new file mode 100644 index 0000000000..7e28ab70d1 --- /dev/null +++ b/deploy-manage/cloud-connect.md @@ -0,0 +1,57 @@ +--- +applies_to: + deployment: + self: + ece: + eck: +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 is included with your [self-managed Enterprise license](https://www.elastic.co/subscriptions) and works with self-managed free trials for the duration of the trial period. + +AutoOps is the first service available for use with Cloud Connect. More services are coming soon. + +### 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 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). + +## FAQs + +Find answers to your questions about Cloud Connect. + +:::{dropdown} Does using Cloud Connect require additional payment? + +$$$cc-payment$$$ + +No. Cloud Connect is included with your [self-managed Enterprise license](https://www.elastic.co/subscriptions) and works with self-managed free trials for the duration of the trial period. + +However, you may incur additional costs for specific functions within a cloud connected service. For example, when sending metrics data from your cluster in a CSP region to AutoOps in {{ecloud}}, shipping costs will be determined by your agreement with that CSP. +::: + +:::{dropdown} Does using Cloud Connect consume ECU? + +$$$cc-ecu$$$ + +No. The currently available functionality does not consume ECU, but this may change when more features are introduced. +::: + +:::{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? + +$$$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/_snippets/disconnect-cluster.md b/deploy-manage/monitor/_snippets/disconnect-cluster.md new file mode 100644 index 0000000000..1aef079105 --- /dev/null +++ b/deploy-manage/monitor/_snippets/disconnect-cluster.md @@ -0,0 +1,3 @@ +:::{warning} +If you disconnect a cluster, its connection to your {{ecloud}} account will end and all metrics and AutoOps data will be permanently deleted. +::: \ No newline at end of file diff --git a/deploy-manage/monitor/_snippets/single-cloud-org.md b/deploy-manage/monitor/_snippets/single-cloud-org.md new file mode 100644 index 0000000000..edc4dfddfb --- /dev/null +++ b/deploy-manage/monitor/_snippets/single-cloud-org.md @@ -0,0 +1 @@ +Users can only belong to one {{ecloud}} organization at a time. If you want to create or join another organization, you must [leave the previous one](/cloud-account/join-or-leave-an-organization.md#ec-leave-organization) or use a different email address. \ No newline at end of file diff --git a/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md b/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md new file mode 100644 index 0000000000..a68182d229 --- /dev/null +++ b/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md @@ -0,0 +1,23 @@ +--- +applies_to: + deployment: + self: + ece: + eck: +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). + +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. + +## 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 [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 +* 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 new file mode 100644 index 0000000000..81c962c287 --- /dev/null +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md @@ -0,0 +1,72 @@ +--- +applies_to: + deployment: + self: + ece: + eck: +navigation_title: FAQ +--- + +# AutoOps for self-managed clusters FAQ + +Find answers to your questions about AutoOps for self-managed clusters. + +:::{dropdown} Why should I use AutoOps for my self-managed cluster? + +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. +::: + +:::{dropdown} Which versions of {{es}} does AutoOps support? + +AutoOps is compatible with all [supported {{es}} versions](https://www.elastic.co/support/eol). +::: + +:::{dropdown} Which deployment types can be connected to AutoOps? + +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? + +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} 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. + +To enable IP ranges, {{ecloud}} offers a selection of static IP addresses. All traffic directed to {{ecloud}} deployments, whether originating from the public internet, your private cloud network through the public internet, or your on-premise network through the public internet utilizes Ingress Static IPs as the network destination. + +For more information, refer to [](/deploy-manage/security/elastic-cloud-static-ips.md). +::: + +:::{dropdown} Where are AutoOps metrics stored, and does it cost extra to ship metrics to {{ecloud}}? + +You can choose the CSP and region in which your cluster metrics will be stored from a list of [available regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md). + +Shipping metrics to {{ecloud}} may come at an additional cost. For example, when sending metrics data from your cluster in a CSP region to {{ecloud}}, shipping costs will be determined by your agreement with that CSP. +::: + +:::{dropdown} What information does {{agent}} extract from my cluster? + +{{agent}} only extracts and sends cluster metrics to {{ecloud}}, not the underlying data within your cluster. The following metrics are collected: + +| API | Description | Collected data | +| --- | --- | --- | +| [_cat/shards](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-shards) | Returns detailed information about the shards within the cluster | Shard states, node allocation, index names, sizes, and replica information | +| [_nodes/stats](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats) | Retrieves statistics from cluster nodes including JVM, OS, process, and transport metrics | CPU usage, memory utilization, thread pools, file system stats | +| [_cluster/settings](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-settings) | Returns the settings configured for the cluster | Persistent and transient settings such as cluster-wide configurations | +| [_cluster/health](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-health) | Provides information about the overall health of the cluster | Status (green/yellow/red), number of nodes, number of shards | +| [_cat/template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-templates) | Lists all index templates in the cluster | Template names, patterns, and basic settings | +| [_index_template](/manage-data/data-store/templates.md) | Retrieves composable index templates | Index settings, mappings, and aliases | +| [_component_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-component-template) | Fetches component templates used for building index templates | Metadata for re-usable mappings and settings | +| [_tasks](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-tasks) | Displays information about currently running tasks on the cluster | Task descriptions, start times, running nodes, and execution details | +| [_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get-template) | Retrieves legacy index templates | Similar to composable index templates but in older format | +| [_resolve/index/*](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-index) | Resolves index, data stream, and alias names to their current definitions | Mappings between names and underlying data objects | +::: + + diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md new file mode 100644 index 0000000000..c250ab4460 --- /dev/null +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md @@ -0,0 +1,60 @@ +--- +applies_to: + deployment: + self: + ece: + eck: +navigation_title: Troubleshooting +--- + +# AutoOps for self-managed clusters troubleshooting + +Learn about issues that might come up when using AutoOps with your self-managed cluster. + +## Troubleshoot issues + +Use this guide to troubleshoot any issues you may encounter. + +:::{dropdown} I’m trying to create a Cloud organization, but I’m already part of a different one. + +:::{include} /deploy-manage/monitor/_snippets/single-cloud-org.md +::: + +::: + +:::{dropdown} I need to uninstall {{agent}}. + +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. + +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). + +:::{include} /deploy-manage/monitor/_snippets/disconnect-cluster.md +::: + +::: + +:::{dropdown} After running the installation command, I can't move on to the next steps. + +If an error appears on the screen, follow the suggestion in the error message and try to run the command again. If the issue is not resolved, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us). +::: + +## 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. + +| Error code | Error message | Description | +| :--- | :--- | :--- | +| `HTTP_401` | Authentication failed | Connection denied because of an authentication error. Verify that your API key and password are correct and all [necessary privileges](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#configure-agent) have been granted. | +| `HTTP_502` | Server error | Received an invalid response from the server. Verify the server status and network configuration. | +| `HTTP_503` | Server unavailable | Invalid or corrupt response received from the server. The server acting as a proxy may be busy or undergoing scheduled maintenance. If the issue persists, check the cluster's health and resource usage. | +| `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. | +| `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. | +| `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 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 new file mode 100644 index 0000000000..5dc430f652 --- /dev/null +++ b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md @@ -0,0 +1,218 @@ +--- +applies_to: + deployment: + self: + ece: + eck: +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}}. + +Complete the steps in the following subsections to connect your cluster to AutoOps. The connection process takes about 10 minutes. + +## Prerequisites + +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). +* The agent you install for the connection is allowed to send metrics outside your organization to {{ecloud}}. + +## Connect to AutoOps + +:::{note} +:::{include} /deploy-manage/monitor/_snippets/single-cloud-org.md +::: +::: + +:::::{tab-set} +:group: existing-or-new-cloud-account + +::::{tab-item} Existing account +:sync: existing + +If you already have an {{ecloud}} account: +1. Log in to [{{ecloud}}](https://cloud.elastic.co?page=docs&placement=docs-body). +2. On your home page, in the **Connected clusters** section, select **Connect self-managed cluster**. +3. On the **Connected clusters** page, select **Accept and continue**. This button only appears the first time you connect a cluster. +4. On the **Connect your self-managed cluster** page, in the **AutoOps** section, select **Connect**. +:::: + +::::{tab-item} New account +:sync: new + +If you don’t have an existing {{ecloud}} account: +1. Sign up for an account. + +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 + +This is the first step of the installation wizard. Your cluster ships metrics to AutoOps with the help of {{agent}}. + +Select one of the following methods to install {{agent}}: + +* Kubernetes +* Docker +* Linux +* Windows + +:::{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. +::: + +### Configure agent + +Depending on your selected installation method, you may have to provide the following information to create the installation command: + +* **{{es}} endpoint URL**: The agent will use this URL to identify which cluster you want to connect to AutoOps. +* **Preferred authentication method**: Choose one of the following: +:::::{tab-set} +:group: api-key-or-basic + +::::{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: + +| Setting | Privileges | + | --- | --- | + | Cluster privileges | `monitor`, `read_ilm`, and `read_slm` | + | Index privileges | Indices: `*`
`monitor`, `view_index_metadata`, `allow_restricted_indices: true` | + +:::: + +::::{tab-item} Basic +:sync: 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) On your self-managed cluster, go to **Developer tools** from the navigation menu. 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 {{agent}} to access restricted indices. +::: +:::: + +::::: +* **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 cloud service providers and regions. + +### Install agent + +The wizard will generate an installation command based on your configuration. Depending on your installation method, the following command formats are available: + +* Kubernetes + * YAML + * Helm Chart +* Docker + * Docker + * Docker compose +* Linux +* Windows + +:::{tip} +We recommend installing the agent on a separate machine from the one where your self-managed cluster is running. +::: + +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 {{ecloud}} URL to which {{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 {{agent}} uses to communicate with {{es}}. | +| `ELASTICSEARCH_READ_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 `ELASTICSEARCH_READ_USERNAME` and `ELASTICSEARCH_READ_PASSWORD`. | +| `ELASTICSEARCH_READ_USERNAME` | The username for basic authentication to access the cluster.
This variable should be used with `ELASTICSEARCH_READ_PASSWORD`. | +| `ELASTICSEARCH_READ_PASSWORD` | The password for basic authentication to access the cluster.
This variable should be used with `ELASTICSEARCH_READ_USERNAME`. | +| `ELASTIC_CLOUD_CONNECTED_MODE_API_KEY` | The {{ecloud}} 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. | + +4. Run the command from the machine where you want to install the agent. +5. 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 will appear with a possible reason for the failure and recommended next steps. For a list of these errors, refer to [Potential errors](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md#potential-errors). + +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). + +### 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. + +After the account is ready, the **Open AutoOps** button will appear in the wizard. Select it to launch AutoOps. + +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. + +1. Log in to [{{ecloud}}](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**. + +## Connect additional clusters + +To connect more self-managed 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. + +1. Log in to [{{ecloud}}](https://cloud.elastic.co/home). +2. In the **Connected clusters** section, locate the cluster you want to disconnect. +3. From that cluster’s actions menu, select **Disconnect cluster**. +4. Enter the cluster’s name in the field that appears and then select **Disconnect cluster**. + +:::{include} /deploy-manage/monitor/_snippets/disconnect-cluster.md +::: \ No newline at end of file diff --git a/deploy-manage/monitor/autoops/cc-manage-users.md b/deploy-manage/monitor/autoops/cc-manage-users.md new file mode 100644 index 0000000000..1e4dd22fab --- /dev/null +++ b/deploy-manage/monitor/autoops/cc-manage-users.md @@ -0,0 +1,47 @@ +--- +applies_to: + deployment: + self: + ece: + eck: +navigation_title: Manage connected cluster users +--- + +# Manage connected cluster users + +Learn how to invite users to your {{ecloud}} organization and give them access to AutoOps on your connected clusters. + +## Invite users + +:::{note} +:::{include} /deploy-manage/monitor/_snippets/single-cloud-org.md +::: +::: + +To invite users to your organization and give them access to your self-managed cluster: + +1. Log in to [{{ecloud}}](https://cloud.elastic.co/home). +2. In the **Connected clusters** section, select a cluster. +3. From the lower navigation menu, select **Organization**. +4. On the **Members** page, click **Invite members**. +5. Enter the email address of the user you want to invite. + + 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}}. + + Learn more about roles and their levels of access to AutoOps in [Assign roles](#assign-roles). +8. Click **Send invites**. + + Invitations to join an organization are sent by email. Invited users have 72 hours to accept the invitation before it expires. If an invitation expires, an admin can resend it. + +You can also [manage existing users](/deploy-manage/users-roles/cloud-organization/manage-users.md#manage-existing-users) and [manage users through the {{ecloud}} API](/deploy-manage/users-roles/cloud-organization/manage-users.md#ec-api-organizations). + +## Assign roles + +Assign the following roles to new or existing users based on levels of access to AutoOps: + +| Role | Allowed actions in AutoOps | +| --- | --- | +| **Organization owner** | View events and metrics reports
Add or edit customizations and notification preferences
Connect and disconnect clusters | +| **Connected cluster access** | **Viewer**:
View events and metrics reports

**Admin** for all connected clusters:
View events and metrics reports
Add or edit customizations and notification preferences
Connect and disconnect clusters

**Admin** for selected clusters:
View events and metrics reports
Add or edit customizations and notification preferences
Connect clusters | diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index c306185665..3f95b8dd37 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -653,6 +653,7 @@ toc: - file: remote-clusters/remote-clusters-migrate.md - file: remote-clusters/remote-clusters-settings.md - file: remote-clusters/eck-remote-clusters.md + - hidden: cloud-connect.md - file: monitor.md children: - file: monitor/autoops.md @@ -672,6 +673,11 @@ toc: - file: monitor/autoops/ec-autoops-dismiss-event.md - file: monitor/autoops/ec-autoops-regions.md - file: monitor/autoops/ec-autoops-faq.md + - hidden: monitor/autoops/cc-autoops-as-cloud-connected.md + - hidden: monitor/autoops/cc-connect-self-managed-to-autoops.md + - hidden: monitor/autoops/cc-manage-users.md + - hidden: monitor/autoops/cc-cloud-connect-autoops-faq.md + - hidden: monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md - file: monitor/stack-monitoring.md children: - file: monitor/stack-monitoring/ece-ech-stack-monitoring.md