Skip to content
EKS
AWS track / Compute
Entry overview
Sub-page 2 of 10
Cost & billing mechanics · Free

Budgeting for the Version-Support Cliff Before Extended Support Multiplies Your Control-Plane Bill by 6x

Decision drivers
  • Number of clusters currently running and their individual Kubernetes minor versions relative to the 14-month standard-support window
  • Whether upgrade cadence is currently a scheduled, calendared process or a reactive one
  • Whether cluster-per-team/per-env isolation is a genuine tenant isolation requirement or an unexamined default
  • Whether IaC defaults (Terraform, CloudFormation) currently leave Extended Support silently enabled rather than gated

Production premise

EKS charges a fixed hourly fee just for keeping a cluster's control plane running, and that fee is not flat forever. It is a two-tier system, and which tier you are in depends on how current your Kubernetes minor version is. Cluster size and traffic have nothing to do with it.

Standard support runs $0.10/cluster/hour for 14 months from a version's EKS release date. The moment that window closes, the cluster is automatically enrolled in Extended Support at $0.60/cluster/hour — a 6x increase — for up to 12 more months. There is no opt-in and no warning banner.

Multi-cluster topologies multiply the exposure. Isolating dev/staging/prod, or running per-business-unit clusters, puts this fixed fee on every cluster before a single pod is scheduled.

Failure mode & inflection point

The tier transition is silent and automatic. Clusters provisioned via CLI or IaC tooling (Terraform included) default to Extended Support being available rather than blocking the auto-tier. A cluster that nobody is actively tracking just crosses into $438/month at month 15, with no event to notice.

Across a fleet of 20 un-upgraded non-production clusters, that is an unannounced ~$7,300/month ($87,600/year) increase, with zero change in compute utilization.

Find out what you are already paying. Run aws eks describe-cluster-versions, or look for the CUR line-item AmazonEKS-Hours:extendedSupport (vs. AmazonEKS-Hours:perCluster for standard). That shows which of your clusters are already paying the multiplier without anyone deciding to.

Production guardrail

Enforce an automated pipeline gate that mandates control-plane upgrades by month 12 of a Kubernetes version's release lifecycle. That leaves two months of buffer before the Extended Support auto-tier arrives at month 14–15.

For non-production environments, default to namespace-isolated multi-tenancy on shared clusters rather than per-team/per-env dedicated control planes, unless hard tenant isolation is an actual requirement. Every additional dedicated cluster is another independent $73–$438/month clock, running regardless of whether it is used.