![]() parameters ParameterKey=SolutionHomeAccountId,ParameterValue= \ template-body "file://aws-backup-org-resource-policy-delegate-backup-policy-mgmt.yaml" \ You can follow the directions in the CloudFormation documentation. You will need to enable trusted access between AWS CloudFormation StackSets and AWS Organizations. If StackSets have not been configured yet in your AWS Organizations management account then you will need to configure StackSets first. You will also need to manage new account additions and deletions as well if you don't use service-managed StackSets. This will require you to provision the necessary CloudFormation StackSet Execution roles into new accounts and then establish a trust relationship with the AWS StackSet administration account. If you don't do this, then you will need to self-manage StackSet deployments to target accounts to configure AWS Backup. New accounts added to the target OUs will automatically be configured with the Backup and Recovery with AWS Backup solution. The Backup and Recovery with AWS Backup solution uses a service-managed StackSet to configure AWS Backup in accounts within the AWS Organization Units (OUs) you specify. With only consolidated billing features enabled, you cannot create a stack set with service-managed permissions which are required for the baseline architecture. ![]() If your AWS Organization doesn't have all features enabled, then enable all features in AWS Organizations. ![]() Prerequisites AWS Organizations with all features enabled.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |