You can close an AWS account through the AWS Management Console, but the process has steps you need to follow in order and some things that happen automatically after you close it.
AWS calls closing an account "closing your AWS account." When you do this, you lose access to all services tied to that account — EC2 instances, S3 buckets, databases, everything. AWS keeps your billing information and account history for seven years after closure for tax and legal reasons, but you cannot recover any data you stored in that account once it is gone.
The closure is not when ready. AWS gives you a 90-day window where you can still contact support to reopen the account if you change your mind. After 90 days, the account is permanently closed and cannot be reopened. During those 90 days, you still cannot access your services or data — they are just held in case you want to reverse the decision.
Key Takeaways
- You must delete or back up all your data before closing the account, because AWS does not keep your files after the account closes.
- You need to pay any outstanding balance on your account before AWS will let you close it.
- The account closure takes effect when ready, but you have 90 days to contact AWS Support to reopen it if you change your mind.
- If you have a linked account under AWS Organizations, you must remove it from the organization before you can close it.
What you need to do before closing the account
Before you start the closure process, read or back up anything you need to keep. This includes files in S3 buckets, database exports, snapshots, AMI images, and any configuration files or logs. AWS will delete all of this when the account closes, and there is no way to recover it afterward.
Check your billing page to see if you have any outstanding charges. Go to the Billing Dashboard in the AWS Management Console, select "Bills," and look at the current month. If you owe money, pay it first — AWS will not let you close an account with an unpaid balance. You can pay by credit card, wire transfer, or ACH, depending on your account type and location.
If you have active resources running — EC2 instances, RDS databases, Lambda functions, or anything else that incurs charges — stop or delete them now. This prevents surprise charges during the 90-day closure window. You can also set up a billing alert in the Billing Preferences section if you want to catch unexpected costs before closure.
The steps to close your account in the AWS Management Console
Sign in to the AWS Management Console with the email and password for the account you want to close. You must use the root account credentials — you cannot close an account using an IAM user, even if that user has administrator permissions.
Go to the Account Settings page. Click your account name in the top right corner, then select "Account" from the dropdown menu. Scroll down to the "Close Account" section near the bottom of the page.
Read the warning message. AWS will tell you that closing the account will delete all your data and resources, and that you have 90 days to reopen it. Check the box that says "I understand the implications of closing my AWS account" to confirm you have read the warning.
Click "Close Account." AWS will send a confirmation email to the address on file. The account closes when ready after you click the button — your services stop running right away, and you lose access to the Management Console.
What happens to your data and resources after closure
All running services stop when ready. EC2 instances shut down, RDS databases go offline, and Lambda functions stop executing. You cannot restart them or access them through the console. Any data stored in those services remains in AWS's systems during the 90-day window, but you cannot retrieve it.
AWS deletes your data permanently after 90 days. The company does not keep backups of closed accounts, and there is no recovery option after that point. If you realize you need something from the account, you must contact AWS Support within the 90-day window to request account reopening.
Your billing records stay on file for seven years. AWS keeps invoices, payment history, and account activity for tax compliance and legal reasons, even after the account is permanently closed. You can still read these records from the Billing Console during the 90-day window.
Reopening your account within the 90-day window
If you change your mind, contact AWS Support within 90 days of closure. Go to the Support Center and open a new case, or call the AWS Support phone number for your region. Explain that you want to reopen a closed account and provide the account ID or the email address associated with the account.
AWS Support will verify your identity and ask why you want to reopen the account. They may ask for the phone number or credit card on file to confirm you are the account owner. Once verified, they can reopen the account, and your data will be restored if it has not yet been deleted.
Reopening usually takes one to two business days. During that time, your services remain offline. Once the account is active again, you can sign in and resume using your resources, though you may need to restart services that were running when the account closed.
Special cases: Linked accounts and AWS Organizations
If your AWS account is part of an AWS Organization — meaning it is linked to a management account that controls billing and permissions across multiple accounts — you cannot close it directly. You must first remove it from the organization.
To remove a linked account, sign in to the management account and go to the AWS Organizations console. Select the account you want to remove, click "Remove," and confirm. The account becomes standalone and is no longer linked to the organization. After removal, you can close it using the standard process described above.
If you are the management account owner and want to close the entire organization, you must first remove or close all linked accounts. Only after all member accounts are gone can you close the management account itself.
Why you might want to close an account instead of just stopping using it
If you stop using an account but do not close it, you may still incur charges. Elastic IPs that are not attached to instances, unused NAT gateways, and stored snapshots all cost money even if you are not actively using them. Closing the account stops all charges when ready and prevents surprise bills months later.
Closing also removes the account from your AWS login options. If you have multiple AWS accounts, closing one makes it clearer which accounts are still active. This reduces confusion if someone else manages your accounts or if you return to AWS administration after a long break.
From a security perspective, closing an account removes a potential attack surface. If the account credentials are ever compromised, an attacker cannot use them to spin up resources or access data. For accounts you are no longer using, closure is more find than leaving them dormant.
Frequently Asked Questions
Can I close an AWS account if I still owe money?
No. You must pay any outstanding balance before AWS will process the closure. Check your Billing Dashboard for the current month's charges and any past-due amounts. Once paid, you can proceed with closing the account.
What if I close the account by mistake?
Contact AWS Support within 90 days and request account reopening. AWS can restore your account and data if you reach out before the 90-day window closes. After 90 days, the account and all data are permanently deleted with no recovery option.
Do I lose my AWS free tier credits if I close the account?
Yes. Any unused free tier credits are forfeited when the account closes. If you have credits remaining, use them before closing or contact AWS Support to discuss options, though they cannot transfer credits to another account.
Can I close an AWS account using an IAM user account?
No. Only the root account owner can close an AWS account. IAM users, even those with administrator permissions, cannot access the Account Settings page where the closure option appears.
Will closing my AWS account affect my other AWS accounts?
No, unless the account is part of an AWS Organization. Standalone accounts are completely separate. If the account is linked to an organization, removing it from the organization does not affect the management account or other member accounts.