Who it is for
A startup or agency spending $500-5,000 a month on AWS, with nobody whose job is cost. The bill grew with every project, and nobody is sure which resources are still needed.
The problem
- Resources outlive the projects that created them: unattached disks, load balancers with no targets, idle NAT gateways, instances stopped for months but still paying for storage.
- Defaults cost money: gp2 disks, logs kept forever, previous-generation instance types.
- Nobody has time to check every region by hand, and fear of breaking something stops the clean-up.
What I do
- A read-only IAM role that you create and can revoke at any time. The tool cannot change anything.
- 12 waste checks across every enabled region, each with a monthly saving estimate and a risk level.
- A ranked report with the exact command for every fix. Commands that delete something take a snapshot or image first and wait for it.
- Budgets and anomaly alerts, so the bill can't drift back unnoticed.
How it works
- 1Read-only role (you create it)
- 2Scan: 12 checks, every region
- 3Ranked report: saving, risk, fix
- 4Safe fixes together, with approval
- 5Budgets and anomaly alerts
- 6Re-scan after 30 days
Day by day
- Day 1You create the read-only role from a template (CloudFormation or Terraform). I run the scan across every region.
- Day 2I check each finding against Cost Explorer and your context, remove false alarms, and write the report.
- Day 3Walkthrough call. We apply 3-5 low-risk fixes together; you approve every command.
- Day 4-5Budgets and anomaly alerts, a short handover note, and you revoke my access.
- +30 daysA second scan to confirm the savings held and nothing new crept in.
Evidence from the demo
The evidence below comes from my own demo project with synthetic data. It shows exactly what you receive; it is not a story about a client.
- On a synthetic demo account (simulated with moto), the scan finds 20 issues worth $616.37 a month: 4 high, 7 medium, 5 low and 4 informational.
- Every finding carries the exact AWS CLI command, and the sample report prints cleanly to PDF.
- 46 automated tests, including one that records every API call of a full scan and proves the client's read-only policy covers it.
Demo project: AWS Bill Doctor kit (cost + security)
What you keep
- HTML and PDF report ranked by monthly saving
- 3-5 fixes applied with you
- Budgets and anomaly alerts
- A second scan after 30 days
Not included
- Re-architecting applications or buying Savings Plans for you (advice only)
- Any change without your explicit approval
Questions
Do you need access to my production systems?
No passwords, ever. Audits use a read-only role you create and can delete at any time; changes arrive as a pull request you review and merge yourself.
How long does a project take?
2 to 10 working days depending on the package. You get the timeline and the fixed price before we start.
What if you find nothing worth fixing?
Then you hear that early, with the evidence. For the AWS Bill Doctor on accounts above $1,000 a month: if I don't find at least my fee in yearly savings, you don't pay.
What happens to my data?
Reports stay between us. When the project ends I delete your data and confirm it in writing.
How do I pay?
Upwork, international bank transfer, or UPI / bank transfer in India. Direct clients pay 50% upfront and 50% on delivery.