What should a solutions architect do to reduce costs with the LEAST operational effort?
Create an Amazon EventBridge rule that runs once every day. Configure the rule to invoke one AWS Lambda function that starts or slops instances based on me tag, day, and time.
Create an Amazon EventBridge rule that runs every business day in the evening. Configure the rule to invoke an AWS Lambda function that stops instances based on the tag. Create a second EventBridge rule that runs every business day in the morning. Configure the second rule lo invoke another Lambda function that starts instances based on the tag.
Create an Amazon EventBridge rule that runs every business day in the evening, Configure the rule to invoke an AWS Lambda function that terminates, instances based on the lag. Create a second EventBridge rule that runs every business day in the morning. Configure the second rule lo invoke another Lambda function that restores the instances from their last backup based on the tag.
Create an Amazon EventBridge rule that runs every hour. Configure the rule to invoke one AWS Lambda function that terminates or restores instances from their last backup based on the tag. day, and time.
Explanations:
While this option automates starting and stopping of instances, it may not effectively reduce costs since it operates on a daily basis without considering business hours specifically for development and testing environments.
This option optimally reduces costs by stopping instances outside of business hours for development and testing environments while keeping the production environment running 24/7. It utilizes EventBridge rules effectively with minimal operational effort.
Terminating instances instead of stopping them is not appropriate as it leads to data loss and requires restoration from backup, which is complex and increases operational effort.
Running an EventBridge rule every hour is overly frequent and may not be efficient for environments that do not require constant monitoring, leading to unnecessary operational overhead.
I reckon the answer is:
Create an Amazon EventBridge rule that runs every business day in the evening. Configure the rule to invoke an AWS Lambda function that stops instances based on the tag. Create a second EventBridge rule that runs every business day in the morning. Configure the second rule lo invoke another Lambda function that starts instances based on the tag.