elastic · wajihaparvez · Feb 2, 2026 · Jan 23, 2026 · Jan 26, 2026 · Jan 26, 2026
@@ -84,6 +84,24 @@ helm install eck-stack-with-apm-server elastic/eck-stack \
     --values https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{version.eck | M.M}}/deploy/eck-stack/examples/apm-server/basic.yaml -n elastic-stack
 ```
 
+## AutoOps along with {{es}} [k8s-install-autoops-elasticsearch-helm]
+
+```{applies_to}
+  eck: ga 3.3
+```
+
+Use the following code to connect your ECK-managed {{es}} clusters to [AutoOps](../../monitor/autoops.md) using Helm.
+
+```sh subs=true
+# Install an eck-managed {{es}} cluster and connect to AutoOps using custom values.
+helm install eck-stack-with-autoops elastic/eck-stack \
+    --values https://raw.githubusercontent.com/elastic/cloud-on-k8s/{{version.eck | M.M}}/deploy/eck-stack/examples/autoops/basic.yaml -n elastic-stack
+```
+
+The `eck-autoops-agent-policy` chart creates an `AutoOpsAgentPolicy` resource that connects your {{es}} clusters to AutoOps. The ECK operator handles the creation of API keys, agent configuration, and the deployment of {{agent}} required to send metrics to AutoOps.
+
+To connect to AutoOps using the installation wizard, refer to [](../../monitor/autoops/cc-connect-self-managed-to-autoops.md).
+
 ## Enterprise Search server along with {{es}} and {{kib}} [k8s-install-enterprise-search-elasticsearch-kibana-helm]
 
 Enterprise Search is not available in {{stack}} versions 9.0 and later. For an example deployment of {{es}} version 8.x, {{kib}} 8.x, and an 8.x Enterprise Search server using the Helm chart, refer to the [previous ECK documentation](https://www.elastic.co/guide/en/cloud-on-k8s/2.16/k8s-stack-helm-chart.html).

@@ -8,6 +8,7 @@ This content applies to {{eck_resources_list_short}} applications. To orchestrat
 
 The following guides provide specific instructions for deploying and configuring each application on ECK:
 * [APM Server](apm-server.md)
+* [AutoOps](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) {applies_to}`eck: ga 3.3`
 * [Standalone Elastic Agent](standalone-elastic-agent.md)
 * [{{fleet}}-managed {{agent}}](fleet-managed-elastic-agent.md)
 * [Elastic Maps Server](elastic-maps-server.md)

@@ -1,4 +1,3 @@
-:::{note}
 If your organization uses firewalls, you need to provide access to port 443 and allow the agent to send data to the following URLs:
 * `https://api.elastic-cloud.com`
 * `https://otel-auto-ops.${region}.${csp}.svc.elastic.cloud/`
@@ -7,5 +6,4 @@ If your organization uses firewalls, you need to provide access to port 443 and
 
     `https://otel-auto-ops.us-east-1.aws.svc.elastic.cloud/`
 
