County non-production accounts run EC2 and RDS for QA all weekend even though testers only work weekday business hours. Leadership wants scheduled stop/start without redesigning every application. Which approach best uses scheduling to reduce cost?
Select an answer to reveal the explanation.
Short Explanation
QA that runs Saturday for nobody is burning the county’s overtime budget. Instance Scheduler stop/start on nights and weekends is the boring, correct win. Bigger RIs for idle QA just discounts the waste.
Full Explanation
Scheduling non-production compute and databases to stop outside business hours is a standard continuous-improvement cost control, commonly delivered with AWS Instance Scheduler or Systems Manager automation. It preserves weekday capacity without paying for idle nights and weekends. Deleting ASGs wholesale, buying more commitments for idle QA, or multi-cloud overnight moves are not appropriate substitutes for scheduling policies.