# Outdated EKS cluster incurring extended support charges Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/outdated-eks-cluster-incurring-extended-support-charges When an EKS cluster remains on a Kubernetes version that has reached the end of standard support, AWS begins charging an additional Extended Support fee. By: Jason Eckle, Yulia Perlis [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Outdated EKS Cluster Incurring Extended Support Charges The short version When an EKS cluster remains on a Kubernetes version that has reached the end of standard support, AWS begins charging an additional Extended Support fee. Jason Eckle, Yulia Perlis AWS service [AWS EKS](https://www.pointfive.co/efficiency-hub/cloud-services/aws-eks) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0077 Type Outdated Version ## Explanation Why the waste happens and who it affects. These charges often arise from delays in upgrade cycles, uncertainty about workload compatibility, or overlooked legacy clusters. If the workload does not require the older version, continuing to run the cluster in this state results in unnecessary cost and technical risk. ## Billing model The pricing dimensions that drive this cost. EKS charges a fixed hourly rate per cluster for the control plane. In addition, AWS imposes an additional hourly Extended Support charge per cluster for any control plane running a Kubernetes version beyond the standard support period. This fee is charged in addition to the standard cluster fee, and continues until the cluster is upgraded to a supported version. ## How to detect 5 checks to find it in your estate. - Identify clusters running Kubernetes versions that have reached end of standard support - Confirm whether the cluster is incurring Extended Support charges - Review upgrade history and backlog to understand why the version was not updated - Assess any upgrade blockers, such as incompatible workloads or dependency constraints - Engage with platform teams to determine if the version can be upgraded safely ## How to fix How to remove the waste. Upgrade the EKS control plane and associated node groups to a supported Kubernetes version. Follow AWS best practices for staged upgrades, workload compatibility testing, and version planning. Incorporate version lifecycle checks into your infrastructure review process to avoid future support charges. ## Documentation Vendor references for pricing and configuration. - [AWS EKS Kubernetes Version Lifecycle docs.aws.amazon.com](https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html) - [AWS EKS Pricing aws.amazon.com](https://aws.amazon.com/eks/pricing/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - AWS EKS CER-0298 ### [Stale Completed or Failed Fargate Pods Causing Direct Billing and Capacity Waste](https://www.pointfive.co/efficiency-hub/inefficiencies/stale-completed-or-failed-fargate-pods-causing-direct-billing-and-capacity-waste) Kubernetes Jobs or CronJobs running on EKS Fargate leave completed or failed pod objects in the cluster indefinitely. Although the workload execution has finished, AWS keeps the underlying Fargate microVM running to allow log inspection... Compute - AWS EKS CER-0280 ### [Fargate Resource Rounding and Per-Pod Overhead Driving Step-Up Costs](https://www.pointfive.co/efficiency-hub/inefficiencies/fargate-resource-rounding-and-per-pod-overhead-driving-step-up-costs) Pod resource requests - often inflated by sidecar containers-push total memory or CPU just over a Fargate sizing boundary. Because Fargate adds mandatory system overhead and only supports fixed resource combinations, small incremental... Compute - AWS EKS CER-0120 ### [Orphaned and Overprovisioned Resources in EKS Clusters](https://www.pointfive.co/efficiency-hub/inefficiencies/orphaned-and-overprovisioned-resources-in-eks-clusters) In EKS environments, cluster sprawl can occur when workloads are removed but underlying resources remain. Common issues include persistent volumes no longer mounted by pods, services still backed by ELBs despite being unused, and... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.