Compute Optimizer and CloudWatch show an Auto Scaling group for a library catalog tier chronically underutilized on oversized instance types. Which rightsizing action is most appropriate?
Select an answer to reveal the explanation.
Short Explanation
Paying for a moving van to haul a backpack is classic chronic underuse. Compute Optimizer plus CloudWatch are waving the receipt—shrink the instance type in the launch template and roll the group. Rightsizing is continuous improvement, not a one-time purchase order.
Full Explanation
Assessing solutions for rightsizing uses Compute Optimizer and utilization metrics to select instance types that match actual demand. Updating the launch template and performing an instance refresh or rolling replacement applies the new size safely. Growing unused capacity, claiming ASGs cannot change types, or defaulting to largest bare metal wastes spend and misses performance-efficiency goals. Continuous improvement periodically revalidates ASG sizing for municipal workloads.