-Learn more about [defining an Elastic IP address](/deploy-manage/monitor/autoops/ec-autoops-faq.md#elastic-ip-address) for AutoOps for self-managed clusters.
-:::
+Learn more about [defining an Elastic IP address](/deploy-manage/monitor/autoops/ec-autoops-faq.md#elastic-ip-address) for AutoOps for ECE, ECK, or self-managed clusters.
@@ -12,7 +12,7 @@ products:
 
 # Disable certain types of data collection by AutoOps 
 
-AutoOps collects data from your self-managed cluster with the help of {{agent}} and analyzes it to diagnose issues and provide performance recommendations. 
+AutoOps collects data from your {{es}} cluster with the help of {{agent}} and analyzes it to diagnose issues and provide performance recommendations. 
 
 If you don't want the agent to access certain types of data, you can disable the collection of related metrics by editing your configuration file as described in the following section.
 

@@ -12,7 +12,7 @@ products:
 
 # Configure AutoOps {{agent}} with a custom SSL certificate 
 
-{{agent}} might not recognize your SSL certificate if it is signed by a custom or internal Certificate Authority (CA). In this case, {{agent}} will fail to connect your self-managed cluster to AutoOps and you might encounter an error like the following:
+{{agent}} might not recognize your SSL certificate if it is signed by a custom or internal Certificate Authority (CA). In this case, {{agent}} will fail to connect your ECE, ECK, or self-managed cluster to AutoOps and you might encounter an error like the following:
 
 ```sh
 ... x509: certificate signed by unknown authority ...
@@ -133,7 +133,7 @@ Complete the following steps:
 
 4. Save your changes to the `elastic-agent.yml` file.
 5. Restart {{agent}} for the new settings to take effect.
-6. Check the agent logs again to confirm that the error is gone and that {{agent}} has successfully connected your self-managed cluster to AutoOps. 
+6. Check the agent logs again to confirm that the error is gone and that {{agent}} has successfully connected your cluster to AutoOps. 
 
     :::{tip}
     If you encounter the following error in the agent logs, there might be a formatting issue in the `elastic-agent.yml` file.

@@ -0,0 +1,132 @@
+---
+applies_to:
+  deployment:
+    eck: ga 3.3
+navigation_title: Connected clusters not appearing with ECK
+products:
+  - id: cloud-kubernetes
+---
+
+# Troubleshoot connected clusters not appearing with ECK installation
+
+If you are using the ECK installation method (`AutoOpsAgentPolicy` resource) to connect your {{es}} clusters to AutoOps, but you can't view any connected clusters in your account, go through this guide to diagnose and fix common issues.
+
+## Verify `AutoOpsAgentPolicy` status
+
+Check if the `AutoOpsAgentPolicy` resource was successfully created and the ECK operator is processing it correctly.
+
+:::::{stepper}
+
+::::{step} Check if the policy was created
+Run the following command.
+```shell
+kubectl get autoopsagentpolicy <policy_name>
+```
+If the policy doesn't appear, there was an issue with its creation.
+
+If the policy appears, run the following command to check its status and any associated events.
+
+```shell
+kubectl describe autoopsagentpolicy <policy_name>
+```
+::::
+
+::::{step} Confirm the issue by checking logs
+Run the following command to show logs.
+```shell
+kubectl logs -f -n <ECK_operator_namespace> -l control-plane=elastic-operator
+```
+If the log contains any errors mentioning `AutoOpsAgentPolicy` or the policy's name, this confirms that the policy's creation and processing is causing the issue. 
+::::
+
+::::{step} Re-add the YAML manifest to your configuration file
+Repeat the steps to [install the agent](../autoops/cc-connect-self-managed-to-autoops.md#install-agent) with ECK as your installation method. This should resolve any issues with the policy.
+::::
+
+:::::
+
+## Verify that {{agent}} was deployed
+
+Check if `AutoOpsAgentPolicy` successfully deployed {{agent}} for your {{es}} clusters. 
+
+:::::{stepper}
+
+::::{step} List agent deployments
+Run the following command.
+```shell
+kubectl get deployments -l autoops.k8s.elastic.co/policy-name=<policy_name>
+```
+If no deployments appear, there might be an issue with the `resourceSelector` label applied to your {{es}} clusters. If deployments appear but pods are not running, there might be an issue with a specific pod.
+::::
+
+::::{step} Check cluster labels and agent pods 
+If no deployments appeared in the previous step, run the following command to check your cluster labels.   
+```shell
+kubectl get elasticsearch <elasticsearch_cluster_name> --show-labels
+```
+Make sure that the label you applied in the [Launch AutoOps](../autoops/cc-connect-self-managed-to-autoops.md#launch-autoops) step of the wizard appears correctly in the list.
+
+If deployments appeared in the previous step, run the following command to check pod status.
+```shell
+kubectl get pods -l autoops.k8s.elastic.co/policy-name=<policy_name>
+```
+
+If the status indicates that a pod is crashing or in a pending state, run the following command to inspect its events:
+```shell
+kubectl describe pod <agent_pod_name>
+```
+::::
+
+:::::
+
+## Validate connection secrets
+
+Make sure there are no errors in your secret keys.
+
+:::::{stepper}
+
+::::{step} Verify secret content
+Run the following command.
+```shell
+kubectl get secret <secret_name> -o yaml
+```
+Make sure the secret has the following required keys:
+* `autoops-token`
+* `autoops-otel-url`
+* `cloud-connected-mode-api-key`
+::::
+
+::::{step} Confirm secret reference
+Run the following command to confirm that `AutoOpsAgentPolicy` is actually referencing the correct configuration.
+```shell
+kubectl get autoopsagentpolicy <policy_name> -o jsonpath='{.spec.autoOpsRef.secretName}'
+```
+The command should return the correct `.spec.autoOpsRef.secretName`. 
+::::
+
+:::::
+
+## Check for authorization errors
+
+When you go through the installation wizard, the ECK operator attempts to create an API key for {{agent}} within {{es}}. If there is an issue with this creation, authorization errors will appear in the operator logs.
+:::::{stepper}
+
+::::{step} Pull operator logs
+Run the following command.
+```shell
+kubectl logs -f -n <ECK_operator_namespace> -l control-plane=elastic-operator
+```
+::::
+
+::::{step} Inspect logs
+If any errors in the logs mention "authorization" or "unauthorized connection", go through the installation wizard again so that the operator can reattempt creating a user or API key.
+::::
+
+## Ensure that {{agent}} is allowed to send data to AutoOps
+
+:::{include} ../_snippets/autoops-allowlist-port-and-urls.md
+:::
+
+## Check cluster health
+
+Ensure that the {{es}} clusters you are trying to connect to AutoOps are healthy. {{agent}} may fail to connect clusters in a Red state.
@@ -24,7 +24,7 @@ Ensure that you have allowed {{agent}} the required level of access. If the prob
 
 ## Test {{agent}}'s connection with your system
 
-There are [three main components](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md#how-your-self-managed-cluster-connects-to-autoops) of {{agent}}'s connection with your system:
+There are [three main components](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md#how-your-cluster-connects-to-autoops) of {{agent}}'s connection with your system:
 
 :::{include} /deploy-manage/monitor/_snippets/autoops-cc-components.md
 :::

@@ -4,27 +4,27 @@ applies_to:
     self:
     ece:
     eck:
-navigation_title: For self-managed clusters
+navigation_title: For ECE, ECK, and self-managed clusters
 products:
   - id: cloud-kubernetes
   - id: cloud-enterprise
 ---
 
-# AutoOps for self-managed clusters
+# AutoOps for ECE, ECK, and self-managed clusters
 
 For ECE ({{ece}}), ECK ({{eck}}), and self-managed {{es}} clusters, AutoOps can be set up through [Cloud Connect](/deploy-manage/cloud-connect.md).
 
 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.
 
-## How your self-managed cluster connects to AutoOps
+## How your cluster connects to AutoOps
 
 To connect your ECE, ECK, or self-managed cluster to AutoOps, you have to use your {{ecloud}} account to install {{agent}}. After that, the process can be broken down into three components:
 
 :::{include} /deploy-manage/monitor/_snippets/autoops-cc-components.md
 :::
 
 :::{image} /deploy-manage/images/self-managed-autoops-diagram.png
-:alt: Diagram depicting how AutoOps for self-managed clusters works
+:alt: Diagram depicting how AutoOps for ECE, ECK, and self-managed clusters works
 :::
 
 For instructions on how to get started, refer to [](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md).
@@ -35,11 +35,11 @@ After this setup is complete, you can start using AutoOps to monitor your cluste
 
 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 ECE, ECK, or self-managed cluster to AutoOps](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md)
 * How to [connect your local development cluster to AutoOps](/deploy-manage/monitor/autoops/cc-connect-local-dev-to-autoops.md)
 * How to [manage users of your connected clusters](/deploy-manage/monitor/autoops/cc-manage-users.md)
 * A [troubleshooting guide](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md) to help you with any issues you may encounter
 
 :::{tip}
-Refer to our [FAQ](/deploy-manage/monitor/autoops/ec-autoops-faq.md#questions-about-autoops-for-self-managed-clusters) for answers to frequently asked questions about AutoOps for self-managed clusters.
+Refer to our [FAQ](/deploy-manage/monitor/autoops/ec-autoops-faq.md#questions-about-autoops-for-ece-eck-or-self-managed-clusters) for answers to frequently asked questions about AutoOps for ECE, ECK, or self-managed clusters.
 :::
@@ -10,7 +10,7 @@ products:
   - id: cloud-enterprise
 ---
 
-# AutoOps for self-managed clusters troubleshooting
+# AutoOps for ECE, ECK, or self-managed clusters troubleshooting
 
 Learn about issues that might come up when connecting your clusters and using AutoOps.
 
@@ -24,6 +24,7 @@ Use this guide to troubleshoot any issues you may encounter.
 * [After running the installation command, I can't move on to the next steps.](#next-steps)
 * [My organization's firewall may be preventing {{agent}} from collecting and sending metrics.](#firewall)
 * [{{agent}} is failing to connect because it doesn't recognize my SSL certificate.](#custom-cert)
+* [I went through the wizard with {{ECK}} (ECK) as my installation method, but I can't view any connected clusters in my account.](#eck-no-clusters) {applies_to}`eck: ga 3.3`
 
 $$$single-cloud-org$$$**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
@@ -42,7 +43,10 @@ $$$firewall$$$**My organization's firewall may be preventing {{agent}} from coll
 :   If you're having issues with connecting your cluster to AutoOps and you suspect that a firewall may be the reason, refer to [](/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-firewalls.md).
 
 $$$custom-cert$$$**{{agent}} is failing to connect because it doesn't recognize my SSL certificate.**
-:   If {{agent}} is failing to connect your self-managed cluster to AutoOps because it doesn't recognize your SSL certificate, refer to [](/deploy-manage/monitor/autoops/autoops-sm-custom-certification.md). 
+:   If {{agent}} is failing to connect your cluster to AutoOps because it doesn't recognize your SSL certificate, refer to [](/deploy-manage/monitor/autoops/autoops-sm-custom-certification.md). 
+
+$$$eck-no-clusters$$$**I went through the wizard with {{ECK}} (ECK) as my installation method, but I can't view any connected clusters in my account.** {applies_to}`eck: ga 3.3`
+:   Refer to [](/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md) to diagnose and resolve common issues.
 
 ## Potential errors