Skip to main content

Analyze EKS costs

DoiT Cloud Analytics integrates EKS cluster metrics with AWS billing data. It allows you to break down EKS costs by Kubernetes resources and other Dimensions and labels supported in the DoiT platform.

Components of EKS costs​

When analyzing EKS costs, it's important to understand that with Amazon EKS, you pay separately for the EKS service and any AWS resources your workloads use.

  • EKS service costs: Amazon EKS pricing includes per cluster pricing based on Kubernetes cluster version support, pricing for Amazon EKS Auto Mode, and per vCPU pricing for Amazon EKS Hybrid Nodes.

  • Resource costs: You pay separately for the resources you use to run your applications on Kubernetes worker nodes. For example, if your EKS cluster uses EC2 instances, you will be billed according to EC2 pricing. The same applies to EBS volumes (storage) and data transfer (networking) costs.

Note that the OpenTelemetry agent in the EKS cost monitoring solution does not collect storage and networking metrics for your workloads. This means that, in the current implementation of EKS Lens, it is not possible to split storage or networking costs.

EKS labels​

EKS labels are assigned at the Pods level. You can use EKS labels to track Kubernetes resources usage, analyze project cost, and identify cost optimization opportunities.

In the DoiT Cloud Analytics Reports, EKS labels are grouped under the EKS Labels section, which consists of two categories:

  • Kubernetes metadata: Data that helps uniquely identify a Kubernetes object, including EKS billing_source, EKS cluster name, EKS deployment_kind EKS pod, EKS uid, EKS pod_owner_name, and EKS nodegroup name.

  • Custom labels: Labels defined and assigned from your side. These labels appear with a prefix label_ in the DoiT console, for example, label_k8s_app.

DoiT Cloud Analytics integrates EKS metrics with AWS billing data, which means you can combine EKS labels with AWS cost allocation tags assigned to other AWS resources in the same report.

Required permission​

To build and run Cloud Analytics reports, you need the Cloud Analytics User permission in the DoiT console.

Example reports​

The DoiT console provides a pre-built EKS Lens dashboard with report widgets highlighting various aspects of your Amazon EKS spend. You can also build your own reports using EKS labels and other dimensions. Below are some examples.

Cost breakdown by namespace and pod owner​

This example breaks down the cost of the EKS cluster eks-cluster-1 in the last month by namepace and pod owner.

Cost By Service report widget

Cost breakdown by cost type and SKU​

This example further breaks down the EKS cluster cost by cost type and SKU.

Cost By Service report widget

Cost attribution across services​

In this example, the organization uses the label Team to distinguish AWS resources requested by different entities. To display the costs of EKS and other AWS services in the same report, you can include both the standard label Team and the EKS custom label EKS label_team. (Alternatively, you can create an attribution that contains the standard label and its corresponding EKS custom label, and then use attributions in your report.)

Cost By Service report widget

Last updated on