docs.aws.amazon.com Open in urlscan Pro
18.66.147.42  Public Scan

Form analysis
0 forms found in the DOM

Text Content

SELECT YOUR COOKIE PREFERENCES

We use essential cookies and similar tools that are necessary to provide our
site and services. We use performance cookies to collect anonymous statistics so
we can understand how customers use our site and make improvements. Essential
cookies cannot be deactivated, but you can click “Customize cookies” to decline
performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide
useful site features, remember your preferences, and display relevant content,
including relevant advertising. To continue without accepting these cookies,
click “Continue without accepting.” To make more detailed choices or learn more,
click “Customize cookies.”

Accept all cookiesContinue without acceptingCustomize cookies


CUSTOMIZE COOKIE PREFERENCES

We use cookies and similar tools (collectively, "cookies") for the following
purposes.


ESSENTIAL

Essential cookies are necessary to provide our site and services and cannot be
deactivated. They are usually set in response to your actions on the site, such
as setting your privacy preferences, signing in, or filling in forms.




PERFORMANCE

Performance cookies provide anonymous statistics about how customers navigate
our site so we can improve site experience and performance. Approved third
parties may perform analytics on our behalf, but they cannot use the data for
their own purposes.

Allow performance category
Allowed


FUNCTIONAL

Functional cookies help us provide useful site features, remember your
preferences, and display relevant content. Approved third parties may set these
cookies to provide certain site features. If you do not allow these cookies,
then some or all of these services may not function properly.

Allow functional category
Allowed


ADVERTISING

Advertising cookies may be set through our site by us or our advertising
partners and help us deliver relevant marketing content. If you do not allow
these cookies, you will experience less relevant advertising.

Allow advertising category
Allowed

Blocking some types of cookies may impact your experience of our sites. You may
review and change your choices at any time by clicking Cookie preferences in the
footer of this site. We and selected third-parties use cookies or similar
technologies as specified in the AWS Cookie Notice.

CancelSave preferences




UNABLE TO SAVE COOKIE PREFERENCES

We will only store essential cookies at this time, because we were unable to
save your cookie preferences.

If you want to change your cookie preferences, try again later using the link in
the AWS console footer, or contact support if the problem persists.

Dismiss


Contact Us
English


Create an AWS Account
 1. AWS
 2. ...
    
    
 3. Documentation
 4. AWS Account Management
 5. Reference Guide

Feedback
Preferences


AWS ACCOUNT MANAGEMENT


REFERENCE GUIDE

 * Welcome
    * Do I need multiple AWS accounts?
    * Getting started: Are you a first-time AWS user?
    * Using the root user

 * Manage your account
    * Create your account
    * View your account identifiers
    * Update your account settings
    * Understanding API modes of operation
    * Update your account contact information
       * Alternate account contacts
       * Primary account contact
   
    * Update your security challenge questions
    * Specify which AWS Regions your account can use
    * Create or update your account alias
    * Billing for your AWS account
    * Manage accounts in India
    * Close your account

 * Account Management & AWS Organizations
    * Trusted access
    * Delegated admin account
    * Example SCPs

 * Security
    * Data protection
    * AWS PrivateLink
       * Endpoint policies
   
    * Identity and Access Management
       * AWS Account Management and IAM
       * Identity-based policy examples
       * Using identity-based policies
       * Troubleshooting
   
    * AWS managed policies
    * Compliance validation
    * Resilience
    * Infrastructure security

 * Monitoring
    * CloudTrail logs
    * Monitoring Account Management events with EventBridge

 * API Reference
    * Actions
       * DeleteAlternateContact
       * DisableRegion
       * EnableRegion
       * GetAlternateContact
       * GetContactInformation
       * GetRegionOptStatus
       * ListRegions
       * PutAlternateContact
       * PutContactInformation
   
    * Related actions
       * CreateAccount
       * CreateGovCloudAccount
       * DescribeAccount
   
    * Data Types
       * AlternateContact
       * ContactInformation
       * Region
       * ValidationExceptionField
   
    * Common Parameters
    * Common Errors
    * Making HTTP Query requests

 * Quotas
 * Troubleshooting your AWS account
    * Account creation issues
    * Other issues

 * Document history
 * AWS Glossary

