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 choose “Customize” or “Decline” 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 accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Update organizations

Focus mode
Update organizations - AWS Control Tower

The quickest way to update an organizational unit (OU) or to update multiple accounts within an OU is to Re-register the OU.

What happens during re-registration

When you re-register an OU:
  • The State field indicates whether the account currently is enrolled with AWS Control Tower (Enrolled), whether the account has never been enrolled (Not enrolled), or whether enrollment failed previously (Enrollment failed).

  • When you re-register the OU, the AWSControlTowerExecution role is added to all accounts with status Not enrolled or Enrollment failed.

  • AWS Control Tower creates a single sign-on (IAM Identity Center) login for those new enrolled accounts.

  • Enrolled accounts are re-enrolled into AWS Control Tower.

  • Drift on any preventive controls applied to the OU is fixed, because the SCPs are returned to their default definitions.

  • All accounts are updated to reflect the latest landing zone changes.

For more information, see Enroll an existing AWS account.

Tip

When you re-register an OU, or when you're updating your landing zone version and multiple member accounts, you may see a failure message mentioning the StackSet-AWSControlTowerExecutionRole. This StackSet in the management account can fail because the AWSControlTowerExecution IAM role already exists in all enrolled member accounts. This error message is expected behavior, and it can be disregarded.

On this page

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