Enterprises wasting 25-35% on AWS
- Flexera’s March 19, 2025 State of the Cloud report found 84% of organizations struggle to manage cloud spend, with 27% self-reported waste. - The FinOps Foundation’s 2025 survey said workload optimization and waste reduction remained the top priority, especially among companies spending over $50 million yearly. - AWS itself pushes anomaly alerts, budgets, rightsizing and idle-resource cleanup as standard cost controls, underscoring how mainstream the problem has become. (docs.aws.amazon.com)
The cleanest version of this story is not that one viral post “revealed” AWS waste. It is that multiple 2025 reports and AWS’s own guidance describe cloud overspending as a routine enterprise problem. (flexera.com) (docs.aws.amazon.com) Flexera said on March 19, 2025 that 84% of organizations see managing cloud spend as their top cloud challenge, and its 2025 State of the Cloud report put wasted cloud spend at 27%. (flexera.com) That 27% figure is broad cloud spend, not AWS alone. It is also self-reported across more than 750 technical professionals and executives, so it should be read as an industry benchmark, not an audited AWS bill. (flexera.com) The FinOps Foundation’s 2025 report points in the same direction. It said workload optimization and waste reduction were the top priority for practitioners, including many at companies spending more than $50 million a year on public cloud. (data.finops.org) By 2026, the FinOps Foundation said optimization was still a priority, but teams reported “diminishing returns” after removing the “big rocks” of waste. The work was shifting from obvious idle capacity to smaller, harder-to-catch inefficiencies. (data.finops.org) AWS’s own Well-Architected guidance names the mechanics plainly: budgets, anomaly detection, Cost Explorer, Trusted Advisor, Savings Plans recommendations, and reports on idle or underused resources. Those are not niche tools for edge cases; they are standard operating advice from AWS. (docs.aws.amazon.com) Another 2025 data point came from Harness, which surveyed 700 engineering leaders and developers in the United States and United Kingdom. Harness estimated 21% of enterprise cloud infrastructure spend would be wasted in 2025 and said fewer than half of respondents had real-time visibility into idle or orphaned resources. (prnewswire.com) Harness also found 55% of developers said purchasing commitments were based on guesswork, while 48% said they did not track and shut down idle resources. That helps explain why cloud waste is often described as an operating problem, not just a pricing problem. (prnewswire.com) On AWS specifically, compute is where much of the money sits. ProsperOps said in its 2025 AWS Compute report that about 60% or more of usage in its survey pool was compute, with roughly 90% of that coming from Amazon Elastic Compute Cloud rather than Lambda or Fargate. (prosperops.com) That matters because idle instances, oversized machines, and poorly managed commitments all compound in compute-heavy environments. ProsperOps said 64% used Reserved Instances or Savings Plans in 2024, up from 45% in 2023, showing enterprises are still trying to close the gap with discounts and automation. (prosperops.com) So the safest takeaway is narrower than the headline. There is solid evidence that enterprises waste a meaningful share of cloud spend, but the strongest sourced benchmark here is roughly 21% to 27%, not a verified AWS-wide 25% to 35% figure. (flexera.com) (prnewswire.com) What the thread on X got right is the direction of travel. What the underlying research shows is that cloud waste is real, common, and now treated by AWS, Flexera, FinOps Foundation, and vendors as a permanent management discipline rather than a one-time cleanup. (docs.aws.amazon.com) (data.finops.org)
