A company has multiple Amazon RDS DB instances that run in a development AWS account. All the instances have tags to identify them as development resources. The company needs the development DB instan

Question

Options

• ACreate an Amazon CloudWatch alarm to identify RDS instances that need to be stopped Create
• BCreate an AWS Trusted Advisor report to identify RDS instances to be started and stopped.
• CCreate AWS Systems Manager State Manager associations to start and stop the RDS instances.
• DCreate an Amazon EventBridge rule that invokes AWS Lambda functions to start and stop the

• A
  16% (8)
• B
  10% (5)
• C
  4% (2)
• D
  71% (36)

Explanation

To run RDS instances only during business hours with the least operational overhead, you can useAmazon EventBridgeto schedule events that invokeAWS Lambda functions. The Lambda functions can be configured to start and stop the RDS instances based on the specified schedule (business hours). EventBridge rules allow you to define recurring events easily, and Lambda functions provide a serverless way to manage RDS instance start and stop operations, reducing administrative overhead. Option A: While CloudWatch alarms could be used, they are more suited for monitoring, and using Lambda with EventBridge is simpler. Option B (Trusted Advisor): Trusted Advisor is not ideal for scheduling tasks. Option C (Systems Manager): Systems Manager could also work, but EventBridge and Lambda offer a more streamlined and lower-overhead solution.

No community discussion yet for this question.