How to Close Your AWS Account Step by Step

Understanding AWS Account Closure and What Happens to Your Data

Closing an Amazon Web Services account is a permanent action that stops all AWS services and removes access to your account resources. When you close your account, AWS begins a deletion process that affects everything associated with that account—databases, storage, virtual machines, and billing information. This guide covers the steps to close your AWS account and what you should know before doing so.

Before initiating closure, you should understand what happens to your data. AWS retains some information for billing and compliance purposes, typically for seven years after account closure. However, the resources you created—such as Amazon EC2 instances, S3 buckets, RDS databases, and Lambda functions—are deleted according to AWS's data retention policies. Most user-created data is deleted within 90 days, though some backup or archived data may persist longer depending on your configuration.

AWS distinguishes between account closure and service suspension. If your account is suspended due to policy violations or unpaid bills, you may not have the option to close it through normal channels. A suspended account can sometimes be reactivated if the underlying issue is resolved and AWS agrees to reinstate it. However, a voluntarily closed account cannot be reopened—you would need to create an entirely new AWS account if you want to use AWS services again in the future.

Financial implications matter significantly. When you close your account, you remain responsible for any outstanding charges incurred up to the moment of closure. AWS will charge your payment method for any resources that were running or data that was stored. If you have active Reserved Instances (long-term pricing commitments), closing your account does not refund the unused portion—you lose that investment. Understanding these details before closure prevents unexpected charges or regret about lost prepaid commitments.

Practical takeaway: Before closing your AWS account, review your recent bills, identify any Reserved Instances or long-term commitments, back up any critical data, and confirm you won't need AWS services again, as reopening requires creating a new account entirely.

Preparing Your Account for Closure: Backing Up and Cleaning Up

The preparation phase is crucial and should take several days or weeks depending on how much data and resources you have. This phase involves backing up important data, deleting unnecessary resources, and documenting what you're keeping versus removing. Rushing through preparation often leads to accidental data loss or discovering months later that you needed something you deleted.

Start by identifying all resources running in your AWS account. Log into the AWS Management Console and navigate to each service to see what's active. Common resources include EC2 instances (virtual servers), RDS databases, S3 buckets (storage), Lambda functions, and DynamoDB tables. You can also use the AWS Resource Groups service to get a comprehensive view across regions and services. Document what each resource does and whether it contains data you need to preserve.

For data backup, the method depends on the service type. For S3 buckets, you can download files directly or use AWS DataSync to transfer data to another location. For EC2 instances, create an AMI (Amazon Machine Image) snapshot before deletion if you might need to recreate the instance later. For RDS databases, create a final manual snapshot—AWS-managed automated backups are deleted when you close the account, but manual snapshots you created can be retained and restored to a new AWS account if needed. For DynamoDB, export your table data to S3, then download from S3.

Delete resources you no longer need to reduce your final bill and simplify the closure process. Terminating running EC2 instances stops charges immediately. Deleting S3 buckets removes storage costs, but buckets must be completely empty first—delete all objects and versions. Remove unused Elastic IPs, unattached EBS volumes, and unused databases. Check your AWS Cost Explorer to identify which resources are consuming the most charges, as removing these saves the most money before closure.

Review your billing information and payment methods. If you have multiple payment methods on file, you should know which one will be charged for any final bills. Check for any Reserved Instances or Savings Plans you purchased—these cannot be refunded, and you should decide whether to let them expire naturally or close the account despite the sunk cost. Download your billing history and invoices from the Billing Dashboard for your records.

Practical takeaway: Spend time backing up critical data to external storage, downloading important files, creating final database snapshots, and deleting unused resources to minimize your final bill and prevent accidental data loss during account closure.

Verifying You Don't Have Active Subscriptions or Marketplace Items

AWS Marketplace is an online store where third-party vendors sell software, services, and data products that run on AWS. If you subscribed to any Marketplace products, these subscriptions continue billing even after you close your AWS account—the vendor, not AWS, manages the subscription. Identifying and canceling these subscriptions before account closure prevents surprise charges from appearing on your payment method weeks or months later.

Log into the AWS Management Console and navigate to the AWS Marketplace section. Look for "Manage Subscriptions" or "My Subscriptions" to see all active Marketplace subscriptions. The list shows subscription name, vendor, status, and renewal date. For each subscription you no longer want, click the subscription and select the option to unsubscribe or cancel. Some subscriptions have penalties or notice periods—review the terms before canceling. After unsubscribing, the vendor should send a confirmation email within a few hours.

AWS also offers optional support plans: Developer Support, Business Support, and Enterprise Support. If you have a paid support plan, you should cancel it before closing your account. Support plans bill monthly and don't refund partial months. Navigate to AWS Support in the Management Console and look for plan management options. Downgrade to the free Basic Support before account closure. Note that canceling a support plan is different from closing your account—you must do both.

Check for any AWS Service Catalog portfolios, AWS Config rules, or AWS Systems Manager subscriptions you may have set up. Some of these services have optional paid components or integrated third-party tools that may charge fees. Review each service you use in the Management Console and disable or cancel any subscriptions. Additionally, look at your AWS Organizations structure if you have multiple accounts linked—closing one linked account doesn't close others, but it may affect billing consolidation or permissions for remaining accounts.

Review Cost Anomaly Detection and Cost Explorer alerts you've set up—these are free, but disabling them simplifies the account before closure. Check if you have any pending support cases or open AWS Support tickets; close these or transfer ownership to another team member if relevant. For AWS Trusted Advisor checks and AWS Well-Architected reviews you may have paid for, these are not subscriptions per se, but note that you won't receive future recommendations after closure.

Practical takeaway: Review your AWS Marketplace subscriptions and support plans in the Management Console, cancel any active subscriptions before closing the account, and confirm cancellations with the vendors to prevent unexpected charges to your payment method after account closure.

Step-by-Step Process for Closing Your Account in the AWS Management Console

The actual account closure happens through the AWS Management Console's Account Settings section. The process requires you to confirm your identity and intent multiple times to prevent accidental closure. AWS also requires your account to meet certain conditions—for example, if your account is suspended, you cannot close it through the standard process and must contact AWS Support.

Begin by logging into the AWS Management Console using your root account credentials. Using the root account is mandatory for account closure; IAM users or federated identities cannot perform this action. If you normally use an IAM user, you'll need the root account email address and password. Click on your account name in the top-right corner and select "Account" from the dropdown menu.

On the Account page, scroll down to find the "Close Account" section. This section displays your account ID and current account status. Click the "Close Account" button. AWS displays a warning message explaining that this action is permanent and cannot be undone, that you remain responsible for charges incurred through the closure date, and that certain data deletion processes will begin. Read this message carefully, as it confirms the irreversible nature of the action.

AWS asks you to confirm several conditions before closure proceeds. These typically include confirming that you understand all AWS services will be terminated, that you have reviewed your final charges, that you've backed up any needed data, and that you won't be able to reopen this account. You may also need to confirm that you don't have any un