Skip to content
TrustList
News

Amazon EKS Hybrid Nodes now bills large servers as 32 vCPUs

Editorial

By TrustList Editorial

AWS now bills each Amazon EKS Hybrid Nodes server for at most 32 vCPUs, so at the first pricing tier a 64 vCPU host costs 50% less and a 256 vCPU host 88% less; existing nodes must be removed and reattached to get the new price.

About Amazon EKS Hybrid Nodes now bills large servers as 32 vCPUs

Amazon EKS Hybrid Nodes now bills large servers as 32 vCPUs

18 November 2026: Amazon Web Services has capped what it charges for each server attached to Amazon EKS Hybrid Nodes, the option that lets companies run their own on-premises and edge machines as nodes in an Amazon Elastic Kubernetes Service cluster. Each hybrid node is now billed for at most 32 vCPUs, however many it has. At the first pricing tier, AWS says, a 64 vCPU node now costs 50% less than before and a 256 vCPU node 88% less.

Not yet independently verified. The change, the 50% and 88% figures and the advice on existing nodes come from the AWS announcement posted on 18 November 2026 and the Amazon EKS pricing page, both read on 19 November. The per-vCPU hourly rates on the pricing page are drawn by script and could not be read, so no rate is quoted here. The two percentages are AWS's own figures for the first pricing tier. We will update this when it can be confirmed, and remove this note.

How the charge works now

Hybrid Nodes are charged per vCPU per hour, based on what each node reports to Kubernetes, from the moment it joins a cluster until it is removed. On bare metal with hyperthreading switched on, each physical core reports two vCPUs, which made large servers expensive to attach. Under the new rule a node reporting more than 32 vCPUs is billed as 32; a node with 32 or fewer is still billed for what it has. The existing tiers stay in place, applied to total monthly vCPU-hours in each region, across all accounts in an AWS Organization where consolidated billing is used, so the effective rate still falls as usage grows.

The new price applies automatically to hybrid nodes added from now on. Nodes already attached to a cluster keep the old billing until they are deleted and reattached, AWS says. The change is available in every region that offers EKS Hybrid Nodes.

Who gains

AWS aims the change at large bare-metal and GPU servers running heavy work, such as AI training and inference, that must stay on premises for data residency, latency or regulatory reasons. Until now the per-vCPU charge grew with the size of the machine, which pushed some teams to split big hosts into virtual machines or to keep them outside EKS altogether.

What platform teams should do

  • List the hybrid nodes that report more than 32 vCPUs; they are the ones whose bill changes.
  • Plan the delete-and-reattach step for those nodes in a maintenance window: drain each node, remove it from the cluster and join it again, checking that daemon sets, storage drivers and GPU operators come back as expected.
  • Recheck any cost model that compared EKS Hybrid Nodes with running a separate Kubernetes distribution on premises, since the answer for large GPU hosts may now be different.
  • Note that hybrid nodes running on Amazon EC2 instances are also charged the hybrid nodes fee, so the cap matters there too.

Teams should read the current per-vCPU rates on the EKS pricing page before they rework budgets, and confirm the saving on the first full monthly bill after reattaching.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in