Close a standalone AWS account - AWS Account Management
AWSDocumentationAWS Account ManagementReference Guide
Considerations before you close your AWS accountTroubleshooting errors when
closing an AWS accountClosing your AWS accountAccessing your AWS account during
the post-closure periodReopening your AWS accountAfter the post-closure Period


CLOSE A STANDALONE AWS ACCOUNT

PDF

This topic describes how to close a standalone AWS account that isn't managed by
AWS Organizations. If you want to close an account that's managed by AWS
Organizations, see Closing a member account in your organization in the AWS
Organizations User Guide. To close a GovCloud account, see Closing an AWS
GovCloud (US) account in the AWS GovCloud (US) user guide.

Only the root user can close an AWS account. AWS can't close an account on your
behalf. If you have any questions about the process, contact your account
representative or contact AWS Support for assistance. For more information about
contacting AWS Support, see Contacting AWS Support.

TOPICS

 * Considerations before you close your AWS account
 * Troubleshooting errors when closing an AWS account
 * Closing your AWS account
 * Accessing your AWS account during the post-closure period
 * Reopening your AWS account
 * After the post-closure Period


CONSIDERATIONS BEFORE YOU CLOSE YOUR AWS ACCOUNT


Before closing your AWS account, consider the following:


YOUR AGREEMENT WITH AWS

Closing your AWS account will serve as your notice of termination of the AWS
Customer Agreement (or any other AWS agreement governing this account) for this
account. If you reopen your AWS account during the post-closure period (90 days
from the day you closed the account and 60 days for accounts suspended by AWS
prior to account closure), you agree that the same agreement terms govern your
access to and use of the service offerings through your reopened AWS account.


AWS MANAGEMENT CONSOLE ACCESS

Your access to the AWS Management Console for a closed AWS account is
restricted. During the post-closure period, you can still sign in to your AWS
account to view your past billing information, access your account settings, and
to contact AWS Support. You can't access any other AWS services in the closed
account.


FIND AND TERMINATE ACTIVE RESOURCES

To prevent unexpected charges, prior to closing your account, we recommended
that you first review and terminate all applicable resources currently running
in the account.

TO FIND ACTIVE RESOURCES IN YOUR ACCOUNT

 1. Log in to the AWS Management Console.

 2. On the navigation pane, choose Services.

 3. On the Services page, search for Resource Groups.

 4. Under Tag Editor, in Regions, select the regions where you have created
    resources, or choose All regions.

 5. In Resource types, select All supported resource types.

 6. Choose Search Resources. If search results appear, then there are still
    active resources on the account.
    
    NOTE
    
    AWS Resource Groups search results don't show AWS Marketplace subscriptions.
    To manage subscriptions, see Managing your software.

You should archive your content and delete the resources where appropriate. For
additional instructions on how to retrieve your content, see the documentation
for that service.

For more information, see How do I check for active resources that I no longer
need on my AWS account?.


ACCOUNTS PROTECTED BY MFA

If you've turned on multi-factor authentication (MFA) on your AWS account root
user, or configured an MFA device on an IAM user, the MFA isn't removed
automatically when you close the account. If you choose to leave the MFA turned
on during the 90 days post-closure period, keep the virtual hardware MFA device
active until the post-closure period expired in case you need to access the
account during that time.

You have the option to turn off the MFA device before closing the account. MFA
devices for IAM users must be deleted by the account administrator.


BILLING

We charge you through your designated payment method for any usage fees incurred
before you closed your AWS account. We issue you any refunds that might be due
through that same payment method. If you have active subscriptions (such as a
Reserved Instance that you pay for monthly), even after your account is closed,
you might continue to be charged for the subscription through your designated
payment method until the subscription expires or is sold according to the terms
governing the subscription. These charges and refunds might occur after you
close your account.

