--- title: What Is EKS Auto Mode? Managed Karpenter Node Autoscaling description: EKS Auto Mode is an AWS cluster configuration mode (GA December 2024) that runs Karpenter as a fully managed off-cluster service, automating node provisioning,... canonical: https://daily.dev/posts/what-is-eks-auto-mode-managed-karpenter-node-autoscaling-8bgdetnrj twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: What Is EKS Auto Mode? Managed Karpenter Node Autoscaling | daily.dev og:description: EKS Auto Mode is an AWS cluster configuration mode (GA December 2024) that runs Karpenter as a fully managed off-cluster service, automating node provisioning,... og:url: https://daily.dev/posts/what-is-eks-auto-mode-managed-karpenter-node-autoscaling-8bgdetnrj og:image: https://api.daily.dev/og/posts/8bGdetNrJ.png og:image:alt: What Is EKS Auto Mode? Managed Karpenter Node Autoscaling og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # What Is EKS Auto Mode? Managed Karpenter Node Autoscaling **[Cast AI](https://daily.dev/sources/castai)** · 14 min read · 0 upvotes · 0 comments ## Summary EKS Auto Mode is an AWS cluster configuration mode (GA December 2024) that runs Karpenter as a fully managed off-cluster service, automating node provisioning, AMI patching, load balancing, networking, and storage with a single API call. It requires EKS 1.29+. The key trade-off is a ~12% surcharge on EC2 On-Demand price per managed node — a fleet of 100 m5.large nodes accumulates ~$830/month in fees alone. Auto Mode restricts AMIs to Bottlerocket only, disables SSH/SSM, and pins the Karpenter version. Self-managed Karpenter offers full control over AMIs, versions, and node access but requires significant engineering overhead. The post covers cost comparisons, migration steps from self-managed Karpenter, monitoring approaches, and notes that neither option solves workload-level overprovisioning (average CPU utilization sits at just 8% across 23,000+ clusters). ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How much does the EKS Auto Mode management fee cost compared to running Karpenter myself? EKS Auto Mode adds approximately a 12% surcharge on the EC2 On-Demand price per managed node, billed per second. For example, an m5.large instance costs $0.096/hr in EC2 plus about $0.0115/hr in Auto Mode fees, totaling $0.1075/hr. Compute Savings Plans and Reserved Instances discount only the EC2 portion, not the surcharge, and a 100-node m5.large fleet accrues roughly $830/month in fees alone. _Compare autoscaler cost trade-offs like this before locking in an EKS compute strategy, using daily.dev to track the details._ ### What are the main limitations of EKS Auto Mode compared to self-managed Karpenter? EKS Auto Mode only supports Amazon-provided Bottlerocket AMIs, disables SSH and SSM host access, and prevents pinning the Karpenter version or enabling experimental feature flags. It also uses a different NodeClass API (eks.amazonaws.com/v1 NodeClass instead of karpenter.k8s.aws/v1 EC2NodeClass), so existing configurations need rewriting rather than direct porting, and existing load balancers require a blue-green migration to move over. _Weigh flexibility against operational overhead like this when choosing an EKS autoscaling setup, and keep notes on daily.dev._ ### How do I migrate from self-managed Karpenter to EKS Auto Mode? Scale the self-managed Karpenter controller deployment to 0 replicas so it stops scheduling, then let Auto Mode gradually take over as pods reschedule, tainting old nodes to speed adoption if needed. Rewrite NodePool specs to use the Auto Mode eks.amazonaws.com/v1 NodeClass API, migrate load balancers using a blue-green approach, and run both setups in parallel during validation before removing the old controller. _Follow a migration sequence like this and track the rollout details on daily.dev as you validate the switch._ ## Similar posts on daily.dev - [AWS EKS Auto Mode wants to end Kubernetes toil — one node at a time](https://daily.dev/posts/aws-eks-auto-mode-wants-to-end-kubernetes-toil-one-node-at-a-time-qcwmvi1vw) · The New Stack · 0 upvotes · 0 comments - [Best Kubernetes Autoscaling Tools in 2026 Compared](https://daily.dev/posts/best-kubernetes-autoscaling-tools-in-2026-compared-cb2bncs0t) · Cast AI · 0 upvotes · 0 comments - [Amazon EKS Auto Mode Announces Enhanced Logging for its Managed Kubernetes Capabilities](https://daily.dev/posts/amazon-eks-auto-mode-announces-enhanced-logging-for-its-managed-kubernetes-capabilities-cz6yy5ebn) · AWS · 0 upvotes · 0 comments - [Deploy Karpenter on EKS: Node Auto-Scaling Guide \(2026\)](https://daily.dev/posts/deploy-karpenter-on-eks-node-auto-scaling-guide-2026--xmjijfzcy) · Cast AI · 0 upvotes · 0 comments --- Tags: [#aws](https://daily.dev/tags/aws), [#kubernetes](https://daily.dev/tags/kubernetes) [View this post on daily.dev](https://daily.dev/posts/what-is-eks-auto-mode-managed-karpenter-node-autoscaling-8bgdetnrj) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"What Is EKS Auto Mode? Managed Karpenter Node Autoscaling","url":"https://daily.dev/posts/what-is-eks-auto-mode-managed-karpenter-node-autoscaling-8bgdetnrj","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/what-is-eks-auto-mode-managed-karpenter-node-autoscaling-8bgdetnrj"},"datePublished":"2026-08-07T08:27:24.570Z","dateModified":"2026-10-15T02:22:57.002Z","description":"EKS Auto Mode is an AWS cluster configuration mode (GA December 2024) that runs Karpenter as a fully managed off-cluster service, automating node provisioning,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/4a517f2bb3ac092a93c7831b54217153?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/4a517f2bb3ac092a93c7831b54217153?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Cast AI","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Cast AI","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/e5868702aaf84d8293e56794e2c6629c","url":"https://daily.dev/sources/castai"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/what-is-eks-auto-mode-managed-karpenter-node-autoscaling-8bgdetnrj","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"aws,kubernetes","timeRequired":"PT14M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Cast AI","item":"https://daily.dev/sources/castai"},{"@type":"ListItem","position":3,"name":"What Is EKS Auto Mode? Managed Karpenter Node Autoscaling"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/what-is-eks-auto-mode-managed-karpenter-node-autoscaling-8bgdetnrj#faq","mainEntity":[{"@type":"Question","name":"How much does the EKS Auto Mode management fee cost compared to running Karpenter myself?","acceptedAnswer":{"@type":"Answer","text":"EKS Auto Mode adds approximately a 12% surcharge on the EC2 On-Demand price per managed node, billed per second. For example, an m5.large instance costs $0.096/hr in EC2 plus about $0.0115/hr in Auto Mode fees, totaling $0.1075/hr. Compute Savings Plans and Reserved Instances discount only the EC2 portion, not the surcharge, and a 100-node m5.large fleet accrues roughly $830/month in fees alone. Compare autoscaler cost trade-offs like this before locking in an EKS compute strategy, using daily.dev to track the details."}},{"@type":"Question","name":"What are the main limitations of EKS Auto Mode compared to self-managed Karpenter?","acceptedAnswer":{"@type":"Answer","text":"EKS Auto Mode only supports Amazon-provided Bottlerocket AMIs, disables SSH and SSM host access, and prevents pinning the Karpenter version or enabling experimental feature flags. It also uses a different NodeClass API (eks.amazonaws.com/v1 NodeClass instead of karpenter.k8s.aws/v1 EC2NodeClass), so existing configurations need rewriting rather than direct porting, and existing load balancers require a blue-green migration to move over. Weigh flexibility against operational overhead like this when choosing an EKS autoscaling setup, and keep notes on daily.dev."}},{"@type":"Question","name":"How do I migrate from self-managed Karpenter to EKS Auto Mode?","acceptedAnswer":{"@type":"Answer","text":"Scale the self-managed Karpenter controller deployment to 0 replicas so it stops scheduling, then let Auto Mode gradually take over as pods reschedule, tainting old nodes to speed adoption if needed. Rewrite NodePool specs to use the Auto Mode eks.amazonaws.com/v1 NodeClass API, migrate load balancers using a blue-green approach, and run both setups in parallel during validation before removing the old controller. Follow a migration sequence like this and track the rollout details on daily.dev as you validate the switch."}}]} ```