Client case study
62% lower AWS spend. Same performance.
Cloud infrastructure The infrastructure fieldbook
An infrastructure audit removed unused capacity and aligned resources with actual usage, reducing the monthly AWS bill without downtime.
Monthly cost reduction
Downtime or performance impact
Drift monitoring post-engagement
01 / Context
An AWS bill without a map.
The client ran its workloads on AWS across multiple accounts, and the environment had grown organically over time.
No one had a clear picture of what was running, what was still needed, and what was simply burning money. Idle instances, unattached storage and oversized compute were consuming budget without matching actual demand.
- Industry
- Cloud services
- Service
- Cloud cost optimization
- Platform
- AWS, across accounts
- Deliverables
- Audit · Right-sizing · Drift monitoring
The challenge
An AWS estate without a clear inventory.
The client's Cloud environment had grown organically over time. No one had a clear picture of what was running, what was needed, and what was burning money.
Idle instances, unattached storage and oversized compute were consuming budget.
Resources were right-sized to usage, with monitoring to prevent future drift.
02 / Approach
Audit, right-size and monitor infrastructure.
Optimize usage before adding capacity. The audit identified idle instances, unattached storage and oversized compute, allowing the work to focus on resources that were consuming budget without matching actual demand.
Inventory everything
A comprehensive audit of all cloud resources across accounts, so every cost had an owner and a purpose.
Find the waste
Identified idle instances, unattached storage, oversized compute and redundant services.
Right-size to real usage
Matched infrastructure to actual usage patterns instead of peak guesses, with zero downtime or performance impact.
Keep it that way
Implemented monitoring to catch drift early, so savings did not erode after the engagement.
03 / Process
From inventory to monitored, right-sized infrastructure.
The work moved in one direction: see everything, remove what is not needed, size what remains to demand, and watch for drift.
- Inventory resources→
- Identify unused capacity→
- Right-size to usage→
- Monitor for drift
04 / Reported results
Lower running costs. No service disruption.
Monthly cost reduction
Reduction in monthly cloud costs after the infrastructure audit.
Downtime or performance impact
The case reports no downtime or performance impact during the change.
Drift monitoring post-engagement
Monitoring continued after the engagement to prevent infrastructure drift.
“We had no idea how much money we were leaving on the table. Software Sushi came in, audited everything, and within weeks we saw a 62% drop in our monthly AWS bill.”
About these results
These outcomes are reported in the published Software Sushi case study. The published account does not include the baseline dataset or measurement methodology.
- Monthly cost reduction: Published case study · Results
- Downtime or performance impact: Published case study · Results
- Drift monitoring post-engagement: Published case study · Results
05 / Delivery
What we delivered.
Resource inventory
A complete view of what was running across accounts.
Waste findings
Idle instances, unattached storage, oversized compute and redundant services, ready to act on.
Right-sized infrastructure
Resources aligned with actual usage, with no downtime.
Drift monitoring
Ongoing monitoring that continued after the engagement.
Tools and methods
- AWS
- Infrastructure audit
- Right-sizing
- Cost monitoring
You cannot optimize what you cannot see.
The largest savings came from visibility, not from new technology. An inventory first, then right-sizing, then monitoring keeps a cloud bill tied to the work it actually supports.
A useful first conversation
Is your AWS bill outgrowing your workload?
Let’s discuss your infrastructure, resource usage and opportunities to reduce waste.
