How athenahealth modernized healthcare workloads with Amazon EKS Hybrid Nodes
athenahealth moved its Clinicals Macro Service from AWS Outposts to Amazon EKS Hybrid Nodes, keeping on-premises worker nodes in one EKS cluster with a control plane in an AWS Region. The post reports about 50 percent lower HTTP response times, about 50 percent projected hardware cost savings, and CPU use below 10 percent across an eight-node fleet, and says the company passed a HITRUST audit. These figures are the authors' own account of the migration and were not independently verified.
What changes for platform teams
A platform team that must keep latency-sensitive or data-resident workloads on premises can run them under the same EKS control plane, APIs and tooling as cloud nodes, instead of operating a second control plane. The team still owns the hardware, network, node OS and storage, and needs Direct Connect or VPN connectivity and a separate nodeadm upgrade path for hybrid nodes.
Read the original at AWS Containers Blog ↗
written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules