~/ nmadiraju.com Amazon EKS · Cost visibility and allocation
arrow_back Back to nmadiraju
Visual Walkthrough · Cost

How Cost Visibility and Allocation Work on Amazon EKS

Follow Finance's question through shop-prod's October bill as it's split by team, then check yourself with 8 questions.

1Visual Walkthrough

A shared cluster's three nodes split by team, and AWS billing turning instance costs into cost per namespace Cluster shop-prod runs three m6i.4xlarge nodes in three Availability Zones, each with a bar of vCPU requested by teams checkout, search and ml, plus unused capacity. On the right, Cost Explorer shows the bill by service, Cost Management preferences turns on split cost allocation data, a CUR 2.0 export lands in S3, and an Athena query sums cost by namespace. The walkthrough shows oversized requests, idle capacity removed by consolidation, Kubecost, shared costs and cross-AZ traffic. Finance what does each team cost? YOUR VPC · CLUSTER shop-prod · vCPU REQUESTED (CPU ONLY) node-1 us-east-1a m6i.4xlarge · $561/mo TERMINATED node-2 us-east-1b m6i.4xlarge · $561/mo TERMINATED node-3 us-east-1c m6i.4xlarge · $561/mo TERMINATED checkout 6 search 4 unused 6 ml 8 search 4 checkout 2 unused 2 checkout 2 search 2 unused 12 ml 2 search 4 checkout 2 unused 8 checkout 8 search 6 unused 2 uses 1 vCPU Kubecost EKS-optimized bundle cost by namespace, label idle shown as its own line kube-system CoreDNS · VPC CNI kube-proxy · Karpenter used by every team AWS BILLING AND COST MANAGEMENT Cost Explorer · by service EC2-Instances EC2-Other: EBS$96 EC2-Other: transfer$58 EKS$73 Cost Management preferences split cost data usage: Managed Prometheus CUR 2.0 export (Data Exports) → S3 split_line_item_split_cost · _unused_cost tags: aws:eks:namespace, aws:eks:workload-name Athena · EC2 by namespace · Oct · CPU only checkout search ml unused cost column total EC2

    2Quiz to check understanding

    Check yourself