On October 28, 2026, Amazon EKS Auto Mode gained native support for the Kubernetes Gateway API. You define GatewayClass , Gateway and HTTPRoute (or GRPCRoute , TCPRoute , UDPRoute ), and Auto Mode provisions and runs the Application Load Balancer or Network Load Balancer behind them. No AWS Load Balancer Controller to install, no Helm chart to upgrade, no IAM role to wire up.
If your clusters already run Auto Mode, this closes an awkward gap. Auto Mode promised that AWS operates the cluster's infrastructure components, but its managed load balancing only spoke Ingress and Service type LoadBalancer . With Ingress NGINX retired in March and most teams moving to Gateway API, Auto Mode users had to bolt a controller back on, which is exactly what Auto Mode is supposed to remove.
Platform defines the class, cluster operators define the Gateway, app teams define routes, and Auto Mode runs the load balancer (labels in Spanish).…