Amazon Elastic Kubernetes Service (EKS) - Utility Installation Troubleshooting steps
Amazon Elastic Kubernetes Service (EKS) - Utility Installation Troubleshooting Steps
This article provides troubleshooting steps to resolve AWS Kubernetes (EKS) monitoring failures that occur when data collection stops due to missing or inaccessible utilities (aws-cli or kubectl).
These issues commonly arise when prerequisite utilities are either not installed or installed by a user other than the Applications Manager service logon user.
Installation and Permission - Related Errors
Note: The following error messages apply only from Applications Manager v17.86.00 onwards.Error 1: AWS CLI Utility Not Found
Error Message: Data Collection has stopped.
Reason: The aws-cli utility is not found. Ensure that aws-cli is installed and accessible to the Applications Manager service logon user (<USERNAME>$), or start the Applications Manager with a user account that can access aws-cli.
Verify AWS CLI Installation
- Open Command Prompt (Windows) or Terminal (Linux).
- Run the following command:
aws --version. - Expected: AWS CLI version details appear.
- If AWS CLI is not installed, install it on an Applications Manager-installed machine (Windows or Linux). Learn more.
- If AWS CLI is installed, ensure it is accessible to the Applications Manager service logon user.
Screenshot:
Error 2: kubectl Utility Not Found
Scenario 1: kubectl Missing or Inaccessible (Path already set)
The default kubectl path exists in environment variables, but the utility itself is missing or unusable.
Error Message: Data Collection has stopped.
Reason: The kubectl utility is not found. Ensure that kubectl is installed and accessible to the Applications Manager service logon user.
Screenshot:
Scenario 2: kubectl Path Missing in Environment Variables
The kubectl is installed, but its installation directory is not added to the logon user’s environment variables.
Error Message: Data Collection has stopped.
Reason: The kubectl utility is not found. Ensure that kubectl is installed and accessible to the Applications Manager service logon user (<USERNAME>$). The default installation path %USERPROFILE%\.aws-kubectl is not set in the environment variable for the logon user.
Screenshot:
Verify kubectl Installation
- Open Command Prompt (Windows) or Terminal (Linux).
- Run the command:
kubectl version --client. - Expected: the kubectl client version is displayed.
- If the command is not recognized, kubectl is not installed.
- If kubectl is missing, install the compatible version
kubectl.exeas per the EKS prerequisite. Learn more. - If kubectl is installed, ensure it is accessible to the Applications Manager logon user. Refer to the Windows access troubleshooting steps below.
Troubleshooting Utility Access Issue (Windows)
Why does the issue occur?
Applications Manager running as a Windows service typically uses the Local System account.
If utilities (
If utilities (
aws-cli, kubectl) were installed by another user:- They are placed in user-specific directories.
- Their paths are added to that specific user’s environment variables.
- The Local System account cannot access these utilities → data collection fails.
How to fix this:
- Check the Logon User of Applications Manager
- Open Services (
services.msc). - Locate the service ManageEngine Applications Manager (or similar).
- Right-click → Properties → Log On tab.
- Note the account used (e.g., Local System, Administrator, or a domain user).
- Open Services (
- Ensure Logon User has access to Required Utilities
- Verify the user running Applications Manager has installed the required utilities (aws-cli, kubectl).
- If the logon user differs from the installer user, either:
- Change the Applications Manager service logon user (via Services) to a user who has access.
- Or log in as the Applications Manager logon user and install the required utilities.
Further Resources
New to ADSelfService Plus?
Related Articles
Azure Kubernetes Service (AKS) - Utility Installation Troubleshooting steps
Overview This KB provides troubleshooting steps to resolve Azure Kubernetes monitoring failures that occur when kubectl data collection fails due to missing or inaccessible utilities (azure-cli, kubectl, kubelogin). These issues typically occur when ...AWS EKS Troubleshooting FAQs
AWS EKS monitor can be configured only if you have already added an Amazon monitor in Applications Manager. Ensure that you have met the pre-requisites for the Amazon monitor before monitoring Elastic Kubernetes Service in Applications Manager. How ...Azure Kubernetes Service(AKS) Troubleshooting FAQs
Azure Kubernetes Service (AKS) monitor can be configured only if you have already added a Microsoft Azure monitor in Applications Manager. Ensure that you have met all the prerequisites for the Microsoft Azure monitor before monitoring Azure ...Absence of data in the Pods tab or some tabs in the Kubernetes monitor
This is a known issue in the older version of Applications Manager, which is fixed in APM v16800. So, we recommend upgrading the Applications Manager to the stable version to properly fix this issue. To collect data for the Kubernetes Monitor, ...Unable to Add Kubernetes Monitor
If you are having trouble adding a Kubernetes monitor in Applications Manager, ensure that the the prerequisites have been met: Verify whether you can establish an SSH connection to the Kubernetes server from the APM installed machine. Use the ...