EKS 1.31 end of extended support: Nov 26, 2026

• You can no longer create new EKS clusters on 1.31.
• AWS automatically updates existing 1.31 control planes to the earliest supported version, through a gradual rollout after the date. AWS says it can't give a time frame and you won't get a notification before the update.
• Only the control plane is upgraded. Managed node groups and self-managed nodes stay on the old version (EKS Auto Mode nodes may update). You must update add-ons and nodes yourself afterwards.
• Clusters that were auto-upgraded at end of extended support can't be rolled back.

Per AWS pricing, a cluster in extended support pays $0.60 per cluster-hour instead of $0.10, an extra $0.50/hour. Our math at 730 hours/month: about +$365/month per cluster ($438 vs $73). The fee is per cluster, not per node.

Billing for extended support starts at the beginning of the day the version reaches end of standard support (UTC). 1.34 clusters start paying the higher rate on Dec 2, 2026 unless upgraded, because the default upgrade policy is EXTENDED. If you set the policy to STANDARD, AWS instead auto-upgrades the cluster at the end of standard support. See the EKS extended support cost calculator.

aws eks list-clusters --query "clusters[]" --output text

aws eks describe-cluster --name my-cluster \
  --query "cluster.[name,version,upgradePolicy.supportType]" --output text

aws eks describe-cluster-versions

Run per Region. describe-cluster-versions returns each version's endOfStandardSupportDate and endOfExtendedSupportDate. Paste versions into the checker.

1. EKS control plane upgrades go one minor version at a time: 1.31 → 1.32 → 1.33 → 1.34 and so on.
2. Before each hop, check for removed Kubernetes APIs and review AWS's per-version notes.
3. Keep nodes within the supported skew of the control plane; AWS recommends running the same version on both.
4. After the control plane, update managed node groups, self-managed nodes and Fargate pods (redeploy), and the VPC CNI, kube-proxy and CoreDNS add-ons.
5. In-place upgrades can be rolled back to the previous minor version within 7 days.

• AWS docs: Kubernetes version lifecycle on EKS (release calendar, extended support FAQs) ↗
• Amazon EKS pricing ↗
• AWS docs: Update existing cluster to new Kubernetes version ↗
• AWS docs: Kubernetes versions on extended support ↗

When does EKS 1.31 extended support end?

Nov 26, 2026 (UTC), per the Amazon EKS Kubernetes release calendar. Standard support ended Nov 26, 2025.

What happens to my EKS 1.31 cluster after Nov 26, 2026?

AWS automatically updates the control plane to the earliest supported version at some point after the date, without prior notification. Nodes and add-ons are not upgraded, and an auto-upgrade cannot be rolled back.

When does EKS 1.34 standard support end?

Dec 2, 2026. With the default EXTENDED upgrade policy, clusters then move to extended support at $0.60 per cluster-hour instead of $0.10.

Can I skip versions when upgrading EKS?

No. EKS control plane upgrades go one minor version at a time, so 1.31 to 1.34 takes three upgrades.

• EKS extended support cost calculator
• RDS & Aurora extended support pricing
• RDS MySQL 8.0 end of support
• RDS PostgreSQL end-of-support dates
• Lambda runtime deprecation schedule
• ElastiCache for Redis OSS end of support
• OpenSearch & Elasticsearch end of support
• OpenSearch extended support fees from Nov 7, 2026
• Lambda Python 3.10 deprecation (Oct 31, 2026)
• RDS MariaDB 10.6 end of support (Dec 31, 2026)
• RDS PostgreSQL 14 end of standard support (Feb 28, 2027)
• Lambda .NET 8 deprecation (Nov 10, 2026)
• Amazon Neptune 1.1/1.2 end of life (Dec 4, 2026)