How Acquia cut web node infrastructure by 65% with continuous Kubernetes rightsizing
Acquia modernized a platform that previously ran on roughly 26,000 EC2 nodes by moving to Kubernetes. The goal wasn’t just containerization—it was elastic scaling for traffic spikes without relying on fixed “small/medium/large” sizing.
Results at a glance
| 65% reduction in web node footprint | 99.99% availability delivered consistently |
| 26,000 EC2 nodes as the legacy baseline modernized toward Kubernetes | Elastic scaling for peak demand (traffic spikes and seasonal/holiday events) |
“We don’t bring value to our customers by building an optimization platform for Kubernetes—we bring value by bringing customers the resources they need, when they need them.”
– Ed Brennan, Chief Architect, Acquia
Before StormForge, Acquia migrated customers from EC2 using static configuration tiers—small, medium, and large—based on historical usage. That approach worked for getting workloads moved, but it didn’t match how demand changes over time.
With StormForge, Acquia shifted to continuous rightsizing for web nodes, so infrastructure stays closer to real need as workloads scale up and down. The outcome was a 65% reduction in web node footprint while maintaining consistent 99.99% availability as well as a more efficient AWS operating model.
Start a free trial of continuous Kubernetes rightsizing
Start free trial
Related Blogs
Does Your Multi-Cloud Stack Need a Control Plane?
Most infrastructure teams never decide to run a dozen tools across three clouds. It accumulates, one reasonable choice at a…
