Guides

How to Stop All AWS Billing and Close Your AWS Account Safely

By Ravindra Bagale, AWS & DevOps trainer · LinkedIn · Published: 16 October 2026 · Last updated: 17 October 2026

To stop all AWS billing, first read the bill: Billing and Cost Management → Bills shows every service that charged you, by region. Delete those resources in each region (EC2, EBS volumes and snapshots, Elastic IPs, NAT gateways, load balancers, RDS, EKS), and check Cost Explorer for two days. Then, if you want, close the account as the root user. You can reopen it within the 90-day post-closure period.

A live example first

A student in Nagpur finished an EKS lab in the Mumbai region and terminated the EC2 nodes. A week later, the bill still grew by about a dollar a day. Here is how we found it.

1. Open Billing and Cost Management → Bills, choose the current month, and expand Charges by service.

Amazon Elastic Compute Cloud          USD 5.10
  Asia Pacific (Mumbai)
    NAT Gateway hours                 USD 3.40
    EBS gp3 storage (unattached)      USD 0.96
    Public IPv4 address (idle EIP)    USD 0.74
Amazon Elastic Kubernetes Service     USD 0.00

2. The cluster was gone, but three things were left: a NAT gateway created for the private subnets, two EBS volumes from the persistent volume claims, and one Elastic IP.
3. In ap-south-1 we deleted the NAT gateway (VPC → NAT gateways), then released the Elastic IP it used, then deleted the two available EBS volumes.
4. Two days later, Cost Explorer showed zero for EC2 in the new days.

Friends, the bill is the truth. The console of one region does not show you the others.

Why do charges continue?

AWS bills each resource separately. Terminating an EC2 instance only stops the instance-hour charge. Its extra volumes, snapshots, IP addresses and anything the lab created around it (NAT gateways, load balancers, log groups) keep billing until you delete them. Resources can also sit in a region you forgot, for example us-east-1, the default region in many tutorials.

How do I stop all charges step by step?

1. Sign in and open Billing and Cost Management → Bills.
2. Note every service and region with a charge this month.
3. Open Resource Explorer (turn it on for all regions) or Resource Groups → Tag Editor with "All regions" and "All resource types".
4. Delete resources in this order:
   1. Auto Scaling groups (or they will start new instances).
   2. EKS clusters and their node groups, ECS services.
   3. EC2 instances (terminate).
   4. Load balancers and target groups.
   5. NAT gateways, then release Elastic IPs.
   6. RDS databases (choose whether to keep a final snapshot) and Aurora clusters.
   7. Unattached EBS volumes and old snapshots, and AMIs you created (deregister first).
   8. S3 buckets you do not need (empty, then delete).
   9. CloudWatch log groups with large storage, OpenSearch domains, Redshift clusters.
   10. Route 53 hosted zones (0.50 USD per month each) and any domain auto-renewals.
5. Check Savings Plans and Reserved Instances. These are commitments; they keep billing until the term ends.
6. Wait 24 to 48 hours and check Cost Explorer with daily granularity.

Costs people miss, by service

Close the account

When nothing is left:

1. Sign in as the root user (an IAM user cannot close the account).
2. Pay any unpaid bill.
3. Download anything you want to keep, such as invoices for tax.
4. Open the account menu (top right) → Account → scroll to Close account.
5. Read the notes, tick the boxes, and confirm.

After closing:

• The account enters a 90-day post-closure period. You can reopen it by contacting AWS Support.
• After 90 days, AWS permanently deletes the remaining content.
• You still receive the final bill for usage before closing.
• You cannot reuse the same email address for a new AWS account.

If your account is part of an AWS Organization, the management account closes member accounts from AWS Organizations instead.

Prevent it next time

1. Set a monthly budget of 1 or 5 USD with email alerts (billing alarm guide).
2. Turn on Cost Anomaly Detection (free).
3. Tag every lab resource with project=lab-xyz and delete by tag.
4. Use Terraform or CloudFormation for labs, then run terraform destroy or delete the stack.

Real example

AWS introduced a charge for all public IPv4 addresses from 1 February 2024 (0.005 USD per IP per hour), including ones attached to running instances. Many learners who left a few Elastic IPs or old load balancers around saw small new charges on their bills. It is a good reminder to check the bill every month, even when you think nothing is running.

Summary table