Your AWS bill is 20 to 40% larger than it needs to be
That is the range the industry consistently reports for estates that have never had a dedicated cost review. In two weeks we tell you where yours sits, what to cut first, and what each cut is worth per year.
From EUR 6,000 · 2 weeks · read-only access · fixed fee, never a percentage of savings.
Does this sound like your estate?
If three or more of these are true, the review will pay for itself.
- The AWS bill goes up every month and nobody can say exactly why.
- You cannot attribute spend to a team, product, or environment.
- Savings Plan and Reserved Instance coverage was set once and never revisited.
- Instances were sized during migration and have not been touched since.
- Snapshots, unattached volumes, and old S3 tiers accumulate unchecked.
- Data transfer and NAT Gateway charges are a line item nobody owns.
- A cost surprise is discovered on the invoice, not by an alert.
- Finance asks for a forecast and engineering cannot produce one.
The six levers we pull
- Commitment strategy. Savings Plans and Reserved Instances modelled against your actual usage curve. Coverage and utilisation tracked as two separate numbers, because high coverage on the wrong commitment is a loss, not a win.
- Rightsizing and idle elimination. Compute, database, and cache instances measured against real utilisation rather than the size someone picked during migration.
- Tagging governance and showback. A tagging standard that survives contact with delivery teams, plus reporting so each team sees and owns its own consumption.
- Storage lifecycle. S3 class transitions and expiry, EBS snapshot hygiene, unattached volumes, and log retention matched to what you are actually required to keep.
- Data transfer and network design. Cross-AZ and cross-region traffic, NAT Gateway placement, and VPC endpoint opportunities.
- Visibility that outlives the engagement. Cost and Usage Report analysis in Athena and QuickSight, cost anomaly detection, and budget alerting.
What you get
- Cost breakdown - where the money actually goes, by account, service, team, and environment.
- Prioritised savings backlog - each item with estimated annual saving, effort, and risk to production.
- 90-day implementation plan - sequenced so the no-risk savings land in week one and fund the rest.
Everything is delivered in a format your team can edit and maintain. The Athena queries and QuickSight dashboards are built in your account and stay there.
How the two weeks run
- Week 1, measure. Read-only access to billing and the Cost and Usage Report, plus a look at the account structure. We build the spend picture, interview the teams who own the largest workloads, and separate committed spend from on-demand waste.
- Week 2, model and sequence. Every candidate saving quantified and weighted by effort and production risk. You get the backlog, the 90-day plan, and a walkthrough with whoever signs off.
- After. Implementation is scoped separately. Take the plan to your own team, or engage us for some or all of it.
Why ccX
- We do this work right now. ccX currently owns AWS cost optimisation across an EU institution's multi-account estate: commitment strategy, tagging governance, showback, and anomaly detection running in production.
- Architects, not dashboard resellers. Our principal holds six AWS certifications, all three at Professional level. Most savings need an architecture change rather than a coupon.
- No percentage of savings. A fixed fee, published up front.
Get started
Book a 30-minute scoping call or email info@ccx.hu.