A company has multiple Amazon RDS DB instances in a development AWS account. All instances are tagged as development resources. The company needs the development DB instances to run only during business hours. Which solution meets these requirements with the LEAST operational overhead?

The correct solution leverages EventBridge and Lambda for automated, scheduled operations. EventBridge allows you to define time-based schedules (e.g., cron expressions) that trigger a Lambda function. The Lambda function can then identify RDS instances based on their "development" tag and issue start/stop commands. This approach is highly automated and requires minimal ongoing operational overhead once configured. Incorrect options: CloudWatch alarms are typically used for monitoring metrics and triggering actions based on thresholds, not for scheduled start/stop operations. While a Lambda function can stop/start instances, CloudWatch alarms are not the primary scheduling mechanism here. AWS Trusted Advisor provides recommendations for cost optimization, security, and performance, but it does not directly facilitate the automation of starting and stopping RDS instances based on a schedule. AWS Systems Manager State Manager is designed for configuring and maintaining the state of EC2 instances, not for scheduling the start/stop of RDS instances.