Skip to main content

Rightsizing

AvailableReviewed 21 August 2026

Rightsizing recommendations compare recent utilisation with the current SKU. Accept records intent. Someone still resizes the instance in AWS, Azure or Google Cloud.

Use the provider chip, then open Details on a row.

AWS​

Filter Recommendations to AWS and type Right sizing. Typical rows are EC2 families (m6i, r6i) with 14-day CPU below ~40%.

AWS rightsizing table with current type, suggested type, 14-day CPU and estimated saving
Sample EC2 candidates. Confirm the workload is not spiky before you accept a downsize.

Then follow Review a recommendation. Implementation is in the EC2 console or your IaC — not in FinomateAI.

Azure​

Filter to Azure. Rows are Virtual Machine SKUs (Standard_D* and similar).

Azure rightsizing table with current SKU, suggested SKU and 14-day CPU
Sample Virtual Machines. Check availability set and reserved-instance fit before changing SKU.

Google Cloud​

Filter to GCP. Rows are Compute Engine machine types.

Google Cloud rightsizing table with machine type, suggested type and 14-day CPU
Sample Compute Engine. Committed use discounts can make a smaller type less valuable — check [Commitments](/docs/optimisation/commitments) if that view is enabled.

What FinomateAI will not do​

Connectors are read-only. There is no “apply in AWS” button. If a recommendation is Ready, the owner still performs the change and Savings Tracker waits for a later bill to confirm it.