After several months of CloudWatch and Cost Explorer data, a citizen portal’s EC2/Fargate baseline CPU and spend look steady across business hours. Finance asks whether to adopt a commitment discount. Which action best adopts Savings Plans appropriately?
Select an answer to reveal the explanation.
Short Explanation
When the citizen portal’s baseline finally looks flat, that’s when Savings Plans earn their keep. Size the commitment to measured steady-state—not the biggest SKU on the menu. Spot-only for the whole portal is a different bet.
Full Explanation
Savings Plans should follow evidence: Cost Explorer recommendations and multi-week utilization baselines for steady citizen-portal compute. Compute Savings Plans offer flexibility across instance families and some compute services once steady-state is proven. Oversized single-family commitments without analysis, Spot-only mandates, or ignoring recommendations undermine appropriate price-model adoption.