FAQ
What's the difference between EKS Lens, Kubecost, and OpenCost?
While Kubecost and OpenCost provide valuable Kubernetes cost management capabilities, DoiT EKS Lens is specifically optimized for AWS environments, offering a more integrated approach to managing EKS costs and performance:
-
EKS Lens is designed with a deep understanding of AWS services and their integration with EKS, providing insights and analytics that are closely aligned with AWS billing and management practices.
-
EKS Lens focuses on EKS-specific metrics, offering detailed insights into cluster performance, cost allocation, and optimization opportunities within the AWS ecosystem.
-
EKS Lens leverages AWS-native services for enhanced security, compliance, and performance monitoring, ensuring a cohesive and secure environment for your EKS clusters.
-
With EKS Lens, you can easily customize dashboards and reports in the DoiT console, enabling effective cost management and optimization strategies.
The table below lists the main differences between DoiT EKS Lens, Amazon EKS optimized Kubecost custom bundle, and OpenCost.
| Feature | DoiT EKS Lens | Amazon EKS optimized Kubecost custom bundle | OpenCost |
|---|---|---|---|
| Description | A DoiT Cloud Analytics feature that provides comprehensive visibility into EKS spend. | A customized version of Kubecost by AWS, including a subset of commercial features. | A vendor-neutral open-source project for measuring and allocating cloud infrastructure and container costs in real time. |
| Number of clusters | Unlimited (unified multi-cluster view) | Unlimited (unified multi-cluster view) | Unlimited (no unified view) |
| Number of labels for pods | Unlimited | Unlimited | Unlimited |
| EKS on Fargate | Limited support (for Amazon EKS on Fargate, DoiT Cloud Analytics uses metrics from AWS billing data but not metrics generated by kube-state-metrics). | Kubecost tracks costs for Amazon EKS on Fargate with lower accuracy than with EKS on EC2. | No support for Amazon EKS on Fargate. |
| Deployment |
| Deployed using Helm. Bundled with Prometheus and Grafana dependencies. | Deployed as a pod. Prometheus and kube-state-metrics dependencies are managed separately.Also provides a community-supported Helm chart. |
| Metrics retention | Subject to your contract with DoiT. | Unlimited historical data for database retention; 15 days for the Kubecost API retention (ETL). | Limited by Prometheus environment. |
| Cloud billing integration | Custom pricing support for AWS (including multiple clusters and multiple accounts). | Custom pricing support for AWS (including multiple clusters and multiple accounts). | Core billing integrations with AWS EKS. |
| Support | Subject to your contract with DoiT. | Subject to your AWS support agreements. | Built and supported by community users. |
-
AWS Documentation: Cost monitoring: Frequently asked questions
-
OpenCost Documentation: FAQ: What's the difference between OpenCost and Kubecost?
-
Kubecost Documentation: OpenCost Product Comparison
There is no quick link to "connect your EKS clusters".
DoiT uses the AWS-generated cost allocation tag eks:cluster-name to identify EKS EC2 instances. Make sure your clusters are tagged correctly in the AWS billing data. See Activating AWS-generated tags cost allocation tags and AWS cost allocation tags in DoiT platform.
In addition, the DoiT platform scans the billing data on a daily basis. If your clusters are newly created (within 72 hours) or have no spend, then the DoiT platform will not be able to detect them.