# Inactive EKS cluster | Cloud Efficiency Hub Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/inactive-eks-cluster Clusters that no longer run active workloads but remain provisioned continue incurring hourly control plane costs and may also maintain associated... By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Inactive EKS Cluster The short version Clusters that no longer run active workloads but remain provisioned continue incurring hourly control plane costs and may also maintain associated infrastructure like node groups or VPC components. PointFive Research Cloud cost research at PointFive 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-0061 Type Idle or Unused Resource ## Explanation Why the waste happens and who it affects. Inactive clusters often persist after environment decommissioning, project shutdowns, or migrations. Decommissioning unused clusters eliminates unnecessary operational costs and simplifies infrastructure management. ## Billing model The pricing dimensions that drive this cost. EKS control planes are billed per cluster per hour, regardless of whether any workloads are actively running. In addition, any underlying compute resources (EC2 nodes or Fargate tasks) continue to accrue charges separately. Maintaining unused EKS clusters results in ongoing hourly billing even when no active workloads are present. ## How to detect 5 checks to find it in your estate. - Identify EKS clusters with no active Deployments, StatefulSets, DaemonSets, CronJobs, or running pods over a representative time window - Review node group activity and verify whether any EC2 instances or Fargate tasks are currently attached to the cluster - Analyze cluster API server logs or CloudWatch metrics to confirm minimal API usage and cluster activity - Check tagging, cluster creation metadata, and documentation to assess whether the cluster was associated with a deprecated project or environment - Validate findings with infrastructure owners, DevOps teams, or platform engineering groups before decommissioning ## How to fix How to remove the waste. Decommission EKS clusters confirmed to be inactive by deleting the cluster through the AWS Console, CLI, or API. Ensure that any dependent resources, such as node groups, VPCs, security groups, or service-linked roles, are also reviewed for cleanup. If a lightweight future usage model is anticipated, consider rearchitecting with AWS EKS Fargate profiles to avoid managing EC2 instances directly. ## Documentation Vendor references for pricing and configuration. - [Amazon EKS Documentation docs.aws.amazon.com](https://docs.aws.amazon.com/eks/latest/userguide/what-is-eks.html) - [AWS EKS Fargate Overview docs.aws.amazon.com](https://docs.aws.amazon.com/eks/latest/userguide/fargate.html) - [Amazon 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-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 - AWS EKS CER-0192 ### [Orphaned Kubernetes Resources in EKS](https://www.pointfive.co/efficiency-hub/inefficiencies/orphaned-kubernetes-resources-e7e68) In Kubernetes environments, resources such as ConfigMaps, Secrets, Services, and Persistent Volume Claims (PVCs) are often created dynamically by applications or deployment pipelines. When applications are removed or reconfigured, these... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.