An internal city intranet on EC2 is rarely used yet remains on large instance types. Which service provides rightsizing visibility for that compute?
Select an answer to reveal the explanation.
Short Explanation
If the city truck never leaves the lot, you do not keep paying for a semi-truck engine. Compute Optimizer looks at utilization and suggests a smaller EC2 size for that sleepy intranet.
Full Explanation
An internal city intranet that sits on large EC2 instance types despite rare use needs rightsizing visibility grounded in utilization metrics. AWS Compute Optimizer analyzes CloudWatch utilization and recommends downsizing or other rightsizing actions for over-provisioned EC2, which is exactly the signal municipal FinOps teams need before shrinking the sleepy intranet without guesswork. Acting on those recommendations reduces idle civic spend while keeping the service available for staff who occasionally need it.
Amazon Macie alone does not rightsize EC2; it discovers and classifies sensitive data such as PII, a different control plane. AWS Shield Advanced protects against DDoS and does not include instance downsizing advice as its cost-optimization purpose. Amazon QuickSight without utilization metrics as the only input can chart whatever you feed it, but it does not replace Compute Optimizer's EC2 rightsizing analysis role.
Exam caveat: pick the service whose primary job matches the requirement—Compute Optimizer for rightsizing recommendations, not adjacent security or BI tools. Operational check: enable Compute Optimizer for the intranet account, wait for recommendations, compare suggested instance type against observed CPU and memory, apply a change in a maintenance window, and confirm application latency and error rates remain acceptable afterward.