3 Underrated Kubernetes Tools in AWS Every DevOps Engineer Should Know
Discover lesser-known Amazon EKS capabilities that can simplify Kubernetes operations, improve security, reduce costs, and make troubleshooting faster.
Series: Underrated Kubernetes Tools (2 articles)
- 13 Underrated Kubernetes Tools in AWS Every DevOps Engineer Should Know This article
Kubernetes has become a core technology for deploying and managing modern applications. On AWS, Amazon Elastic Kubernetes Service (Amazon EKS) simplifies Kubernetes control-plane management, but running production workloads still requires careful attention to security, networking, monitoring, scaling, and cost optimisation.
Most engineers are familiar with
kubectl, Helm, Prometheus, and Grafana. However, AWS offers several useful capabilities and tools that receive less attention in everyday Kubernetes workflows.In this article series, we explore seven underrated tools and features that can make operating Kubernetes on AWS more efficient.
1. kubectl ekslogs - Troubleshoot Nodes Without SSH
One of the most interesting tools for EKS operators is
kubectl ekslogs, particularly when using EKS Auto Mode.
Traditional node troubleshooting often involves SSH access, operating-system commands, and manually collecting logs. This approach can be difficult in environments where direct node access is restricted.
With
kubectl ekslogs, engineers can collect diagnostic log bundles from supported EKS nodes through Kubernetes APIs, without requiring SSH access. EKS Auto Mode includes the underlying node-diagnostic capabilities.1
kubectl ekslogs <node-name>
The collected diagnostics can help investigate operating-system issues, kernel messages, networking problems, and container runtime failures.
Why it is useful ?
- Reduces dependence on SSH access.
- Helps investigate node failures in restricted environments.
- Simplifies diagnostic collection for production incidents.
Best use cases are Production EKS environments where direct access to worker nodes is limited or unavailable.
Documentation: https://aws.amazon.com/blogs/containers/under-the-hood-how-amazon-eks-auto-mode-detects-repairs-and-diagnoses-node-failures/
2. Amazon EKS MCP Server - Use AI to Assist with Cluster Operations
The Amazon EKS Model Context Protocol (MCP) Server is a newer option for teams exploring AI-assisted Kubernetes operations.
It integrates EKS-specific context with compatible AI assistants, allowing engineers to interact with cluster information, AWS documentation, and operational workflows through natural-language interfaces.
Instead of manually searching documentation for every problem, an engineer might ask questions such as:
- Why is this Kubernetes deployment failing?
- What should I investigate when a pod cannot start?
- How should I troubleshoot an EKS configuration error?
The available operations depend on the integration, permissions, and supported tools.
Its usefull for
- Speeds up investigation and documentation lookup.
- Helps engineers unfamiliar with particular EKS features.
- Can reduce repetitive troubleshooting work.
You must Review those! AI-generated recommendations should be reviewed before applying changes to production. Use least-privilege IAM permissions and require appropriate approval for destructive operations.
3. EKS Capabilities - Reduce the Operational Burden of Platform Services
Many Kubernetes teams install and maintain several controllers inside their clusters. Depending on the architecture, these components can require upgrades, monitoring, scaling, and additional capacity.
Amazon EKS Capabilities offers managed options for selected platform functions.
Three notable capabilities are:
- AWS Controllers for Kubernetes (ACK) - Manage supported AWS resources using Kubernetes APIs.
- Argo CD - Manage application deployments through GitOps workflows.
- kro (Kube Resource Orchestrator) - Build reusable abstractions that combine Kubernetes and AWS resources.
For example, ACK can allow a team to manage supported AWS resources, such as S3 buckets or DynamoDB tables, using declarative Kubernetes resources.
This helps connect application deployment workflows with infrastructure management.
Why it is useful?
- to Reduces the burden of operating selected controllers.
- to Supports declarative infrastructure management.
- to Helps platform teams create standardized developer workflows.
These capabilities are optional, and pricing and permissions should be reviewed before adoption.
So.....
Managing Kubernetes on AWS involves more than deploying applications and running
kubectl commands. Engineers must also understand node diagnostics, operational automation, and platform management.Tools such as
kubectl ekslogs, the Amazon EKS MCP Server, and EKS Capabilities can help address operational challenges that are often overlooked.The key is to identify the biggest challenge in your environment, evaluate the available tools, and introduce them where they provide measurable value.
By understanding these capabilities, DevOps engineers can build more efficient, secure, and maintainable Kubernetes environments on AWS.
Series: Underrated Kubernetes Tools (2 articles)
- 13 Underrated Kubernetes Tools in AWS Every DevOps Engineer Should Know This article
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article