Your AWS bill has dead branches. We find them for a fixed $2,400.
Oversized instances, half-empty Kubernetes nodes, unattached volumes, NAT gateway traffic, staging running all weekend. A fixed-price audit with read-only access tells you what to cut and what each cut saves, and ships the quick wins as Terraform pull requests.
What one finding looks like
EBS volumes still on gp2
- Evidence
- Volume IDs, sizes and IOPS from
describe-volumes - AWS list price
- gp3 is 20% cheaper per GB-month than gp2 ($0.08 vs $0.10 in AWS's example)
- Effort and risk
- Low. Volumes over 1 TiB need provisioned IOPS to match.
- Fix
- Terraform PR:
type = "gp3" - Monthly saving
- Computed from your own bill
What the audit looks at
The same twelve places come up again and again. None of them needs a re-architecture. The guide to the twelve cuts shows how to check each one yourself.
- Instances, databases and nodes sized for a peak that never comes
- Staging and dev environments running nights and weekends
- Unattached EBS volumes and forgotten snapshots
- NAT gateway traffic that should go through free gateway endpoints
- gp2 volumes that could be gp3
- Savings Plans coverage, and commitments that no longer fit
- Workloads that could run on Spot
- x86 instances that could move to Graviton
- S3 buckets with no lifecycle rules
- CloudWatch log groups kept forever
- Public IPv4 addresses nobody uses
- EKS clusters paying for extended support
Three ways to work together
Start with the free review. The audit only makes sense if the savings are there, and you will hear it if they aren't. Prices in USD, excluding taxes.
Free bill review
$0 20 minutes
- A call over a Cost Explorer screen share, or async from an exported CSV
- The areas most worth a closer look
- A straight answer on whether the audit is worth $2,400 to you
Cost audit
$2,400 fixed price
- Read-only IAM access, nothing changed in your account
- Written report: each saving with its monthly amount, effort and risk
- Savings ranked by priority
- Terraform pull requests for the quick wins
- Delivered in 10 business days, with a walkthrough call
Implementation days
Optional day rate quoted with the report
- For the larger items: rightsizing, Spot, Graviton, Savings Plans, Kubernetes requests
- Everything goes through your Terraform and your pipelines
- Book as many or as few days as you need
How the audit runs
- Day 1: you create a read-only role. You get the exact IAM policy in advance: describe, list and billing read. No write access, no access to application data.
- Days 2 to 8: analysis. Three months of Cost and Usage data, actual resource utilization, EKS clusters, databases, storage and network paths.
- Day 9: pull requests. The quick wins land as Terraform PRs in your repository, one change per PR, each with its expected effect in the description.
- Day 10: report and walkthrough. The written report, ranked by priority, and a call to go through it. Then you revoke the role.
Who does the work
Amine, a freelance DevOps engineer based in France, in the EU. AWS, Google Cloud, Azure, Kubernetes and Terraform every day. You deal with one person from the first review to the last pull request, in English.
No savings percentages are promised up front: every number in the report comes from your own bill and AWS's public prices.
Frequently asked questions
How much does the AWS cost audit cost?
$2,400, fixed, in USD and excluding taxes. The price is the same whatever the size of the bill. The 20-minute bill review before it is free.
What access do you need to our AWS account?
A read-only IAM role that you create and can revoke at any time. You get the exact policy before you create it. It can list and describe resources and read billing data; it cannot change anything.
What do the Terraform pull requests cover?
The quick wins that are low risk and easy to review: for example gp2 to gp3 volumes, CloudWatch Logs retention, S3 lifecycle rules, and gateway endpoints for S3 and DynamoDB. You review and merge them; nothing is applied for you.
Does the audit cover Kubernetes and EKS?
Yes: node utilization, pod requests compared with real usage, Karpenter or autoscaler settings, and clusters that are paying for EKS extended support.
We don't use Terraform. Is the audit still useful?
Yes. The report is the same. The quick wins then come as a written change list with the exact AWS CLI commands instead of pull requests.
Can you work with a team in the US, the UK or Australia from France?
Yes. The audit is mostly asynchronous: read-only access, a written report, pull requests. The kickoff and the walkthrough calls are scheduled in overlapping hours.
Ask for the free bill review
Written reply within one business day. No sales sequence.
Sent. You will get a written reply within one business day.