Closing an AWS account
This topic applies only to AWS accounts
To close an Amazon.com shopping account, see http://www.amazon.com/gp/help/customer/display.html?nodeId=GDK92DNLSGWTV6MP
If you no longer need a member account in your organization, and want to ensure that no
one can accrue charges for it, you can close the account from the AWS Organizations console
Before closing your account, back up any applications and data that you
want to retain. Review How do I check for active resources that I no longer need on my AWS account?
Immediately, the account can no longer be used for any AWS activity other than signing in as the root user to view past bills or to contact AWS Support. For more information, see Contacting Customer Support About Your Bill.
Impacts of closing an account
When you close an AWS account, there are some impacts that you should consider prior to account closure.
-
The root user's email address can't be reused if you close an account.
-
To close the management account for the organization, you must first either remove or close all member accounts in the organization. By closing the management account, it automatically deletes the organization, as long as there are no member accounts in the organization.
-
You can only close 10% of member accounts within a rolling 30 day period. This quota is not bound by a calendar month, but starts when you close an account. Within 30 days of that initial account closure, you can't exceed the 10% account closure limit. The minimum account closure is 10 and the maximum account closure is 200, even if 10% of accounts exceeds 200. For more information about Organizations quotas, see Quotas for AWS Organizations.
-
If you use AWS Control Tower, you need to unmanage the accounts before you attempt to close an account. See Unmanage a member account in the AWS Control Tower User Guide.
-
If you have an AWS account that is linked to a AWS GovCloud (US) account, you need to close the standard account before you close the AWS GovCloud (US) account. To learn important pre-closure details, see Closing an AWS GovCloud (US) account in the AWS GovCloud (US) User Guide.
Best practice we recommend but is not required for security:
As a best practice, we recommend that you remove references from any IAM permissions or policies to closed accounts, in accordance with the security best practice of granting the least privilege needed to get the job done. This is not a security issue because AWS never reuses an ID number after the account is closed. IAM Access Analyzer will notify you if you have an ID for a closed account in an IAM policy.
From the time you close the account until 90 days expire:
-
Closed accounts are visible in your organization with the SUSPENDED state.
-
Some active resources that are not terminated prior to account closure can continue to incur fees if you decide to reopen the account within 90 days. For more information, see How do I terminate active resources I no longer need on my AWS account?
in the Knowledge Center. -
You will be able to log in to view past bills and access AWS Support.
After the 90 day grace period expires:
-
A closed AWS account is no longer visible in your organization.
-
AWS accounts are no longer eligible for reinstatement. At this point, any AWS resources that were in the account can’t be recovered.
Closing an AWS account
When you sign in to the organization's management account, you can close member accounts that are part of your organization. To do this, complete the following steps.
Protecting accounts from closure
If you want to protect an AWS account from accidental closure, you can create an IAM policy to specify which accounts are exempt from closure. Any member account protected with these policies can’t be closed. This can't be accomplished with an SCP, because they don't affect principals in the management account.
You can create an IAM policy that denies closing accounts in either of two ways:
-
Explicitly list each account that you want to protect in the policy by including the
arn
in theResource
element. To see an example, see Prevent accounts listed in this policy from getting closed. -
Tag individual accounts to prevent them from getting closed. Use the
aws:ResourceTag
tag global condition key in your policy to prevent any account with the tag from being closed. To learn how to tag an account, see Tagging Organizations resources. To see an example, see Prevent accounts with tag from getting closed .
Example IAM policies that prevent AWS account closures
Topics
Prevent accounts with tag from getting closed
You can attach the following policy to an identity in your management account.
This policy prevents principals in the management account from closing any
member account that is tagged with the aws:ResourceTag
tag global
condition key, the AccountType
key and the Critical
tag value.
{ "Version": "2012-10-17", "Statement": [ { "Sid": "PreventCloseAccountForTaggedAccts", "Effect": "Deny", "Action": "organizations:CloseAccount", "Resource": "*", "Condition": { "StringEquals": {"aws:ResourceTag/AccountType": "Critical"} } } ] }
Prevent accounts listed in this policy from getting closed
You can attach the following policy to an identity in your management account.
This policy prevents principals in the management account from closing accounts
explicitly specified in the Resource
element.
{ "Version": "2012-10-17", "Statement": [ { "Sid": "PreventCloseAccount", "Effect": "Deny", "Action": "organizations:CloseAccount", "Resource": [ "arn:aws:organizations::555555555555:account/o-12345abcdef/123456789012", "arn:aws:organizations::555555555555:account/o-12345abcdef/123456789014" ] } ] }