Cloud Cost Optimization Assessment

Where does your cloud budget go?

Getting rid of things nobody uses yields the least. The biggest savings are in databases, compute, and networking.

In the AWS environments analyzed by SUE, more than a third of the waste is in databases, nearly a quarter is in compute, and nearly a fifth is in networking. Unused resources account for only 6.6% of the total. So if you just clean up, you’re leaving the lion’s share untouched.

That’s because a cloud environment evolves over time. What was a logical choice three years ago no longer aligns with current usage. That’s why we look beyond the invoice: at architecture, workloads, usage patterns, and procurement agreements.

On Azure and Google Cloud, the services have different names, but the assessment examines the same categories. We include Kubernetes clusters and multi-cloud environments in the same analysis.

Waste in AWS environments by category: databases 34.9%, compute 23.4%, networking 18.9%, storage 12.2%, unused resources 6.6%, other 4.1%. Customers save an average of 37%.

  • Databases: 34.9%
  • Compute: 23.4%
  • Network: 18.9%
  • Storage: 12.2%
  • Unused resources: 6.6%
  • Other: 4.1%

Source: Cost analyses from SUE in customers' AWS environments.

From insight to tangible savings


A report that ends up in a drawer doesn’t save anything. That’s why the assessment continues into implementation: we identify areas for improvement, work together to determine what takes priority, and then implement the optimizations. We work according to the principle “Show. Do together. Do yourself.” That way, your team can do it on their own afterward.

How the Cloud Cost Optimization Assessment works

01

Analysis


We analyze infrastructure, cloud costs, workloads, and architecture based on your own cloud’s cost data. Among other things, we look at compute, database configurations, storage tiers, data traffic, serverless versus provisioned resources, unused and overprovisioned resources, and your procurement agreements. At Colect, we identified the most significant opportunities in just three days.

02

Strategy


Not every cost-saving measure is worth the effort. For each measure, we assess the savings, the effort required, and the risk—from quick wins to architectural changes. We align procurement commitments with your roadmap.

03

Implementation


Our cloud engineers implement the optimizations: clearing out unused resources, right-sizing workloads, and adjusting the architecture wherever it can be done more cost-effectively and efficiently. We implement every change in a controlled manner, with a fallback option.

04

Optimize


A cloud environment is constantly changing. Through monitoring, periodic reviews, and knowledge transfer, we make costs an integral part of your cloud management. If desired, an AI agent (Agentic FinOps) can flag anomalies and opportunities, which an engineer then evaluates.

Submission

What do you need to provide, and how long does it take?

During the assessment, SUE does not make any changes to your environment. Those changes are made only during implementation, after you have given your approval.

5 business days from the time SUE gains access to your cost data

1 hour with your architect or engineer for an initial consultation and discussion

The assessment is free: it won't cost you a thing

What you provide

  • Read access to your cost data AWS · IAM role, read-only Azure · Cost Management Reader Google Cloud · Billing Account Viewer

  • An overview of your accounts, subscriptions, or projects and who owns them

  • Your current purchasing agreements: Savings Plans, reservations, or committed use discounts

  • One hour of an architect's or engineer's time

Completion

What you'll get: a plan that's all yours

The assessment results in a single document—the Cloud Cost Savings Plan—and a one-hour discussion with your team. You implement the plan yourself, with SUE, or with another provider.

The choices that developers, engineers, and architects make today determine what you'll pay tomorrow. That's why the plan also shows who incurs which costs, so that teams can factor in costs just as they do performance and security.

Cloud Cost Savings Plan

  • Cost breakdown by account, service, and team

  • Measures listed in order of savings, effort, and risk, with the savings in euros per month

  • Plan for the first 90 days: what your team will do, what SUE will do, and in what order

  • Guidance on the coverage and term of purchase obligations

  • Proposal for FinOps: roles, KPIs, and review frequency

How to reduce your cloud costs, by category

The percentages are based on our analyses of AWS environments. We apply these measures to all three clouds; the services and procurement models differ by cloud.

Databases (34.9%)

Resize and merge instances, adjust database storage, choose between serverless and provisioned capacity (such as Aurora Serverless or Azure SQL Database serverless), and add indexes so that queries consume fewer resources.

Compute (23.4%)

Discounts for committed usage: Savings Plans and Reserved Instances on AWS, reservations and the Savings Plan for Compute on Azure, and committed use discounts on Google Cloud. In addition, Spot capacity for workloads that can tolerate interruptions, rightsizing, scaling policies, and ARM processors such as AWS Graviton, Azure Cobalt, and Google Axion.

Network (18.9%)

Optimize NAT gateways, consolidate load balancers, route traffic through a CDN (CloudFront, Azure Front Door, or Cloud CDN), and eliminate public IPv4 addresses, which incur hourly charges.

Storage (12.2%)

Configure volume types (EBS, Azure Managed Disks, Persistent Disk), select the appropriate storage classes in S3, Azure Blob Storage, and Cloud Storage, and set up lifecycle policies.

Unused resources (6.6%)

Remove unused resources. We'll first show you what they cost so you can clean up without affecting important workloads.

Architecture and throughput

Sometimes the savings come from the architecture or the application itself: a different database, serverless or provisioned, or an application that handles more work using the same infrastructure. On AWS, we combine that with an AWS Well-Architected Review.

How much customers saved

About SUE

Modernize the code. Optimize the cloud. Run the platform.

SUE is a Dutch cloud & AI native solutions partner that modernizes business-critical applications, reduces cloud costs and manages your platform. Specialist in Linux, Kubernetes and cloud.

More about SUEView our approach

29+

Years of experience

150+

Engineers and consultants

1.150+

Certifications

ISO

9001 & 27001

500+

Projects

75+

Research papers

Frequently asked questions

All frequently asked questions
A Cloud Cost Optimization Assessment is a technical analysis of your environment on AWS, Azure, or Google Cloud. SUE examines your invoice and what lies behind it: architecture, workloads, usage, and procurement agreements. You’ll receive the Cloud Cost Savings Plan: a breakdown of costs by account, service, and team; measures ranked by savings potential, effort, and risk; and a plan for the first 90 days. Afterward, we’ll implement the cost-saving measures together with your team.
5 business days from the time SUE gains read access to your cost data. After that, we’ll discuss the Cloud Cost Savings Plan with your team.
The assessment is free.

That varies greatly depending on the environment. In the AWS environments analyzed by SUE, customers save between 4% and 80% on their bills, with an average savings of 37%. An environment that has grown over the years without being reviewed typically yields greater savings than one that has already been optimized. For Azure and Google Cloud, the assessment shows what savings are possible in your environment.

In the AWS environments analyzed by SUE, 34.9% of the waste is in databases, 23.4% in compute, 18.9% in networking, 12.2% in storage, and 6.6% in unused resources. The greatest savings, therefore, require a technical review of databases and architecture. Simply cleaning up yields the least benefit. We examine the same categories on Azure and Google Cloud.

How much should your cloud environment cost?

Please provide your contact information. We'll discuss your environment on AWS, Azure, or Google Cloud and schedule the assessment.

Jonah Sanderse
Jonah Sanderse

Let’s talk


How much should your cloud environment cost?

Please provide your contact information. We'll discuss your environment on AWS, Azure, or Google Cloud and schedule the assessment.

* required

For example: your question, your current situation, or your deadline.
We will respond within one business day. By submitting this form, you confirm that you have read and understood our privacy policy.
SUE Cloud & AI Native Solutions
Privacy overview
This website uses cookies. We use cookies to ensure that our website and services function properly, to gain insight into the use of our website, and to improve our products and marketing. For more information, please read our privacy and cookie policy.