Loading content
Reserved Instances are committed-capacity purchases from cloud providers that reserve compute resources for a defined term in exchange for significantly lower hourly rates. They help optimize predictable infrastructure costs but require forecasting, contractual commitment and active monitoring. For variable workloads, savings plans or pay-as-you-go billing o…
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Theoretical construct: explains a term, principle, or mental model.
Concrete cog in the system that works inside larger relationships.
Reserved Instances are long-term capacity/price commitments that reduce ongoing compute costs by applying significantly lower hourly rates when usage matches the reservation.
Reserved Instances come from AWS’s Amazon EC2 pricing model: AWS offers a commitment-based option where customers buy a reservation for a fixed term (1 or 3 years) and AWS applies the benefit as a billing discount to matching On-Demand usage. In effect, the model turns “predictable” compute demand into a contractual price advantage, trading flexibility for cost savings.
Think of Reserved Instances as a discount that applies only to exactly matching usage. First you define the instance attributes so AWS later recognizes which On-Demand instances qualify (e.g., instance type, Region, tenancy, and platform). Next you choose how broadly the benefit applies (scope: regional or zonal), pick the term (one year or three years), and select an offering class, which influences how the reservation can be adapted when requirements change. Finally you choose a payment option (All Upfront, Partial Upfront, or No Upfront). When matching On-Demand instances run in your account, the discount is applied immediately to hourly charges; after the reservation expires, billing returns to On-Demand rates.
Control whether On-Demand usage counts as a match; AWS lists key attributes such as instance type, Region, tenancy, and platform.
Determines where AWS applies the discount for billing—regional versus zonal.
Reserved Instances are purchased for one or three years and do not renew automatically.
Defines flexibility for changing needs (AWS distinguishes, for example, Standard vs. Convertible).
Describe how much is paid up front and how the discounted hourly rate is applied over the term (All Upfront, Partial Upfront, No Upfront).
Reserved Instances help when you can forecast recurring compute capacity over a fixed period and want measurable savings versus On-Demand. The main trade-off is reduced flexibility: the discount depends on matching attributes and scope, the reservation ends without automatic renewal, and adaptability varies by offering class. For highly variable workloads, AWS explicitly recommends Savings Plans over Reserved Instances.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.