In addition, if you reopen your account, you might be charged for the cost of
running AWS services (that you didn't stop before closing your account) during
the post-closure period.

For example, lets say you reopen your AWS account 30 days after closure. Your
AWS account had only an active t2.micro Amazon EC2 instance at closure. Now,
lets imagine that the price for a t2.micro Amazon EC2 instance in your AWS
Region is $0.01 per hour. In this scenario, you might be charged for 30 days x
24 hours x $0.01 per hour = $7.20 for your AWS services usage.


CROSS-ACCOUNT ACCESS TO THE ACCOUNT YOU’RE CLOSING

After you close your AWS account, any access requests to your closed account's
AWS services from other AWS accounts fail. This occurs even if you have granted
the other accounts permission to access your account's AWS services. If you
reopen your AWS account, other AWS accounts can again access your account's AWS
services and resources if you granted the necessary permissions to the other AWS
accounts.


DOMAINS REGISTERED WITH AMAZON ROUTE 53

Domains that are registered with Route 53 are not deleted automatically. When
you close your AWS account, you have three options:

 * You can disable automatic renewal, and the domains are automatically deleted
   when the registration period expires. For more information, see Enabling or
   Disabling Automatic Renewal for a Domain in the Amazon Route 53 Developer
   Guide.

 * You can transfer the domains to another AWS account. For more information,
   see Transferring a Domain to a Different AWS account.

 * You can transfer the domains to another domain registrar. For more
   information, see Transferring a Domain from Route 53 to Another Registrar.

If you already closed the account, you can open a case with AWS Support to get
help with disabling automatic renewal or transferring your domains. For more
information, see Contacting AWS Support About Domain Registration Issues. There
is no charge to open a case for domain registration issues.


REMOVING AMAZON VPC PEERING CONNECTION

AWS doesn't delete Amazon Virtual Private Cloud (Amazon VPC) peering connections
when you close one of the accounts participating in the VPC peering connection.
Any traffic destined for the VPC peering connection originating from other
active accounts is dropped because AWS terminates instances and deletes any
security groups in the closed account. To remove the VPC peering connection,
delete it from your account using the Amazon VPC console, AWS Command Line
Interface (AWS CLI), or Amazon EC2 API. For more information, see Deleting a VPC
peering connection


TROUBLESHOOTING ERRORS WHEN CLOSING AN AWS ACCOUNT


If you receive an error message while trying to close your AWS account, you can
contact your account representative or contact AWS Support to open a billing or
account support case for assistance. Common reasons why you might not be able to
close your AWS account include the following:

 * Your account is the management account of an organization in AWS
   Organizations with active member accounts. To close the management account,
   you must first remove all member accounts from the organization.

 * You have unpaid invoices for your account.

 * You are an active AWS Marketplace seller.


CLOSING YOUR AWS ACCOUNT


You can close your AWS account using the following procedure.

AWS Management Console

TO CLOSE YOUR AWS ACCOUNT

MINIMUM PERMISSIONS

To perform the following steps, you must have at least the following IAM
permissions:

 * You must sign in as the AWS account root user, which requires no additional
   IAM permissions. You can't perform these steps as an IAM user or role.

 1. Review Considerations before you close your AWS account.

 2. Sign in as the root user of the account that you want to close, using the
    email address and password that are associated with the account. If you sign
    in as an AWS Identity and Access Management (IAM) user or role, you can't
    close an account.

 3. On the navigation bar in the upper-right corner, choose your account name
    (or alias), and then choose Account.

 4. On the Account page, scroll to the end of the page to the Close Account
    section. Read and ensure that you understand the text next to the check
    boxes. After you close an AWS account, you can no longer use it to access
    AWS services.

 5. Select the check boxes to accept the terms, and then choose Close Account.

 6. In the confirmation box, choose Close Account.

AWS CLI & SDKs

This task isn't supported in the AWS CLI or by an API operation from one of the
AWS SDKs. You can perform this task only by using the AWS Management Console.

anchoranchor
 * AWS Management Console
 * AWS CLI & SDKs

TO CLOSE YOUR AWS ACCOUNT

MINIMUM PERMISSIONS

To perform the following steps, you must have at least the following IAM
permissions:

 * You must sign in as the AWS account root user, which requires no additional
   IAM permissions. You can't perform these steps as an IAM user or role.

 1. Review Considerations before you close your AWS account.

 2. Sign in as the root user of the account that you want to close, using the
    email address and password that are associated with the account. If you sign
    in as an AWS Identity and Access Management (IAM) user or role, you can't
    close an account.

 3. On the navigation bar in the upper-right corner, choose your account name
    (or alias), and then choose Account.

 4. On the Account page, scroll to the end of the page to the Close Account
    section. Read and ensure that you understand the text next to the check
    boxes. After you close an AWS account, you can no longer use it to access
    AWS services.

 5. Select the check boxes to accept the terms, and then choose Close Account.

 6. In the confirmation box, choose Close Account.




ACCESSING YOUR AWS ACCOUNT DURING THE POST-CLOSURE PERIOD


After you close an AWS account, you can no longer use it to access AWS services.
The post-closure period refers to the length of time between account closure and
when AWS permanently closes your AWS account. During this period, you can reopen
your account, view past billing information, access account settings, or contact
AWS Support. The post-closure period is 90 days for self-closed accounts and 60
days for accounts suspended by AWS prior to account closure.

During the post-closure period, AWS may retain any content that you didn't
delete and any AWS services that you didn't stop before you closed your AWS
account. You can access any remaining content or AWS services only by reopening
your account during the post-closure period.


REOPENING YOUR AWS ACCOUNT


You can reopen your AWS account by contacting AWS Support during the
post-closure period. When your account is reopened, you can access the content
that you didn't delete and AWS services that you didn't stop before closing your
account, but you might be charged for the cost of running those AWS services
while your account was closed.


AFTER THE POST-CLOSURE PERIOD


After the post-closure period, AWS permanently closes your AWS account, and you
can no longer reopen it. Any content that you didn't delete is permanently
deleted, and any AWS services that you didn't stop are stopped. Service
attributes can be retained as long as needed for billing and administration
purposes.

You can't create a new AWS account using the same alias or email address that
was registered to your AWS account at the time of its closure.

Javascript is disabled or is unavailable in your browser.

To use the Amazon Web Services Documentation, Javascript must be enabled. Please
refer to your browser's Help pages for instructions.

Document Conventions
Manage accounts in India
Account Management & AWS Organizations
Did this page help you? - Yes

Thanks for letting us know we're doing a good job!

If you've got a moment, please tell us what we did right so we can do more of
it.



Did this page help you? - No

Thanks for letting us know this page needs work. We're sorry we let you down.

If you've got a moment, please tell us how we can make the documentation better.





DID THIS PAGE HELP YOU?

Yes
No
Provide feedback

NEXT TOPIC:

Account Management & AWS Organizations

PREVIOUS TOPIC:

Manage accounts in India

NEED HELP?

 * Try AWS re:Post 
 * Connect with an AWS IQ expert 

PrivacySite termsCookie preferences
© 2023, Amazon Web Services, Inc. or its affiliates. All rights reserved.


ON THIS PAGE

 * Considerations before you close your AWS account
 * Troubleshooting errors when closing an AWS account
 * Closing your AWS account
 * Accessing your AWS account during the post-closure period
 * Reopening your AWS account
 * After the post-closure Period









DID THIS PAGE HELP YOU? - NO



Thanks for letting us know this page needs work. We're sorry we let you down.

If you've got a moment, please tell us how we can make the documentation better.




Feedback