What should a solutions architect do to meet these requirements?
Configure an IAM policy for AWS Systems Manager Session Manager. Create an IAM role for the policy. Update the trust relationship of the role. Set up automatic start and stop for the DB instance.
Create an Amazon ElastiCache for Redis cache cluster that gives users the ability to access the data from the cache when the DB instance is stopped. Invalidate the cache after the DB instance is started.
Launch an Amazon EC2 instance. Create an IAM role that grants access to Amazon RDS. Attach the role to the EC2 instance. Configure a cron job to start and stop the EC2 instance on the desired schedule.
Create AWS Lambda functions to start and stop the DB instance. Create Amazon EventBridge (Amazon CloudWatch Events) scheduled rules to invoke the Lambda functions. Configure the Lambda functions as event targets for the rules.
Explanations:
While configuring IAM policies and roles is important for access control, this option does not address the requirement of minimizing costs by automating the start and stop of the RDS instance itself.
Using ElastiCache for Redis could provide caching capabilities, but it does not help in minimizing costs related to the RDS instance as it still requires the DB instance to be running to populate the cache, which does not solve the primary requirement of stopping the DB instance during off-hours.
Launching an EC2 instance and using a cron job to manage it does not directly address the RDS instance’s running costs, as it involves maintaining an additional resource (EC2 instance) rather than just managing the RDS instance itself.
This option directly addresses the requirement by using AWS Lambda functions to automate the start and stop of the RDS instance based on a schedule defined in Amazon EventBridge, thus effectively minimizing costs by ensuring the DB instance is only running during required hours.