How can I implement the 3-2-1 backup strategy for RDS databases in AWS, given that AWS Backup does not support cross-region copy jobs for RDS resources?

Hi,

Please refer to the following blog posts regarding AWS backup and RDS database backup solutions. The first two posts provides details on using AWS Backup to automate copying RDS database snapshots from one AWS account to another AWS account in the same AWS Region, and to copy the backup to a different Region in the destination account using automation with EventBridge and Lambda.

• Automate cross-account backups of Amazon RDS and Amazon Aurora databases with AWS Backup

• Protecting encrypted Amazon RDS instances with cross-account and cross-Region backups

• Automate cross-account backup of Amazon RDS for Oracle including database parameter groups, option groups and security groups - Blog post if you need to include the RDS associated resources for cross-account backup using AWS Backup(written by me).

• Demystifying AWS Backup for Amazon RDS for Oracle - Overall AWS Backup feature usability with Amazon RDS backup, talks about RDS for Oracle, but can be used with other database engines as well.

Please let me know if you have any other specific questions.

For using Backup Plan, the resource assignment need to be done since in the secondary region (account A, Region B) there is no RDS instance and only RDS snapshot backups, Lambda function is used to call the Backup API / CLI to copy the snapshot backups to destination vault (account B Region B).