I will audit your AWS or azure cloud bill and cut wasted spend
DevOps Engineer specializing in cloud cost optimization and Kubernetes
About this Gig
I audit cloud bills for a living, not as a side interest. At OYO I run 120+ node production Kubernetes across AWS, Azure and GCP.
WHAT I HAVE ACTUALLY DONE
- Cut 15,000 USD/month (about 180,000 a year) across 26 AWS accounts, zero service impact
- Cut 50 percent on a 90-instance Redis fleet by migrating it
- Upgraded Prometheus off a 2021 build with zero downtime
WHAT YOU GET
A report saying what you spend, what you can stop spending, and the risk of each change, in the order I would do them. A dollar figure on every line.
WHERE THE MONEY USUALLY IS
- Non-production sized like production
- Resources orphaned after a migration
- Instances sized on a guess and never revisited
- Data transfer and egress, always underestimated
- Commitment coverage that misses baseline usage
- Spend nobody can attribute, so nobody owns
WHAT I NEED
Read-only billing access only. AWS: read-only IAM role, or Cost Explorer plus CUR. Azure: Cost Management Reader. No workload, data or production access.
WHAT I WILL NOT DO
Recommend a change I cannot explain the risk of. Cost work that causes an incident is not a saving.
Tools:
Docker
•
GitHub
•
Azure Resource Manager
•
Kubernetes
•
Amazon EKS
Frameworks:
Terraform
Programming language:
Bash
•
Python
•
Golang
•
Rust
Expertise:
Migration
•
Debugging
•
Configuration
FAQ
Do you need access to our production systems?
No. Read-only billing data only for the audit. If you later want changes implemented, that is a separate conversation with properly scoped access.
How much will we actually save?
I will not promise a percentage before looking. Anyone who does is guessing. What I commit to: if I find less than my fee in credible annualised savings, I will tell you plainly rather than padding the report.

