Which solution will meet these requirements with the LEAST operational overhead?
Turn on the cross-account management feature in AWS Backup. Create a backup plan that specifies the frequency and retention requirements. Add a tag to the DB instances. Apply the backup plan by using tags. Use AWS Backup to monitor the status of the backups.
Turn on the cross-account management feature in Amazon RDS. Create a snapshot global policy that specifies the frequency and retention requirements. Use the RDS console in the management account to monitor the status of the backups.
Turn on the cross-account management feature in AWS CloudFormation. From the management account, deploy a CloudFormation stack set that contains a backup plan from AWS Backup that specifies the frequency and retention requirements. Create an AWS Lambda function in the management account to monitor the status of the backups. Create an Amazon EventBridge rule in each account to run the Lambda function on a schedule.
Configure AWS Backup in each account. Create an Amazon Data Lifecycle Manager lifecycle policy that specifies the frequency and retention requirements. Specify the DB instances as the target resource Use the Amazon Data Lifecycle Manager console in each member account to monitor the status of the backups.
Explanations:
AWS Backup with cross-account management supports centralized backup management across AWS accounts in AWS Organizations. Creating a backup plan with the required frequency and retention and applying it by tags allows low operational overhead.
Amazon RDS does not provide a “snapshot global policy” feature, and RDS’s cross-account management does not support creating centralized policies for snapshot frequency and retention.
This option has higher operational overhead due to the need to deploy CloudFormation stack sets, create a Lambda function, and configure EventBridge rules, making it more complex than needed.
AWS Data Lifecycle Manager does not support RDS snapshots, and this option lacks cross-account centralized management, requiring per-account configuration and monitoring, which increases operational overhead.
If I’m correct, the answer is:
Turn on the cross-account management feature in AWS Backup. Create a backup plan that specifies the frequency and retention requirements. Add a tag to the DB instances. Apply the backup plan by using tags. Use AWS Backup to monitor the status of the backups.