~/ 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 until every dollar has a 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, the bill shows EC2 instances, data transfer and the EKS fee, Cost Management preferences turns on split cost allocation data, the Cost and Usage Report lands in S3, and an Athena query sums cost by namespace. The walkthrough shows an oversized request, idle capacity removed by consolidation, a policy for costs with no team, and cross-zone traffic. Finance what does each team cost? YOUR VPC · CLUSTER shop-prod · vCPU REQUESTED (CPU ONLY) node-1 us-east-1a m6i.4xlarge · $560/mo TERMINATED node-2 us-east-1b m6i.4xlarge · $560/mo TERMINATED node-3 us-east-1c m6i.4xlarge · $560/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 AWS BILLING AND COST MANAGEMENT Cost Explorer · by service EC2 instances Data transfer$58 EKS fee$73 Total Cost Management preferences split cost data max(request, use) Cost and Usage Report (CUR) → S3 hourly row per Pod: split cost, unused cost tagged with namespace, workload Athena · EC2 by namespace · Oct · CPU only checkout search ml unused (not charged) total EC2

    2Quiz to check understanding

    Check yourself