Blog Post - Automate centralized backup at scale across AWS services using AWS Backup
This solution demonstrates how you can save time using AWS CloudFormation automation to centrally automate and scale the process of implementing AWS Backup policies, backup vaults, and cross-Region, cross-account replication across your multi-account AWS environment. Using this solution, you can easily manage AWS Backup with automation and implement a data protection strategy that mitigates the risk of data loss.. In this repository, you will find all the AWS CloudFormation templates and Python code that will build this solution in your AWS environment.
Solution architecture and design
The workflow and architecture of the solution works as follows:
In the management account (the environment hosting your AWS Organizations):
- Opt in to use the AWS Backup service and cross-account management features. See the blog post on how to Automate centralized backup at scale across AWS services using AWS Backup for further details.
- aws-backup-member-account-iam-role.yaml: This stackset implements the IAM roles assumed by the AWS Backup service for backup and restore jobs across the member accounts.
- aws-backup-member-account.yaml: This stackset implements the local backup vaults and vault AWS KMS encryption keys in the member accounts. We assume that the supported AWS Backup resources in the member accounts are tagged as indicated in the prerequisites section of the blog.
- aws-backup-central-backup-account.yaml: This stackset implements the central backup vault, IAM role, vault AWS KMS encryption key, and vault access policy in the central backup account.
- aws-backup-org-policy.yaml: This stack implements a Lambda function, Lambda IAM role, and centralized backup policies. The backup policies consist of tag-based and cross-account, cross-Region copy policies that are automatically attached to the root OU and inherited by all AWS Organizations accounts.
Security
See CONTRIBUTING for more information.
License
This library is licensed under the MIT-0 License. See the LICENSE file.