# Management Account \$1 Offboard Application Account Offboard the specified application account. Run this from the management account for the application account that you want offboarded. You must first confirm the offboarding request by submitting the Confirm offboarding CT (ct-2wlfo2jxj2rkj) from the application account. If you are offboarding a customer-managed account, then ct-2wlfo2jxj2rkj is not needed. After you successfully submit both CTs, AMS can't undo the offboarding, repurpose the account, or help you to remediate issues in the account. **Full classification:** Management \$1 Managed landing zone \$1 Management account \$1 Offboard application account ## Change Type Details **** | | | | --- |--- | | Change type ID | ct-0vdiy51oyrhhm | | Current version | 2.0 | | Expected execution duration | 3600 minutes | | AWS approval | Required | | Customer approval | Not required | | Execution mode | Automated | ## Additional Information ### Management account: Offboard Application account **Important** You have 48 hours to offboard the specified application account after successfully running the [Confirm offboarding](management-managed-application-account-confirm-offboarding.md#ex-man-lz-app-acct-confirm-offb-col) change type (ct-2wlfo2jxj2rkj). After 48 hours, the offboarding request fails and the process of confirming and then offboarding must be restarted. #### Management account: Offboarding an Application account with the Console Screenshot of this change type in the AMS console: ![\[Offboard Application Account details showing ID, execution mode, version, and description.\]](http://docs.aws.amazon.com/managedservices/latest/ctref/images/guiManLzAppAcctRunOffBCT.png) 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**. 1. 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. 1. 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. 1. 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**. 1. 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. #### Management account: Offboarding an Application account 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. 1. 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\" : [\"email@example.com\"]}}"` 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](https://docs.aws.amazon.com/managedservices/latest/ApiReference-cm/API_CreateRfc.html). *INLINE CREATE*: **Note** Run this change type from the Management account associated with the application account being offboarded. 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-0vdiy51oyrhhm" --change-type-version "2.0" --title "Run Offboarding" --execution-parameters "{\"AccountID\": \"000000000000\",\"AccountEmail\": \"email@amazon.com\",\"Confirmation\": \"confirm\",\"DeleteTransitGatewayAttachment\":true}" ``` *TEMPLATE CREATE*: 1. Output the execution parameters JSON schema for this change type to a file; this example names it RunAppAcctOffBParams.json: ``` aws amscm get-change-type-version --change-type-id "ct-0vdiy51oyrhhm" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > RunAppAcctOffBParams.json ``` 1. Modify and save the RunAppAcctOffBParams file. For example, you can replace the contents with something like this: ``` { "AccountID": "000000000000", "AccountEmail": "email@amazon.com", "Confirmation": "confirm", "DeleteTransitGatewayAttachment" : true } ``` 1. Output the RFC template JSON file to a file; this example names it RunAppAcctOffBRfc.json: ``` aws amscm create-rfc --generate-cli-skeleton > RunAppAcctOffBRfc.json ``` 1. Modify and save the RunAppAcctOffBRfc.json file. For example, you can replace the contents with something like this: ``` { "ChangeTypeVersion": "2.0", "ChangeTypeId": "ct-0vdiy51oyrhhm", "Title": "Execute Offboarding" } ``` 1. Create the RFC, specifying the RunAppAcctOffBRfc file and the RunAppAcctOffBParams file: ``` aws amscm create-rfc --cli-input-json file://RunAppAcctOffBRfc.json --execution-parameters file://RunAppAcctOffBParams.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 + The first step to offboarding the AMS multi-account landing zone Application account is to submit the [Confirm offboarding](management-managed-application-account-confirm-offboarding.md#ex-man-lz-app-acct-confirm-offb-col) CT (ct-2wlfo2jxj2rkj) from the application account. Run this change type within 48 hours of successfully running the confirmation change type. + There is no prerequisite or confirmation CT for Customer Managed application accounts. + Note that offboarding is irreversible. + If you intend to self-operate the account after offboarding from AMS, then make sure to specify `DeleteTransitGatewayAttachment` parameter as `false` to retain connectivity. ## Execution Input Parameters For detailed information about the execution input parameters, see [Schema for Change Type ct-0vdiy51oyrhhm](schemas.md#ct-0vdiy51oyrhhm-schema-section). ## Example: Required Parameters ``` { "RequestType": "OffboardingExecution", "Parameters": { "AccountId": "000000000000", "AccountEmail": "example@email.com", "Confirmation": "confirm", "DeleteTransitGatewayAttachment": true } } ``` ## Example: All Parameters ``` { "RequestType": "OffboardingExecution", "Parameters": { "AccountId": "000000000000", "AccountEmail": "example@email.com", "Confirmation": "confirm", "DeleteTransitGatewayAttachment": true } } ```