A Developer’s Guide to Understanding Cloud Bills (AWS, GCP, Azure)

Translate cloud invoices into the Kubernetes resources you ship—nodes, storage, load balancers, and egress.

J
Jesus Paz
1 min read

Cloud bills are written for accountants, not developers. Here’s how to map line items to the Kubernetes resources you deploy.

  • Compute: instance hours = your nodes; mix of on-demand/spot/preemptible/RI/Savings Plans.
  • Storage: EBS/PD/Disk for PVs; snapshots; object storage for backups and logs.
  • Network: egress out of region/AZ/cloud; load balancer LCUs; NAT/IGW charges.
  • Managed services: control planes, databases, queues—allocate shared services by traffic or seats.
  • Taxes/Support: add 3–10% overhead depending on plan and region.
  • Fixed infra: control plane ($0.10/hr on EKS), idle LBs, and NAT gateways—easy to forget, easy to prune.

If you can point to the deployment that created a line item, you can control it. Tie bills to manifests, not just spreadsheets.***

👨‍💻

Jesus Paz

Founder & CEO

Read Next

Join 1,000+ FinOps and platform leaders

Get Kubernetes and ECS cost tactics delivered weekly.