AWS Cost Optimization Audit
A full inventory sweep of your AWS accounts, ending in a ranked remediation plan.
- Turnaround
- 5–7 business days
- Who it is for
- Teams on AWS with spend growing faster than traffic.
01 — The problem
AWS Cost Explorer tells you what you spent. It does not tell you that your queue workers should be Spot, that cross-AZ traffic is accidental, or that half your gp2 volumes should have been gp3 two years ago.
02 — What is included
Exactly what you get, and nothing vague.
- Account-wide inventory: orphaned volumes, unattached Elastic IPs, idle RDS, forgotten snapshots
- Instance right-sizing against actual CloudWatch utilisation, not nameplate specs
- Graviton and ARM migration candidates, with the compatibility caveats stated
- Commitment modelling: Reserved Instances vs Savings Plans vs Spot, with projected ROI
- Executive summary plus a line-by-line engineering backlog
03 — What this usually finds
The recurring ones, named up front.
- gp2 volumes that should have been gp3 since 2021
- Non-production environments running 24/7
- Over-provisioned RDS instances sized for a launch that never came
- Snapshot sprawl with no lifecycle policy
Listed because they recur, not because they are guaranteed. The audit reports what is actually there.
Next step
Twenty minutes to find out whether this is worth doing.
Every engagement runs under a signed mutual NDA with a read-only IAM role. If the audit would not pay for itself, I will say so on the call.