AWS Unexpected Charges: Why Is My AWS Bill So High?

Share
Ongoing Web console, CLI Updated November 13, 2026Based on 5 user reportsHow we research

Quick answer

Open Billing > Bills and Cost Explorer, group by Service then Region, and look for always-on items: NAT gateways, public IPv4 addresses, unattached Elastic IPs, EBS volumes and snapshots, load balancers. Terminate what you don't need and set a budget alert.

Most likely fix: Find the cost driver in Cost Explorer

How to fix it

Try these in order — the most common fix is first.

  1. 1. Find the cost driver in Cost Explorer

    1. Sign in as the root user or an admin with billing access
    2. Open Billing and Cost Management > Cost Explorer
    3. Group by Service, then by Region and Usage type
    4. Open Billing > Bills and expand the service with the largest charge
    Did this fix it?
  2. 2. Delete what is still running

    1. EC2 console > Instances: terminate unused instances in every region
    2. EC2 > Elastic IPs: release unattached addresses
    3. EC2 > Volumes and Snapshots: delete unused volumes (deleting a volume does not delete its snapshots)
    4. Delete load balancers before the instances behind them; terminate Elastic Beanstalk environments through Beanstalk, not EC2
    5. VPC > NAT gateways: delete unused gateways
    Did this fix it?
  3. 3. Set alerts so it can't happen silently

    1. Billing and Cost Management > Budgets > Create budget (cost budget, monthly)
    2. Add email alerts at 50% and 100% of your threshold
    3. Turn on Cost Anomaly Detection
    Did this fix it?
  4. 4. Ask AWS about charges you can't explain

    1. Open Support Center > Create case > Account and billing
    2. Basic support plan can open billing cases
    3. Describe the usage type and dates from the Bills page
    Did this fix it?

Symptoms

Your monthly AWS bill is much higher than expected, or you get a bill when you thought you were only experimenting.

Why it happens

  • NAT gateways ($0.045/hour plus $0.045 per GB processed)
  • Public IPv4 addresses billed $0.005/hour even when idle
  • Elastic IPs, EBS volumes and snapshots left behind after terminating instances
  • Load balancers or Elastic Beanstalk/OpsWorks environments that relaunch instances you stop
  • Resources in a region you forgot about or turned off
  • Data transfer out to the internet

This guide also covers

  • why is my aws bill so high
  • unexpected aws charges
  • aws surprise bill
  • aws charged me but i have nothing running

Still not working?

If AWS keeps failing, you're not alone. See every AWS problem users report or the alternatives people switch to.

We build software. Any software.

Paying for apps that don't quite fit? We build exactly what you need.

We're a small team of developers who build custom software fast. Not just tools like AWS: web and mobile apps, games, desktop software, AI tools, internal tools: whatever you have in mind. We build and run our own products too: booking platforms, games, learning apps. See our work

  • Web apps & SaaS
  • Mobile apps (iOS & Android)
  • Games
  • Desktop software
  • AI tools & automations
  • Internal tools & dashboards
  • Client portals & booking
  • Your own version of any tool
  • ✓ Free 15-min call to scope it
  • ✓ Price agreed up front
  • ✓ Your data, your code
Fixed it? Share this guide

The same problem in other apps

All billing, cancellation & refunds guides →

Other AWS errors

All 11 AWS errors and fixes →