EKS extended support cost: how to check if your clusters pay the surcharge
Amazon EKS bills a higher per-cluster hourly rate for clusters running Kubernetes versions in extended support, and this charge appears as <region>-AmazonEKS-Hours:extendedSupport in your Cost and Usage Report. You can identify affected clusters in under 10 minutes using the AWS CLI and Cost Explorer.
Why is my EKS cluster bill higher than expected?
The extra cost is not from worker nodes, storage, or data transfer. It is a control plane fee on every EKS cluster running a Kubernetes version past its 14-month standard support window, and it applies whether the cluster is busy or idle.
The charge does not end when extended support does. At the end of extended support, AWS automatically upgrades the cluster to the oldest version still in extended support, so the cluster keeps paying the extended rate. The only way off the extended rate is to upgrade the cluster to a version in standard support.
New clusters default to EXTENDED upgrade policy. When a version ages out of standard support, AWS does not automatically upgrade the cluster, it simply switches the billing rate. The cluster continues running, but you pay more. The usage type <region>-AmazonEKS-Hours:extendedSupport appears separately from the standard <region>-AmazonEKS-Hours:perCluster line in your bill.
How do I find EKS extended support charges in Cost Explorer?
Open Billing and Cost Management > Cost Explorer. Set the date range to the last 3 months and granularity to Monthly. Under Filters, set Service to EKS (Cost Explorer lists it as Amazon Elastic Container Service for Kubernetes), then set Group by to Usage type.
Look for any usage type ending in AmazonEKS-Hours:extendedSupport. The prefix (e.g., USE1-) tells you the region where the charge is active.
To find which clusters are affected, run this in each region:
REGION=us-east-1
for cluster in $(aws eks list-clusters --region "$REGION" --query 'clusters[]' --output text); do
aws eks describe-cluster --region "$REGION" --name "$cluster" \
--query 'cluster.[name, version, upgradePolicy.supportType]' --output text
done
Replace us-east-1 with each region you use, or wrap it in a loop over all regions:
for REGION in $(aws ec2 describe-regions --query 'Regions[].RegionName' --output text); do
for cluster in $(aws eks list-clusters --region "$REGION" --query 'clusters[]' --output text); do
aws eks describe-cluster --region "$REGION" --name "$cluster" \
--query 'cluster.[name, version, upgradePolicy.supportType]' --output text
done
done
Each line shows the cluster name, Kubernetes version, and upgrade policy. Compare the version to the EKS Kubernetes version lifecycle page (https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html, checked November 2026). A version past its end-of-standard-support date is billing at the extended support rate.
If supportType is EXTENDED, the cluster moves into extended support when its version ages out. If supportType is STANDARD, AWS upgrades the control plane automatically when standard support ends.
You can also query your CUR in Athena:
SELECT
line_item_resource_id,
line_item_usage_type,
SUM(line_item_usage_amount) AS cluster_hours,
SUM(line_item_unblended_cost) AS cost
FROM cost_and_usage_report
WHERE line_item_product_code = 'AmazonEKS'
AND line_item_usage_type LIKE '%extendedSupport%'
AND line_item_line_item_type = 'Usage'
AND line_item_usage_start_date >= date_add('month', -3, current_date)
GROUP BY line_item_resource_id, line_item_usage_type
ORDER BY cost DESC;
Check your own bill in 2 minutes: https://revelations.consulting/checker?utm_source=blog&utm_medium=organic&utm_content=blog-eks-extended-support-cost
How do I fix EKS extended support costs without breaking anything?
Start by checking for deprecated APIs that will break on newer Kubernetes versions. Use pluto to scan Helm releases and native resources:
# Install: brew install FairwindsOps/tap/pluto
TARGET=1.NN # one minor version above your current version
pluto detect-all-in-cluster --target-versions k8s=v${TARGET}.0 -o wide
pluto detect-helm --target-versions k8s=v${TARGET}.0 -o wide
pluto detect-files -d ./manifests --target-versions k8s=v${TARGET}.0 -o wide
Or use kubent:
# Install: https://github.com/doitintl/kube-no-trouble/releases
kubent --target-version "${TARGET}.0"
Fix any deprecated resources before upgrading. Then check the cluster’s Upgrade insights tab in the EKS console, or run:
aws eks list-insights --cluster-name your-cluster
Clear any errors before proceeding. Update the VPC CNI addon to the latest version supported on both your current and target version:
aws eks describe-addon-versions --kubernetes-version "$TARGET" --addon-name vpc-cni
Do the same for CoreDNS and kube-proxy:
aws eks describe-addon-versions --kubernetes-version "$TARGET" --addon-name coredns
aws eks describe-addon-versions --kubernetes-version "$TARGET" --addon-name kube-proxy
Upgrade the control plane:
aws eks update-cluster-version --name your-cluster --kubernetes-version "$TARGET"
aws eks wait cluster-active --name your-cluster
Once active, update the addons to their default versions for the new release:
for ADDON in vpc-cni coredns kube-proxy; do
VERSION=$(aws eks describe-addon-versions --kubernetes-version "$TARGET" --addon-name "$ADDON" \
--query 'addons[0].addonVersions[?compatibilities[?defaultVersion]] | [0].addonVersion' --output text)
aws eks update-addon --cluster-name your-cluster --addon-name "$ADDON" \
--addon-version "$VERSION" --resolve-conflicts PRESERVE
aws eks wait addon-active --cluster-name your-cluster --addon-name "$ADDON"
done
Use PRESERVE, not OVERWRITE. OVERWRITE resets settings you changed outside the add-on configuration, such as a custom CoreDNS Corefile or VPC CNI environment variables for custom networking or prefix delegation, and that can break DNS or pod networking across the cluster. If aws eks describe-addon returns ResourceNotFoundException, the add-on is self-managed: update it with its own manifest or Helm chart instead.
Then upgrade managed node groups one at a time:
aws eks update-nodegroup-version --cluster-name your-cluster --nodegroup-name your-nodegroup --kubernetes-version "$TARGET"
Ensure PodDisruptionBudgets allow evictions and critical workloads have multiple replicas. Self-managed and Karpenter nodes require new AMIs rolled out separately.
EKS upgrades are one minor version at a time. A control plane upgrade cannot be rolled back. If a workload breaks after upgrade, fix forward or rebuild on a new cluster.
Repeat the one-minor-version upgrade until the lifecycle page shows the cluster's version in standard support. Do not set STANDARD while the cluster is still on an extended support version, because that hands AWS the timing of a control plane upgrade you cannot roll back. Once the cluster is in standard support, set its upgrade policy to STANDARD:
aws eks update-cluster-config --name your-cluster --upgrade-policy supportType=STANDARD
This does not freeze the version. AWS will automatically upgrade the control plane when standard support ends. Only set STANDARD on clusters you plan to upgrade on schedule. Rehearse every upgrade on a non-production cluster first.
What it usually looks like
The EKS extended support charge usually sits in a region you don’t monitor closely, on a cluster created for a test, proof-of-concept, or migration that was never deleted. Terraform or eksctl configurations often pin the version without setting upgradePolicy, so the cluster inherits EXTENDED by default. The describe-cluster output shows a version past its end-of-standard-support date, and Cost Explorer shows a monthly charge that doesn’t move with node count or traffic.
The fee is charged per cluster, so every forgotten cluster pays its own surcharge. Run the region loop above in every AWS account in your organization, not just production. Checking every line item this way, one usage type at a time, is how I cut a roughly $1M-a-year cloud bill by 26% at a former employer.
If the query turns up clusters you cannot upgrade this quarter, or you want the rest of the bill checked the same way, book a free 30-minute consult. You talk to a senior engineer, not a slide deck.
Frequently asked questions
How much does the EKS extended support surcharge cost?
The extended support rate is a higher per-cluster hourly fee for EKS control planes running Kubernetes versions past their 14-month standard support window. The exact rate is listed on the Amazon EKS pricing page (https://aws.amazon.com/eks/pricing/, checked November 2026). You pay this rate instead of the standard rate while the version is in extended support.
Which Kubernetes versions are currently in extended support?
The EKS Kubernetes version lifecycle page (https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html, checked November 2026) lists which Kubernetes versions are in standard support and which are in extended support. EKS clusters on a version in extended support bill at the extended support rate on the Amazon EKS pricing page. When extended support for a version ends, AWS automatically upgrades clusters on that version to the oldest version still in extended support, so those clusters keep paying the extended rate.
Can I disable the extended support surcharge?
The EKS extended support charge stops only when you upgrade the cluster to a Kubernetes version in standard support; no setting switches it off on an older version. Once the cluster is in standard support, aws eks update-cluster-config --name <cluster-name> --upgrade-policy supportType=STANDARD makes AWS auto-upgrade the control plane when standard support ends instead of moving the cluster into extended support.
Does the extended support charge apply to Fargate profiles?
The EKS extended support charge applies to clusters that run Fargate profiles, because the charge is a per-cluster control plane fee on any EKS cluster running a version in extended support, whatever the compute type. Fargate pod compute is billed separately and is not affected by extended support.
How do I know if my EKS cluster is paying for extended support?
Run aws eks describe-cluster --name <cluster-name> --query 'cluster.[version, upgradePolicy.supportType]' --output text. Compare the version to the EKS version lifecycle page (https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html, checked November 2026). If the version is past its end-of-standard-support date and the supportType is EXTENDED, the cluster is paying the extended support rate.
Want this kind of thing weekly? Get Cloud Bill Weekly. Want us to find it in your bill? We're taking three founding clients for a free Cost Assessment.