How to Close an AWS Account: What You Need to Know Before You Pull the Trigger
Closing an AWS account isn't as simple as clicking a delete button. Amazon Web Services has a deliberate, multi-step process designed to make sure you don't accidentally wipe out active infrastructure, incur surprise charges, or lose data you meant to keep. Understanding what actually happens — and in what order — saves you from costly mistakes.
What "Closing" an AWS Account Actually Means
When you close an AWS account, you're initiating a termination process, not an instant deletion. AWS suspends the account immediately upon closure request, but the account enters a post-closure period (typically 90 days) during which:
- Your resources are inaccessible but not yet permanently deleted
- You can reopen the account if you change your mind
- AWS may still generate final charges for usage up to the closure date
After that 90-day window, AWS permanently deletes the account and all associated data. This is irreversible.
Before You Close: The Pre-Closure Checklist ✅
Skipping preparation is where most people run into trouble. Work through these steps before you ever touch the account closure setting.
Terminate All Active Resources
Active services continue billing until explicitly stopped. Go through every region — AWS resources are region-specific, meaning an EC2 instance in us-east-1 and one in eu-west-2 are listed separately.
Key services to check and terminate:
| Service Category | What to Look For |
|---|---|
| Compute | EC2 instances, Lightsail instances, ECS tasks |
| Storage | S3 buckets and objects, EBS volumes, Glacier archives |
| Database | RDS instances, DynamoDB tables, ElastiCache clusters |
| Networking | Elastic IPs, NAT Gateways, VPNs, load balancers |
| Serverless | Lambda functions, API Gateway endpoints |
| ML/AI | SageMaker endpoints and notebooks |
Elastic IPs, NAT Gateways, and load balancers are common billing culprits that people forget because they're not "running" services in the obvious sense — they just exist and charge.
Download Everything You Want to Keep
Once the account is closed and the 90-day window passes, data recovery is not possible. Before closing:
- Export S3 data to local storage or another cloud provider
- Create final snapshots of RDS databases and download them
- Export CloudWatch logs you want to retain
- Download any billing reports or Cost Explorer data you may need for tax or audit purposes
Check for Active Subscriptions and Marketplace Purchases
AWS Marketplace subscriptions don't automatically cancel when you close an account. Review your subscriptions under AWS Marketplace → Manage Subscriptions and cancel each one individually before proceeding.
Settle Any Outstanding Balance
AWS requires a zero or paid balance before account closure. If you have an outstanding invoice, it must be resolved. Attempting to close an account with unpaid charges will block the process.
Remove or Transfer Reserved Instances
If you purchased Reserved Instances or Savings Plans, closing the account doesn't automatically refund them. Reserved Instances can sometimes be listed on the Reserved Instance Marketplace for resale. Savings Plans have no resale mechanism — you'd be forfeiting remaining committed spend. Factor this into your timing.
How to Actually Close the Account 🔒
Once your pre-closure checklist is complete:
- Sign in as the root user — account closure requires root credentials, not an IAM user, even one with full admin permissions
- Navigate to Account Settings in the AWS Management Console (top-right menu → your account name → Account)
- Scroll to the Close Account section at the bottom of the page
- Read the on-screen confirmations — AWS presents explicit warnings about what you're agreeing to
- Check all required acknowledgment boxes
- Click Close Account
You'll receive a confirmation email to the root account's email address.
Organizations and Multi-Account Setups
If your account is a member account inside an AWS Organization, you cannot close it directly from the member account alone in all cases. You may need to:
- Remove the account from the organization first, then close it
- Or close it through the management (master) account depending on your organization's policy settings
If your account is the management account of an organization, you must close all member accounts first before the management account can be closed. This significantly changes the scope of the process.
What Happens During the 90-Day Post-Closure Period
During this window:
- Root login still works — you can reopen the account
- Resources are suspended, not deleted
- AWS will still attempt to collect any final charges against payment methods on file
- Support cases can still be opened if you encounter billing disputes
After the 90 days expire, deletion is permanent and AWS support cannot recover data or the account.
The Variable That Changes Everything
The complexity of closing an AWS account scales directly with how deeply embedded your infrastructure is. A personal account with a single S3 bucket and no active services takes about ten minutes to close cleanly. An account with multi-region infrastructure, active Reserved Instances, Marketplace subscriptions, and organizational dependencies can take days of careful work to wind down properly.
Your own account history — how long it's been active, which services you've used, whether it sits inside an organization, and what financial commitments are attached — determines how straightforward or involved this process will be for you. 🗂️