Management Account | Move Account To OU

Move an account under an AWS organizational unit (OU) to a different OU.

Full classification: Management | Managed landing zone | Management account | Move account to OU

Change Type Details

Change type ID	ct-1vq0f289r36ay
Current version	1.0
Expected execution duration	3600 minutes
AWS approval	Required
Customer approval	Not required
Execution mode	Automated

Additional Information

Move account to OU

Moving an account to a different OU with the console

Screenshot of this change type in the AMS console:

How it works:

1. Navigate to the Create RFC page: In the left navigation pane of the AMS console click RFCs to open the RFCs list page, and then click Create RFC.

2. Choose a popular change type (CT) in the default Browse change types view, or select a CT in the Choose by category view.

   • Browse by change type: You can click on a popular CT in the Quick create area to immediately open the Run RFC page. Note that you cannot choose an older CT version with quick create.

     To sort CTs, use the All change types area in either the Card or Table view. In either view, select a CT and then click Create RFC to open the Run RFC page. If applicable, a Create with older version option appears next to the Create RFC button.

   • Choose by category: Select a category, subcategory, item, and operation and the CT details box opens with an option to Create with older version if applicable. Click Create RFC to open the Run RFC page.

3. On the Run RFC page, open the CT name area to see the CT details box. A Subject is required (this is filled in for you if you choose your CT in the Browse change types view). Open the Additional configuration area to add information about the RFC.

   In the Execution configuration area, use available drop-down lists or enter values for the required parameters. To configure optional execution parameters, open the Additional configuration area.

4. When finished, click Run. If there are no errors, the RFC successfully created page displays with the submitted RFC details, and the initial Run output.

5. Open the Run parameters area to see the configurations you submitted. Refresh the page to update the RFC execution status. Optionally, cancel the RFC or create a copy of it with the options at the top of the page.

Moving an account to a different OU with the CLI

How it works:

1. Use either the Inline Create (you issue a create-rfc command with all RFC and execution parameters included), or Template Create (you create two JSON files, one for the RFC parameters and one for the execution parameters) and issue the create-rfc command with the two files as input. Both methods are described here.

2. Submit the RFC: aws amscm submit-rfc --rfc-id ID command with the returned RFC ID.

   Monitor the RFC: aws amscm get-rfc --rfc-id ID command.

To check the change type version, use this command:

aws amscm list-change-type-version-summaries --filter Attribute=ChangeTypeId,Value=CT_ID

Note

You can use any CreateRfc parameters with any RFC whether or not they are part of the schema for the change type. For example, to get notifications when the RFC status changes, add this line, --notification "{\"Email\": {\"EmailRecipients\" : [\"[e-mail]\"]}}" to the RFC parameters part of the request (not the execution parameters). For a list of all CreateRfc parameters, see the AMS Change Management API Reference.

INLINE CREATE:

Note

Run this change type from your Management account.

Issue the create RFC command with execution parameters provided inline (escape quotes when providing execution parameters inline), and then submit the returned RFC ID. For example, you can replace the contents with something like this:

aws amscm create-rfc \
--change-type-id "ct-1vq0f289r36ay" \
--change-type-version "1.0" --title "Move Account To OU" \
--execution-parameters "{ \"AccountId\": \"ACCOUNT_ID\", \"TargetOUPath\": \"applications:managed:OU1\"}"

TEMPLATE CREATE:

1. Output the execution parameters JSON schema for this change type to a file; this example names it MvAcctToOuParams.json:

   aws amscm get-change-type-version --change-type-id "ct-1vq0f289r36ay" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > MvAcctToOuParams.json

2. Modify and save the MvAcctToOuParams file. For example, you can replace the contents with something like this:

   {
       "AccountId": "ACCOUNT_ID",
       "TargetOUPath": "applications:managed:OU1",
   }

3. Output the RFC template JSON file to a file; this example names it MvAcctToOuRfc.json:

   aws amscm create-rfc --generate-cli-skeleton > MvAcctToOuRfc.json

4. Modify and save the MvAcctToOuRfc.json file. For example, you can replace the contents with something like this:

   {
   "ChangeTypeVersion":    "1.0",
   "ChangeTypeId":         "ct-1vq0f289r36ay",
   "Title":                "Move-Acct-To-OU-RFC"
   }

5. Create the RFC, specifying the MvAcctToOuRfc file and the MvAcctToOuParams file:

   aws amscm create-rfc --cli-input-json file://MvAcctToOuRfc.json  --execution-parameters file://MvAcctToOuParams.json

   You receive the ID of the new RFC in the response and can use it to submit and monitor the RFC. Until you submit it, the RFC remains in the editing state and does not start.

Tips

Note

When moving accounts between OUs having custom SCPs, functionality may break due to SCPs being applied or a security posture compromised due to SCPs being removed.

When moving accounts from an OU having a custom stackset (with CloudFormation auto-deployment feature enabled (see Manage automatic deployments for a stack set with service-managed permissions, to an OU which does not have this stackset, AWS CloudFormation would remove the stackset instance from the account. This may cause functionality loss. Vice versa, you should be aware of the addition of unwanted stackset instances when moving to a new OU.

When an account is moved, it may no longer have access to resources specified by OU based policy conditions (aws:PrincipalOrgID) in IAM/S3, (see AWS global condition context keys.

To learn more about AMS multi-account landing zone, see AWS Managed Services (AMS) Now Offers Managed Landing Zones.

Execution Input Parameters

For detailed information about the execution input parameters, see Schema for Change Type ct-1vq0f289r36ay.

Example: Required Parameters

{
    "AccountId": "123456789012",
    "TargetOUPath": "applications:development"
}

Example: All Parameters

Example not available.