A virtual machine, database instance, or container right-sized too large for its actual workload, with the consequence that a smaller and cheaper SKU would have served the same service level. Oversized instances are the most common rightsizing target. The federation requires oversize detection to be performed against trailing fourteen-day metrics, with the recommendation including a destination SKU, a forecast monthly saving, and a confidence score. Implementation evidence is recorded in the inform-to-operate ledger under UFMS-001:2.4 and reconciled against actual savings.
A compound of over and sized; the SKU-specific sense stabilised with the AWS instance family literature in the mid 2010s.
Federation members run oversize detection weekly with documented confidence scores. Implemented rightsizings are reconciled to actual savings within thirty days. Unimplemented recommendations older than ninety days are escalated to FinOps council review under MEV-Annex:3.2.
@misc{ifo4_glossary_oversized_instance,
title = {{Oversized Instance}},
author = {{IFO4 Federation Editorial Board}},
howpublished = {{IFO4 Federation Glossary, slug \texttt{oversized-instance}}},
year = {2026},
url = {https://ifo4.org/glossary/oversized-instance},
note = {Category: Waste; key: OversizedInstance}
}Federation members and accredited practitioners may challenge any entry under TGS-002:1.7. Filed challenges are routed to the editorial board, triaged into the revision register, and resolved in writing on the public docket. The slug remains stable through any revision.