Removing a member account from an organization with Amazon Organizations
Removing a member account does not close the account, instead it removes the member account from the organization. The former member account becomes a standalone Amazon Web Services account that is no longer managed by Amazon Organizations.
Afterwards, the account is no longer subject to any policies and is responsible for its own bill payments. The organization's management account is no longer charged for any expenses accrued by the account after it's been removed from the organization.
Considerations
IAM access roles created by the management account are not automatically deleted
When you remove a member account from the organization, any IAM role that was created to enable access by the organization's management account isn't automatically deleted. If you want to terminate this access from the former organization's management account, then you must manually delete the IAM role. For information about how to delete a role, see Deleting roles or instance profiles in the IAM User Guide.
You can remove an account from your organization only if the account has the information that is required for it to operate as a standalone account
You can remove an account from your organization only if the account has the information that is required for it to operate as a standalone account. When you create an account in an organization using the Amazon Organizations console, API, or Amazon CLI commands, all the information that is required of standalone accounts is not automatically collected.
For each account that you want to make standalone, you must choose a support plan, provide and verify the required contact information, and provide a current payment method. Amazon uses the payment method to charge for any billable (not Amazon Free Tier) Amazon activity that occurs while the account isn't attached to an organization. To remove an account that doesn't yet have this information, follow the steps in Leave an organization from a member account with Amazon Organizations.
You must wait until at least seven days after the account was created
To remove an account that you created in the organization, you must wait until at least seven days after the account was created. Invited accounts aren't subject to this waiting period.
The owner of the account that leaves becomes responsible for all new costs accrued
At the moment the account successfully leaves the organization, the owner of the Amazon Web Services account becomes responsible for all new Amazon costs accrued, and the account's payment method is used. The management account of the organization is no longer responsible.
The account cannot be a delegated administrator account for any Amazon service enabled for the organization
The account that you want to remove must not be a delegated administrator account for any Amazon service enabled for your organization. If the account is a delegated administrator, you must first change the delegated administrator account to another account that is remaining in the organization. For more information about how to disable or change the delegated administrator account for an Amazon service, see the documentation for that service.
The account no longer has access to cost and usage data
When a member account leaves an organization, that account no longer has access to cost and usage data from the time range when the account was a member of the organization. However, the management account of the organization can still access the data. If the account rejoins the organization, the account can access that data again.
Tags attached to the account are deleted
When a member account leaves an organization, all tags attached to the account are deleted.
Principals in the account are no longer affected by any organization policies
The principals in the account are no longer affected by any policies that applied in the organization. This means that restrictions imposed by SCPs are gone, and the users and roles in the account might have more permissions than they had before. Other organization policy types can no longer be enforced or processed.
The account is no longer be covered by organization agreements
If a member account is removed from an organization, that member account will no
longer be covered by organization agreements. Management account administrators
should communicate this to member accounts before removing member accounts from the
organization, so that member accounts can put new agreements in place if necessary.
A list of active organization agreements can be viewed in the Amazon Artifact console on the
Amazon Artifact Organization
Agreements
Integration with other services might be disabled
Integration with other services might be disabled. If you remove an account from an organization that has integration with an Amazon service enabled, the users in that account can no longer use that service.
Remove a member account from an organization
When you sign in to the organization's management account, you can remove member accounts from the organization that you no longer need. To do this, complete the following procedure. This procedure applies only to member accounts. To remove the management account, you must delete the organization.
Minimum permissions
To remove one or more member accounts from your organization, you must sign in as a user or role in the management account with the following permissions:
-
organizations:DescribeOrganization
– required only when using the Organizations console -
organizations:RemoveAccountFromOrganization
If you choose to sign in as a user or role in a member account in step 5, then that user or role must have the following permissions:
-
organizations:DescribeOrganization
– required only when using the Organizations console. -
organizations:LeaveOrganization
– Note that the organization administrator can apply a policy to your account that removes this permission, preventing you from removing your account from the organization. -
If you sign in as an IAM user and the account is missing payment information, the user must have either
aws-portal:ModifyBilling
andaws-portal:ModifyPaymentMethods
permissions (if the account has not yet migrated to fine-grained permissions) ORpayments:CreatePaymentInstrument
andpayments:UpdatePaymentPreferences
permissions (if the account has migrated to fine-grained permissions). Also, the member account must have IAM user access to billing enabled. If this isn't already enabled, see Activating Access to the Billing and Cost Management Console in the Amazon Billing User Guide.