How to Delete an AWS Account: What You Need to Know Before You Close It

Deleting an AWS account is a permanent, irreversible action — and Amazon makes that intentional. Unlike unsubscribing from a newsletter or deactivating a social media profile, closing an AWS account triggers a cascade of effects across every service, resource, and piece of data tied to that account. Understanding exactly what happens, what's required beforehand, and where the process can get complicated is essential before you click anything.

What "Deleting" an AWS Account Actually Means

AWS uses the term account closure rather than deletion. When you close an AWS account, Amazon retains certain account data for a period of time for legal and billing purposes — but your access to AWS services ends, your resources are terminated, and you cannot reopen the account.

Crucially, your email address remains associated with the closed account for a period after closure. This means you may not be able to immediately reuse that email to create a new AWS account, depending on timing.

Before You Can Close an AWS Account: The Prerequisites ✅

AWS enforces several conditions before it will allow account closure. Skipping any of these will either block the process or leave you with unexpected charges.

1. Cancel All Active Services and Resources

Every running resource — EC2 instances, RDS databases, S3 buckets, Lambda functions, Elastic IPs, load balancers — must be manually terminated or deleted. AWS will not automatically clean these up for you. Resources left running continue to generate charges even during the closure process.

Key areas to audit:

• EC2 instances and associated EBS volumes
• S3 buckets and all objects inside them
• RDS and other database instances
• Reserved Instances or Savings Plans (these have financial commitments)
• Route 53 hosted zones
• CloudFront distributions
• Any active Marketplace subscriptions

2. Pay Any Outstanding Balance

AWS requires a zero outstanding balance before an account can be closed. If your billing cycle hasn't closed yet, you may need to wait until the final invoice generates and is settled. Accounts with unpaid balances will not be eligible for closure.

3. Remove Payment Methods (Optional but Recommended)

After confirming your balance is clear, it's good practice to verify your payment method details before proceeding, though AWS handles billing finalization as part of the closure process.

4. Address Organizations Membership

If your account is a member account in AWS Organizations, it must be removed from the organization before it can be closed — or the management account must close it from within the Organizations console. Closing a management account while member accounts still exist is blocked entirely; all member accounts must be closed or removed first.

The Actual Closure Process

1. Sign in to the AWS Management Console as the root user — not an IAM user. Only the root user of an account can initiate closure.
2. Navigate to Account Settings (found under your account name in the top-right menu, then "Account").
3. Scroll to the bottom of the Account page to find the Close Account section.
4. Read and acknowledge the listed checkboxes confirming you understand the consequences.
5. Confirm closure.

🔒 Root user access is mandatory. If you've lost access to the root user email or MFA device, you'll need to go through AWS Support to recover access before closure is possible.

What Happens After You Close the Account

During the 90-day post-closure period, AWS may still allow account reactivation if you change your mind — though this is not guaranteed and depends on account standing.

Common Complications That Slow Down Closure

Reserved Instances and Savings Plans are binding financial commitments. Closing an account doesn't cancel these obligations — you may still owe charges for the commitment term, or need to sell Reserved Instances on the AWS Marketplace before proceeding.

Third-party Marketplace subscriptions must be individually cancelled through the AWS Marketplace console. These don't auto-terminate on account closure.

Cross-account dependencies — if other AWS accounts reference resources in your account (shared AMIs, cross-account IAM roles, S3 bucket policies), those integrations will break immediately upon closure.

IAM Identity Center (SSO) configurations tied to an account may affect other accounts in an organization if not properly decoupled first.

The Variables That Make This Different for Every Account 🧩

How complex and time-consuming account closure is depends entirely on the footprint of the account:

• A personal free-tier account with no active resources closes in minutes
• A development account with a handful of EC2 instances and S3 buckets requires a methodical resource cleanup — plan for an hour or more
• A production or multi-service account with Reserved Instances, Marketplace subscriptions, Organizations membership, and cross-account dependencies may require days of preparation, coordination with billing, and potentially contact with AWS Support

The maturity of your account, how long it's been active, what services were ever enabled, and whether it sits inside an Organizations structure all shape what "closing the account" actually involves for your specific situation.