If Container Insights data is not being populated:
- Verify if you have met all the pre-requisites by verifying using above method.
- Ensure whether amazon-cloudwatch pods are in the running state. If they are and if there's still no data in cloudwatch of AWS console, ensure that the CloudWatchAgentServerPolicy has been attached to the node (EC2 instance) in which the amazon-cloudwatch pods are running. For more info, click here.
Make sure container insights data is populated in cloudwatch console.
After clicking a resource, choose 1h and check if data is being collected for the cluster as shown in the below screenshot.
If you want to disable Proxy:
- In Applications manager, navigate to Admin > Product settings > Connectivity > Proxy server.
- First verify if Proxy server has been configured.
- If yes, to exclude kubectl from using proxy, navigate to EKS monitor page > Overview tab > Cluster information and get Cluster Endpoint information. Give the endpoint information in the Do not use proxy for addresses beginning with field without protocol(http/https)

Proxy is only supported from kubectl version 1.19 and above.
If you want to disable automatic alerts for a specific node condition
Disable the specific condition by navigating to Admin > Performance Polling > Optimize Data Collection > Elastic Kubernetes Service.

If a node is not in the ready state, its health will be automatically affected. If node is in ready state, then we will check the above node conditions and affect the node health based on the configuration.
Possible Errors in EKS Monitor and their troubleshooting
Unable to get data from 'eks:DescribeCluster' API (OR)
Access is denied for 'eks:DescribeCluster' API (OR)
Unable to collect data for <SERVICE_NAME>. Access denied for <API_NAME>.
- Ensure that you have met the pre-requisites to discover and monitor Elastic Kubernetes Service clusters in Applications Manager.
- Login to the AWS console and verify if the IAM user whose credentials used in Applications Manager has permission to the APIs in the pre-requisites.
- Check the user name in the EKS config map.
Data collection has stopped as kubectl is not installed. (OR)
Data collection has stopped as aws-cli is not installed.
- Ensure that you have followed and done all the pre-requisites.
- Verify if you have done the pre-requisites by performing steps mentioned above.
- Restart Applications Manager once and check if the environment changes are reflected in Applications Manager.
Data collection has stopped. Unable to connect to EKS cluster endpoint via kubectl.
If you are using a private EKS endpoint and you encounter this error, refer here to run kubectl commands using private endpoint access.
If you want to add access to kubernetes API server for a specific IP address alone, refer here.
Ensure that the DNS hostnames are enabled in VPC of the EKS Cluster. To enable DNS hostnames and DNS resolution, refer here.
Ensure if the security group's inbound policy is properly configured.
Data collection has stopped. The user is not authorized to fetch data via kubectl.
Ensure that the user whose credentials were used to add the EKS monitor has root permissions.
To resolve unauthorized error, refer here.
To add an IAM user to enable access to EKS cluster, refer here.
Timeout exceeded when executing kubectl command.
Increase the timeout value. (The default and minimum value for timeout is 30 seconds). To increase the value, go to EKS monitor page, monitor actions -> Edit monitor -> give the appropriate value and update.
Ensure your system has a stable network connectivity.
Run the following kubectl commands to get to know the approximate amount of time it takes to receive a response as these commands take.
kubectl get nodes
kubectl get pods --all-namespaces
Possible Errors in EKS Monitor and their troubleshooting
List of kubectl commands used in APM