Enable and configure cross-account backup and monitoring in a management account. This automation can only be completed successfully in a management account.
Full classification: Management | AWS Backup | Backup plan | Enable cross account copy (Management account)
Change Type Details
Change type ID |
ct-2yja7ihh30ply |
Current version |
1.0 |
Expected execution duration |
60 minutes |
AWS approval |
Required |
Customer approval |
Not required |
Execution mode |
Automated |
Additional Information
Enable cross account backup plan copy
The following shows this change type in the AMS console.
How it works:
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.
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.
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.
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.
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.
The following shows this change type in the AMS console.
How it works:
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.
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.
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.
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.
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.
How it works:
Use either the Inline Create (you issue a
create-rfccommand 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 thecreate-rfccommand with the two files as input. Both methods are described here.Submit the RFC:
aws amscm submit-rfc --rfc-idcommand with the returned RFC ID.IDMonitor the RFC:
aws amscm get-rfc --rfc-idcommand.ID
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.
INLINE CREATE:
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-2yja7ihh30ply" \ --change-type-version "1.0" --title "ConfigCrossAccountCopyInManagementAccount" \ --execution-parameters "{\"DocumentName\":\"AWSManagedServices-HandleConfigureCrossAccountBackupInManagementAccount-Admin\",\"Region\":\"ap-southeast-2\",\"Parameters\":{\"DestinationAccountId\":[\"123456789012\"],\"SourceAccountId\":[\"210987654321\"]}}" \ --endpoint-urlhttps://amscm-gamma.us-east-1.amazonaws.com
TEMPLATE CREATE:
Output the execution parameters JSON schema for this change type to a JSON file; this example names it ConfigCrossAcctCopyBackupPlanParams.json:
aws amscm get-change-type-version --change-type-id "ct-2yja7ihh30ply" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > ConfigCrossAcctCopyBackupPlanParams.jsonModify and save the ConfigCrossAcctCopyBackupPlanParams file.
{ "DocumentName": "AWSManagedServices-HandleConfigureCrossAccountBackupInManagementAccount-Admin", "Region": "ap-southeast-2", "Parameters": { "DestinationAccountId": [ "123456789012" ], "SourceAccountId": [ "210987654321" ] } }Output the RFC template to a file in your current folder; this example names it ConfigCrossAcctCopyBackupPlanRfc.json:
aws amscm create-rfc --generate-cli-skeleton > ConfigCrossAcctCopyBackupPlanRfc.jsonModify and save the ConfigCrossAcctCopyBackupPlanRfc.json file. For example, you can replace the contents with something like this:
{ "ChangeTypeId": "ct-2yja7ihh30ply", "ChangeTypeVersion": "1.0", "Title": "ConfigureCrossAcctCopyBackup" }Create the RFC, specifying the ConfigCrossAcctCopyBackupPlanRfc file and the ConfigCrossAcctCopyBackupPlanParams file:
aws amscm create-rfc --cli-input-json file://ConfigCrossAcctCopyBackupPlanRfc.json --execution-parameters file://ConfigCrossAcctCopyBackupPlanParams.jsonYou 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.
To learn more about AWS Backup, see AWS Backup: How It Works.
Execution Input Parameters
For detailed information about the execution input parameters, see Schema for Change Type ct-2yja7ihh30ply.
Example: Required Parameters
Example not available.
Example: All Parameters
{
"DocumentName": "AWSManagedServices-HandleConfigureCrossAccountBackupInManagementAccount-Admin",
"Region": "us-east-1",
"Parameters": {
"DestinationAccountId": [ "123456789012" ],
"SourceAccountId": [ "123456789012" ]
}
}
