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's control-plane fee isn't flat forever — it's a two-tier system tied to how current your Kubernetes minor version is, not to cluster size or traffic. 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, with no opt-in and no warning banner. Multi-cluster topologies (isolating dev/staging/prod, or per-business-unit clusters) multiply this fixed fee across every cluster before a single pod is scheduled.

Failure mode & inflection point

the 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, so a cluster that nobody's 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's an unannounced ~$7,300/month ($87,600/year) increase with zero change in compute utilization. Watch aws eks describe-cluster-versions or the CUR line-item AmazonEKS-Hours:extendedSupport (vs. AmazonEKS-Hours:perCluster for standard) to see 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 — two months of buffer before the Extended Support auto-tier at month 14–15. Non-production environments should 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's used.