You are probably paying for cloud resources you forgot about. Here is how to find them in your own billing CSV in about five minutes.
AWS does not bill you for "waste" — it bills you for resources that exist. The problem is that most waste is forgotten infrastructure: a load balancer left running after a service was deleted, an EBS volume orphaned when its instance was terminated, an Elastic IP nobody uses anymore. None of it shows up in your daily work, but all of it shows up on the invoice.
The good news: almost all of it is findable in the CSV you can already export from the AWS Billing Console. You do not need a paid platform to start.
These are the six patterns a typical Cost Explorer export will reveal. We use the same list in our free scanner.
When you terminate an EC2 instance but forget its attached EBS volume, the volume keeps billing you per GB-month. These show up as unattached, orphaned, or no-instance line items.
Fix: identify unattached volumes in EC2 → Volumes, snapshot what you need, then delete the rest.
Many instances run at 5–15% CPU but sit on a c5.4xlarge or r5.2xlarge because someone "picked a safe size." The difference between right-sized and oversized can be 4–10x in cost.
Fix: check CloudWatch CPU utilization; downsize to a smaller family or use burstable t3/t4g instances where usage is spiky.
An Application Load Balancer costs a fixed hourly rate whether it serves 1 request or 1 million. After a project is retired, the ALB often keeps running with near-zero traffic.
Fix: cross-check ALBs against actual request counts; delete those with no meaningful traffic.
Snapshots older than 90 days that no longer back up an active instance are pure storage cost. They accumulate quietly because deletion is never urgent.
Fix: apply a retention policy (e.g. keep 30–90 days), delete snapshots with no associated running instance.
AWS charges for every Elastic IP that is not associated with a running instance. A "just in case" IP costs you every month for doing nothing.
Fix: release any EIP with no attached resource. They are free only while bound to a live instance.
Data that is rarely accessed but stored in the Standard tier could move to Infrequent Access or Glacier at a fraction of the price. This is common in S3 buckets and old EBS snapshots.
Fix: enable Intelligent-Tiering or lifecycle policies to auto-move cold data to cheaper tiers.
Product/Line Item column for the keywords above: unattached, IdleAddress, SnapshotUsage, ELB, oversized instance types.Doing it by hand works, but it is easy to miss items in a 200-line export. That is exactly why we built a free scanner.
CloudSaver reads your AWS billing CSV in your browser, flags all 6 waste patterns, and shows what you can recover. No signup, no upload to a server.
Scan my AWS bill free →It is the industry estimate from Flexera's State of the Cloud report (2026), based on surveys of hundreds of cloud decision-makers. Individual accounts vary, but the range is widely cited across Gartner, IDC and CloudZero as well.
No. The patterns above are visible in the CSV you can export today. A free scanner just speeds it up and catches items you might miss by hand.
With CloudSaver, the CSV is processed locally in your browser and is never uploaded to a server. Check the privacy policy of any tool you use.