AWS Tutorials

How to Avoid Unexpected AWS Charges as a Beginner

Avoid surprise AWS bills: set budgets and alerts, check every Region, stop what you don't need, and learn which resources keep billing after you stop them.

On this page
  1. Short answer
  2. Why surprise charges happen
  3. Step 1: Set a budget with alerts
  4. Step 2: Turn on billing and Free Tier alerts
  5. Step 3: Know your Free Tier plan
  6. Step 4: Check every Region
  7. Step 5: Know what keeps billing when you stop things
  8. Step 6: Set a log retention period
  9. Step 7: Review Cost Explorer each week
  10. Clean-up checklist
  11. If you get an unexpected bill
  12. Protect your account from leaked keys
  13. Next steps

Short answer

Set up budget alerts before you create anything. Check every Region for leftover resources, and delete what you no longer need. Remember that a few resources keep billing even when they are stopped, including EBS volumes, Elastic IPs, snapshots and RDS storage.

Why surprise charges happen

Most surprises come from a short list of resources that bill by the hour, even when they sit idle:

Resource Rough cost Why it surprises people
NAT gateway About $0.045 per hour (roughly $33 a month), plus data charges Created by some VPC setups and easy to forget
Public IPv4 address About $0.005 per hour each, since February 2024 Charged even when attached to a stopped instance
Load balancer About $0.0225 per hour (roughly $16 a month), plus capacity Keeps billing with no traffic
EKS control plane $0.10 per hour per cluster Runs whether or not any pods exist
RDS instance Instance hours, plus storage and backups Storage and backups keep billing when the instance is stopped
EBS volume and snapshots Storage by the GB-month Survives after the instance is terminated

Prices are for us-east-1 at the time of writing and change over time.

Step 1: Set a budget with alerts

In the Billing and Cost Management console, open Budgets and create a monthly cost budget. Set alerts at 50%, 80% and 100% of your target. Include both actual and forecasted spend, and send the alerts to your email.

A budget only sends alerts by default. It does not stop anything. Budget data also refreshes only a few times a day, so an alert can arrive hours after the spending happened. Budgets can also run actions, such as applying a restrictive policy or stopping EC2 or RDS instances, but set that up deliberately.

Step 2: Turn on billing and Free Tier alerts

In Billing and Cost Management, open Billing preferences and turn on:

  • Free Tier alerts, which warn you when your usage approaches the free allowance.
  • Billing alerts, which you need before you can create CloudWatch billing alarms.

CloudWatch billing alarms exist only in the us-east-1 Region, so create them there.

Also turn on Cost Anomaly Detection. It watches your spending pattern and alerts you to sudden changes. It is free to use.

Step 3: Know your Free Tier plan

AWS changed the Free Tier in July 2025. New accounts choose one of two plans:

  • A Free plan, which comes with credits and is designed to stop before charges apply.
  • A Paid plan, which bills for usage beyond the free allowance, with no hard spending cap.

Accounts created before July 2025 keep their earlier free offers, which generally run for 12 months. Check your plan and remaining credits in the Billing console. The phrase “Free Tier” alone does not tell you whether your account can be charged.

Step 4: Check every Region

Resources are created in one Region at a time, and the console shows only the Region you are in. A forgotten instance in another Region still bills. Use Tag Editor or Resource Explorer to search across Regions. Check each Region where you have worked, especially those you used only once.

Step 5: Know what keeps billing when you stop things

Stopping and terminating are different:

  • Stopping an EC2 instance stops the compute charge. The EBS volumes and any Elastic IP still bill.
  • Terminating an EC2 instance removes the instance. Extra EBS volumes, snapshots and Elastic IPs can remain, so check them.
  • Stopping an RDS instance does not stop storage or backups from billing. RDS also starts a stopped instance again automatically after seven days.
  • Snapshots persist after the source is deleted, until you delete the snapshot itself.

Step 6: Set a log retention period

CloudWatch Logs keeps log data indefinitely by default. Set a retention period, such as 7 or 30 days, on each log group you no longer need. Logs from Lambda functions, ECS tasks and EKS clusters are common sources of storage costs.

Also check the small recurring fees. Secrets Manager charges about $0.40 per secret per month, a customer managed KMS key costs about $1 per month, and each Route 53 hosted zone costs $0.50 per month.

Step 7: Review Cost Explorer each week

Open Cost Explorer once a week. Group the chart by service, then by Region. Look for services you did not expect, and for steps up in cost. A short weekly review catches small problems before they grow.

Clean-up checklist

Run this list after each practice project:

Check Where to look
EC2 instances stopped or terminated EC2 console, in every Region
EBS volumes, snapshots and Elastic IPs removed EC2 console, under Volumes, Snapshots and Elastic IPs
NAT gateways and load balancers deleted VPC and EC2 consoles
RDS instances and snapshots deleted RDS console
EKS clusters and their load balancers deleted EKS and EC2 consoles
CloudWatch log groups have a retention period CloudWatch console
Budget alert and Free Tier alerts on Billing console

If you get an unexpected bill

  1. Open Bills and Cost Explorer to find the service and Region behind the charge.
  2. Delete or stop the resource that causes it.
  3. If you believe the charge is a mistake, open a support case in the Billing category.

AWS may credit some charges as a courtesy, but that is at its discretion. Do not assume a refund. Public forum threads show mixed outcomes, so keep the alerts and the clean-up routine in place from the start.

Protect your account from leaked keys

Charges can also come from someone else. Leaked access keys are sometimes used to run cryptocurrency mining, which can produce very large bills quickly.

  • Turn on multi-factor authentication (MFA) for the root user.
  • Do not create access keys for the root user.
  • Do not commit access keys or .env files to Git. Use IAM roles where you can.
  • Rotate any key that may have leaked, and remove keys you no longer use.

Next steps

The complete guide to aws tutorials

AWS Fundamentals: The Core Cloud Computing Services
Read the guide

Keep exploring

Guides from other topics

All topics →