How to Delete Your AWS Account: A Complete Step-by-Step Guide

Closing an Amazon Web Services account isn't as simple as clicking a single "delete" button. AWS has a deliberate, multi-step process designed to prevent accidental closures — which makes sense given that businesses often run critical infrastructure through the platform. Understanding what actually happens when you close an account, and what you need to do beforehand, determines whether the process goes smoothly or leaves you with unexpected charges and data loss.

What "Closing" an AWS Account Actually Means

When you close an AWS account, Amazon doesn't delete it instantly. Instead, the account enters a post-closure period — typically 90 days — during which your resources are suspended but not yet permanently removed. During this window, you can contact AWS support to reopen the account if needed.

After that 90-day period, AWS permanently deletes all remaining resources, content, and data associated with the account. This deletion is irreversible. Once the window closes, there is no recovery path.

It's also worth knowing that the email address tied to a closed account cannot be reused to create a new AWS account, at least for a period of time. If you plan to open a fresh account later, use a different email from the start.

Before You Close: The Checklist That Actually Matters ✅

Skipping preparation is where most people run into trouble. AWS will still bill you for resources that were active during the billing cycle, even after closure is initiated.

Terminate all active resources first:

• EC2 instances — stop and terminate every running instance
• RDS databases — delete database instances and snapshots you don't need
• S3 buckets — empty and delete all buckets (you're billed for stored objects)
• Lambda functions, ECS clusters, EKS clusters — remove these if active
• Elastic IPs — release any allocated Elastic IP addresses, which incur charges even when unattached
• CloudFront distributions — disable and delete distributions
• Route 53 hosted zones — delete hosted zones to avoid recurring charges

Download or migrate any data you want to keep. Once the account closes and the 90-day window passes, data is gone permanently. This includes S3 objects, database backups, CloudWatch logs, and anything else stored in AWS services.

Settle your billing:

• Pay any outstanding balance on your account
• Review your current month's usage — AWS generates a final bill after closure
• Remove or update any saved payment methods if needed after the process

Check for active Reserved Instances or Savings Plans. These don't automatically refund when you close an account. Depending on the terms, you may still owe remaining payments or forfeit prepaid costs. Review your commitments in the Billing Dashboard before proceeding.

Notify dependent services. If other applications, third-party tools, or team members access resources through this account, closing it will break those connections immediately.

How to Close Your AWS Account: The Actual Steps

1. Sign in to the AWS Management Console using your root account credentials — not an IAM user. AWS requires root access to close an account.

2. Navigate to the top-right corner, click your account name, and select Account.

3. Scroll down to the Close Account section at the bottom of the Account Settings page.

4. Read the acknowledgments carefully. AWS lists what will happen — resource termination, data deletion, billing finalization.

5. Check all the acknowledgment boxes. These confirm you understand the consequences: data loss, final charges, and the inability to reuse the email address.

6. Click Close Account and confirm.

AWS will send a confirmation email to the root account's email address. Keep this for your records.

Multi-Account Environments: AWS Organizations 🏢

If your account is a member account inside an AWS Organization, the closure process has an additional layer. Member accounts can be closed either by the member account holder (using the steps above) or by the management account through the Organizations console.

The management account itself cannot be closed while it still has active member accounts. You must first remove or close all member accounts before closing the management account.

For teams managing multiple accounts, this sequencing matters — closing accounts out of order can cause access and billing complications across the organization.

What Varies Between Users

The straightforwardness of account closure depends heavily on a few factors:

Someone running a personal account with a single EC2 instance can close their account in under an hour. A business account with dozens of services, multi-region deployments, active Reserved Instances, and team access involves significantly more preparation — potentially days or weeks to wind down cleanly.

The 90-Day Window and Final Billing

After closure, your account dashboard may still be accessible during the post-closure period, but you won't be able to launch or use services. AWS will process a final invoice for any usage accrued up to the closure date. This bill arrives on your next regular billing cycle date.

If there are resources AWS couldn't automatically terminate (which can occasionally happen with certain configurations), those may continue to generate charges during the post-closure window. Monitoring your email during this period for any AWS billing notifications is worth doing.

The specific resources you were running, your reserved commitments, and how thoroughly you cleaned up before closing are the factors that determine what your final bill looks like — and those details vary significantly from one account to the next.