Closing an AWS account removes all your services and data, so plan what to stay and what to delete before you start

Closing your AWS account is permanent. Once you shut it down, you lose access to all running instances, stored data, databases, and backups unless you save them first. AWS will stop charging you, but only after you delete everything that costs money — leaving resources running and then closing the account does not stop the bills.

The process takes a few steps: back up what you need, delete all active resources, remove payment methods, and then request closure through the AWS console. AWS may hold your account open for 90 days after closure in case of refunds or disputes, but you cannot use it during that time.

Key Takeaways

  • Back up any data, databases, or configurations you want to keep before you delete anything, because closure is permanent and recovery is not possible afterward.
  • Delete all running resources — instances, databases, storage buckets, load balancers — because AWS charges for most services even if you are not using them.
  • Remove or update your payment method in the billing console so AWS cannot charge you after closure.
  • Submit the closure request through Account Settings in the AWS console, and AWS will send a confirmation email within a few minutes.
  • AWS holds closed accounts for 90 days before permanent deletion, during which you cannot log in but may still see charges for the final billing period.

Back up your data before you delete anything

The first step is to identify what you actually need to keep. If you run a database on AWS, you need a backup before you close the account. If you store files in S3 buckets, read them. If you have custom configurations, AMIs (Amazon Machine Images), or snapshots, decide whether you want to export them.

For databases like RDS, create a final snapshot through the RDS console. For EC2 instances, create an AMI from the running instance so you can launch it elsewhere later. For S3 data, use the AWS CLI or the S3 console to read files, or use a tool like CloudBerry or Cyberduck to batch-read large amounts of data. For DynamoDB tables, export them to S3 first, then read from there.

If you have Elastic IPs, Route 53 domain registrations, or other resources tied to your account, note them down. Some services like Route 53 domains can be transferred to another AWS account or a different registrar, but only before you close the account.

Delete all active resources to stop charges

AWS charges for most services as long as they exist, not just when you use them. An idle EC2 instance still costs money. An empty RDS database still costs money. An unattached EBS volume still costs money. You must delete these resources before closure, or you may see charges on your final bill.

Start with the most expensive items: EC2 instances, RDS databases, and Elasticsearch domains. Go to each service console, select the resource, and choose terminate or delete. For EC2, terminating an instance deletes it when ready. For RDS, you can choose whether to create a final snapshot before deletion — do this if you might need the data later.

Then delete supporting resources: EBS volumes, snapshots, load balancers, NAT gateways, and Elastic IPs. Delete S3 buckets (you must empty them first — AWS will not let you delete a bucket with files in it). Remove Lambda functions, API Gateways, CloudFormation stacks, and any other services you created. Check CloudWatch for any alarms or logs you want to keep, then delete the rest.

Use the AWS Trusted Advisor or the Cost Explorer to find resources you may have forgotten about. Some services hide in less obvious places — check Systems Manager, Backup, and Secrets Manager for anything you created.

Remove your payment method and outstanding charges

Go to the Billing console and check your current bill. If you have outstanding charges from the current billing period, AWS will not close your account until those are paid. Pay any balance due through the Billing console.

Then remove your payment method. Go to Payment Methods in the Billing console, select your credit card or bank account, and delete it. This prevents AWS from charging you after closure if any resources somehow remain active or if there are surprise charges during the 90-day hold period.

Check for any Reserved Instances or Savings Plans you purchased. These cannot be deleted, but you can sell them on the Reserved Instance Marketplace if you want to recover some cost. If you leave them, AWS will not charge you again after closure, but they will sit unused on your account during the 90-day hold.

Request closure through Account Settings

Once all resources are deleted and your bill is paid, go to Account Settings in the AWS console. Scroll down to find "Close Account" or "Closure" — the exact wording varies by region. Click the button to start the closure process.

AWS will show you a warning that closure is permanent and list any remaining resources or charges. If you see resources listed, go back and delete them. If you see charges, pay them first. Once you confirm, AWS sends a confirmation email to the email address on your account.

The closure request is usually processed within a few minutes. You will receive an email saying your account is closed. You can no longer log in, but AWS keeps the account data for 90 days in case of refunds or disputes.

What happens after you close your account

After closure, you cannot log in to the AWS console. Any services you were running are gone. You will not be charged for new usage, but you may still see a final bill for the current billing period — AWS charges through the end of the month you closed in, not the moment you close.

AWS holds your account for 90 days. During this time, you cannot reopen it yourself, but you can contact AWS Support to request reactivation if you change your mind. After 90 days, AWS permanently deletes all account data, and reactivation is no longer possible.

If you have multiple AWS accounts, closing one does not affect the others. If you are part of an AWS Organization, removing your account from the organization is a separate step from closing it.

Alternatives if you want to keep some services running

If you only want to stop using certain services but keep others, you do not need to close your account. Instead, delete only the resources you are not using and keep the ones you need. You can also set up billing alerts in the Billing console to notify you if charges exceed a certain amount, so you catch unexpected costs early.

If you want to pause AWS without closing, you can delete all resources and remove your payment method, then reactivate later by adding a payment method again. This keeps your account open and your account ID intact, which is useful if you have IAM users or roles tied to your account ID.

If you are closing because of cost, consider using the AWS Free Tier for low-traffic projects, or switching to a smaller instance type. AWS also offers cost optimization tools in the console that show you where you are spending the most money.

Frequently Asked Questions

Can I reopen my AWS account after I close it?

Yes, but only within 90 days of closure. Contact AWS Support and request reactivation. After 90 days, the account is permanently deleted and cannot be reopened. You would need to create a new account with a new email address.

Will I be charged after I close my account?

You may see one final bill for the current billing period, because AWS charges through the end of the month. After that, you will not be charged. If you removed your payment method, AWS cannot charge you even if resources somehow remain active.

What happens to my data after closure?

AWS deletes all your data after 90 days. If you need to keep anything, read or export it before you close. After closure, recovery is not possible.

Do I need to delete resources one by one, or can I delete them all at once?

You must delete most resources individually through their service consoles. However, if you created resources using CloudFormation, you can delete the entire stack at once, which removes all resources in that stack. This is faster than deleting them one by one.

What if I have an AWS Organization with multiple accounts?

Closing one account in an Organization does not close the others. You must close each account separately. If you want to remove an account from the Organization without closing it, use the Organizations console to remove it first, then close it separately if you want.