DEV Community

OpenLens Cannot Connect to AWS EKS Cluster: executable aws not found

The user is trying to connect to a remote AWS EKS cluster using OpenLens, but is encountering connection issues. AWS SSO is successfully configured, and terminal access to the cluster functions correctly. OpenLens, however, fails to connect and throws an "executable aws not found" error. This error suggests that OpenLens cannot find the AWS CLI executable during credential retrieval. The problem is due to the AWS CLI not being discoverable by OpenLens, even though it's installed and accessible via terminal. The provided solution involves verifying the AWS CLI installation. The user needs to add the AWS CLI to the system's PATH environment variable. Specifically, the path should be made globally available for OpenLens to find it. For Apple Silicon macOS devices, a symbolic link may be required. Alternatively, the user can hardcode the full path to the AWS CLI in the kubeconfig file. By modifying the kubeconfig, OpenLens will know exactly where to find the AWS CLI. Restarting OpenLens after either fix ensures the changes take effect. Implementing either of these fixes should resolve the connection error. This ultimately enables seamless connection to the remote AWS EKS cluster through OpenLens.
favicon
dev.to
dev.to