Hybrid Nodes attaches on-premises and edge machines to an EKS cluster: AWS runs the control plane, you run the hardware. It costs $0.020 per vCPU-hour for the first tier (about $467 a month for a 32-vCPU server), needs a reliable link to AWS, and isn't for disconnected sites. Where it beats running Kubernetes yourself.
EKS Hybrid Nodes lets physical or virtual machines in your own data centers and edge sites join an EKS cluster as nodes. AWS manages the Kubernetes control plane; you manage the machines, their OS and their network. Most EKS features work, including add-ons, Pod Identity, access entries, cluster insights and extended version support.
Plus the cluster's normal control plane charge. Billing runs while a node is attached, so remove nodes you aren't using.
A 32-vCPU server attached all month is 23,360 vCPU-hours: about $467 at the first tier. Ten of them about $4,670 a month, in exchange for not running a Kubernetes control plane on-premises.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
You have hardware that must stay on-premises (data residency, latency to machines, a sunk investment) and want one way to deploy everywhere.
You want to burst from on-premises into AWS Regions in the same cluster.
Your sites have a reliable connection to AWS: Site-to-Site VPN, Direct Connect or your own VPN.
Sites are disconnected or intermittently connected: AWS points those to EKS Anywhere instead.
The machines are in a cloud, including EC2: that isn't supported, and EC2 instances would be billed the hybrid fee on top.
You need it in GovCloud or China Regions, where it isn't available.
Network ranges are large and scattered: a cluster supports up to 15 remote node CIDRs and 15 remote pod CIDRs.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
An EKS Reference Architecture for 2026, With Diagrams: The Small-Team Version and the Regulated Version
What a production EKS setup looks like in 2026, layer by layer: edge, entry, cluster, platform add-ons, data, security and observability. A lean version for a small team on Auto Mode, and a regulated version with separate node pools, network policies and audit logging, with the choices behind each box.
Read
EKS Network Policies With the VPC CNI: Default Deny, Admin Policies, and the Limits to Know
The VPC CNI enforces Kubernetes network policies natively, and from version 1.21 adds cluster-wide admin policies that namespace owners can't override. How the tiers are evaluated, a default-deny setup, and the limits: EC2 Linux nodes only, 24 port-protocol combinations per CIDR, and pods without an owner.
Read
As of November 2, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.