Blog / AWS Cost Cleanup

My Brother Couldn’t Find the Source of His $180/Year AWS Bill

By Saurav Sharma||5 min read

My brother was paying about $180 a year to AWS and struggling to find what was still charging him. He was getting frustrated trying to track down the resources and stop the bill.

That’s about $180 a year for an old setup he no longer wanted. The charges were spread across a server, its public IP, disks, and snapshots. He wanted to find them all and finish the cleanup.

I did a quick cleanup for him with Codex as an AI agent. We checked the bill, found the resources behind it, removed the approved resources, and verified they were gone. I can help you do the same.

An AWS account can start with a tutorial, a side project, or a few services you wanted to try. Months later, the bill is still arriving, but you no longer remember everything you created or which region you put it in. If you rarely use AWS, even working out where to look can take time.

Deleting an EC2 instance can be straightforward once you know which one it is and that you no longer need it. Tracing every charge and deciding what is safe to remove takes more context. Another account might have costs coming from an unfamiliar database or networking service, or storage left behind by an old experiment. That is where a guided cleanup helps: we follow the bill to the resources, check what they are for, and agree on what can go.

AWS bill cleanup: $150 for a 55-minute working session. We trace the charges, remove unused resources you approve, and check what remains. Book your bill cleanup at cloudyeti.io/meet

What was behind his monthly bill

The actual October bill was $14.61 including tax. At that same monthly amount, that would be $175.32 over a year. The $15/month and $180/year figures are rounded examples, not a claim that every month costs exactly the same.

October 2026 charges, rounded to cents
What was charging himMonthly cost
One running t2.micro EC2 instance$8.63
Its public IPv4 address$3.72
Two 8 GB gp3 disks$1.28
Five snapshots$0.15
Tax$0.83
Total$14.61

The server had been launched in November 2023 and was still running. One disk was attached to it. Another disk was unattached and still costing money. All five snapshots were also from November 2023.

How I used an agent to clean it up

The agent used AWS billing data to break down costs by service, usage type, and region. That gave us specific resources to investigate instead of guessing from the total.

  1. Trace the bill. Match the billed services to the actual server, public IP, disks, and snapshots.
  2. Approve the cleanup. Confirm the resources and their data are no longer needed before deleting them.
  3. Remove the resources. Terminate the instance, delete the disks and snapshots, and deregister the saved machine image. Terminating this instance also released its automatically assigned public IP.
  4. Verify the result. Check the resource inventories again, including other enabled regions.
  5. Remove temporary access. Delete the investigation access key and verify that AWS rejects it.

For this account, we made 136 inventory checks across eight resource categories in all 17 enabled regions. Those checks found no remaining resources in those categories. We also checked S3 buckets, CloudFront distributions, and Route 53 hosted zones.

The resources behind his recurring bill were gone. That stopped their ongoing costs. Charges already incurred still apply, and AWS billing data takes time to catch up. This was a cleanup of an old setup, not a promise that every AWS account can or should cost $0.

The IP address he thought was free

One surprise was the public IP. AWS currently charges $0.005 per hour for an AWS-provided public IPv4 address, whether it is in use or idle. The rate is listed on the official Amazon VPC pricing page.

His October charge matched exactly: one address × 744 hours × $0.005 = $3.72. The server did not need to receive traffic for that address to cost money.

I can do this with you for $150

For $150, I’ll help clean up unused resources in your AWS account in a session that fits within an hour. Book the 55-minute slot at cloudyeti.io/meet and mention “AWS bill cleanup” when booking.

  • Review one AWS account and identify the services behind the charges.
  • Find unused resources that can be removed during the session.
  • Delete only the resources you approve, with agents helping with the investigation and execution.
  • Verify what was removed and explain any costs that remain.

This is a good fit for an old test account, abandoned experiments, or a small setup with charges you do not understand. You stay in control of access and deletion decisions. Do not send passwords or access keys through the booking form.

A production migration, a multi-account investigation, or resources whose ownership is unclear may need more time. We agree on the work before changing anything. If we cannot finish within the session, you get the findings and remaining steps. Further work is scoped separately.

When does the session pay for itself?

The useful number is how much recurring cost we can actually remove. Your total bill alone does not tell us that. A $500 bill could be fully needed, while a much smaller account could contain nothing but abandoned resources.

Illustrative payback if these monthly savings are achieved and continue
Monthly cost removedAnnual savingsTime to recover the $150 fee
$15$18010 months
$25$3006 months
$50$6003 months
$100$1,2001.5 months

If we remove $50 a month, the $150 session pays for itself in three months. At $15 a month, it takes ten months. Those are examples, not guaranteed savings. Your time and the frustration of an unresolved bill also matter.

Book your AWS bill cleanup

My brother wanted someone to trace the charges and finish the cleanup with him. If that sounds familiar, book a session and tell me what is still charging you.

AWS bill cleanup: $150 for a 55-minute working session. We trace the charges, remove unused resources you approve, and check what remains. Book your bill cleanup at cloudyeti.io/meet