Practical guide
EKS pricing: separate cluster fees from worker nodes
estimate EKS cluster and EC2 worker costs. Includes a worked example, calculator scope, and practical questions.
Updated · Sources checked
A Kubernetes cluster fee is not the entire compute bill
An EKS estimate has a control-plane component and a workload infrastructure component. Paying the cluster fee does not include all EC2 worker capacity. Conversely, scaling workers down does not automatically remove the provisioned cluster’s fee.
The calculator combines supported EKS cluster fees with Linux On-Demand EC2 workers in US East. It does not model pod scheduling, workload-specific capacity, or every EKS compute option.
Worked example: two clusters sharing a worker budget
Suppose two clusters each run for a 730-hour planning month. Together they contribute 1,460 cluster-hours. Assume the total fleet across both clusters contains six identical EC2 workers running for the same period, producing 4,380 worker-hours.
The modeled subtotal is 1,460 × cluster-hour rate + 4,380 × worker-hour rate. Enter six as the total worker count, not six per cluster, unless the intended fleet actually has 12 workers.
If the total worker fleet rises to nine, worker-hours become 6,570 while cluster-hours remain 1,460. If a third cluster is added without changing workers, cluster-hours become 2,190 while worker-hours stay fixed in the arithmetic. Whether that arrangement is operationally sensible requires a separate architecture review.
Count dependencies outside compute
Add EBS volumes, load balancers, NAT, public IPv4, logs, data transfer, and other services used by workloads. The calculator’s result is not a turnkey price for hosting Kubernetes applications.
Support tier also matters. Check the cluster version and applicable support status instead of assuming the standard support rate applies indefinitely. EKS Auto Mode, Fargate, and other separately priced options require appropriate additional modeling.
Worker requirements depend on pod requests, overhead, availability, and peak load. The tool cannot establish how many nodes safely run an application. Preserve headroom and disruption requirements while using cost arithmetic to compare technically valid options.
Frequently asked questions
Are worker nodes included in the EKS cluster fee? No. This estimate has separate cluster and worker components.
Is worker count per cluster? Treat it as the total fleet being modeled and document that scope. Summing actual node-hours avoids multiplying the fleet twice.
Calculate your scenario
Use the eks cost calculator. Keep the displayed region, pricing date, billing units, and exclusions alongside your result. The arithmetic examples above illustrate usage or explicitly hypothetical rates; they are not AWS quotes.
Source
Billing structure checked against official AWS documentation on September 6, 2026.