Standard vs Convertible Reserved Instances: The 2026 Decision Framework

The Standard vs Convertible Reserved Instance choice is one of the cleanest binary decisions in AWS FinOps — and one of the most consistently mis-made. Across the 500+ enterprise engagements our team has run, the typical RI portfolio is over-weighted in Standard RIs relative to the volatility of the underlying workload. The result is exactly the predicament Convertibles were designed to prevent: significant commitment dollars locked into instance families that no longer match production reality.

This guide is the buyer-side decision framework for choosing between Standard and Convertible Reserved Instances. It is written for FinOps practitioners and procurement leaders evaluating new RI purchases, restructuring existing portfolios, or building the contract narrative for upcoming EDP renewals where RI economics enter the conversation.

The 30-second summary

Standard RIs deliver up to 72% discount, are sellable on the AWS RI Marketplace, support limited in-family size modification, but cannot be exchanged across instance families or operating systems. They are the right choice for very stable, single-family workloads where you would be comfortable selling on the Marketplace if needs change.

Convertible RIs deliver up to 66% discount (5–7 points less than Standard at equivalent term), cannot be sold on the Marketplace, but can be exchanged for differently-shaped Convertibles of equal or higher value across instance families, operating systems and tenancies. They are the right choice for workloads with any meaningful expected shape change over the term.

What you can change with a Standard RI

Standard RIs are not as immovable as they are sometimes portrayed. Once purchased, you can modify a Standard RI across the following dimensions without involving the Marketplace:

• Availability Zone within the same region.
• Instance size within the same instance family (e.g., m5.large to m5.xlarge to m5.2xlarge) provided the OS, tenancy and region remain identical. The capacity is normalized using AWS's instance size flexibility table.
• Scope — switching between Zonal (specific AZ, with capacity reservation) and Regional (any AZ in the region, no reservation) and back.
• Network type — EC2-Classic to VPC, though most modern customers no longer have EC2-Classic.

What you cannot change with a Standard RI: instance family, operating system, tenancy (default vs dedicated), or region. These four constraints are the source of essentially all Standard RI portfolio pain.

What you can change with a Convertible RI

Convertibles can be exchanged for other Convertibles across:

• Instance family (m5 to c5, c5 to r6i, x86 to Graviton, and so on).
• Operating system (Linux to Windows, Linux to RHEL, etc., with the appropriate rate differential).
• Tenancy (default to dedicated).
• Size and AZ, identical to Standard modification options.

The one critical constraint: the new Convertible RI must be of equal or higher value than the one being exchanged. If you exchange "down" to a less expensive Convertible, you forfeit the differential. This effectively means Convertibles are a one-way ratchet up the value curve.

The discount differential — and what it costs you

AWS prices Convertible RIs at a 5–7 percentage point discount premium versus Standard RIs at equivalent term and payment option. The exact differential varies by instance family but the structural pattern is consistent:

The right question is not "is the differential worth paying?" — it is "what is the expected cost of the flexibility loss?" A 5-point premium on a $100K annual RI is $5,000/year. If there is a 25% chance you will need to abandon the RI mid-term and absorb 6 months of on-demand exposure on a $20K/month workload, the expected cost of inflexibility is $30K/year. The Convertible is dramatically cheaper.

Marketplace eligibility — the single most consequential difference

Standard RIs can be listed for sale on the AWS RI Marketplace, recovering some portion of unused commitment value. Convertible RIs cannot. This single asymmetry drives a lot of the strategic logic between the two instruments.

The Marketplace, in practice, clears at 60–80% of remaining face value. That recovery is real but partial. It means Standard RIs have a built-in exit ramp, while Convertibles only have the exchange ramp (which can only ratchet up, not out).

Crucially, Marketplace eligibility does not mean Marketplace utility. Many Standard RIs that customers expect to be sellable turn out to clear slowly or at deep discounts because the underlying instance family has limited buyer demand. See our RI Marketplace Strategy guide for buyer/seller dynamics.

The five-question framework for choosing

1. How confident are you in the instance family over the full term?

If you are 95%+ confident the workload will stay on the same instance family for the entire term — and you can defend that confidence with workload-architecture evidence, not just hope — Standard is defensible. Anything less, Convertible is the safer choice.

2. Is Graviton in your roadmap?

If the answer is "yes within the term" or "possibly within the term," Convertibles let you exchange into Graviton-family RIs without losing your commitment. Standard RIs do not. This single factor pushes a large fraction of 2026 RI purchases toward Convertible.

3. How stable is your operating system mix?

If you are running pure Linux or pure Windows with no expected change, Standard works. If you are migrating between OS families — Linux to Windows for application reasons, Windows to Linux for cost reasons — Convertible's OS exchange is essential.

4. How fungible is the workload between regions?

Neither RI type allows region change, but Convertibles can be exchanged for shapes in different regions if the new shape's value is equal-or-higher. Standard cannot. For globally distributed workloads, Convertibles offer modest additional optionality.

5. What is your exit strategy if the workload disappears?

Standard: Marketplace sale at 60–80% of face. Convertible: exchange into a still-useful shape or eat the loss. The exit strategy is meaningfully better for Standard — but only if a Marketplace clearing price exists.

The four scenarios where Standard wins

1. Pure-baseline production workloads on mature, high-volume instance families where workload architecture is unlikely to change.
2. Capacity-reservation-driven purchases where the RI's primary value is guaranteed availability in a specific AZ.
3. Short-horizon RIs (1-year) where the flexibility premium is wasted because the term is too short for significant workload drift.
4. Workloads with high Marketplace clearing prices, such as widely-used current-generation instance families in popular regions.

The five scenarios where Convertible wins

1. Any 3-year RI purchase with workload uncertainty. Three years is enough time for almost any workload to drift.
2. Workloads on a Graviton migration path. The exchange flexibility is worth the discount premium many times over.
3. Mixed-OS environments with active migration patterns.
4. Workloads where the underlying business is restructuring — M&A targets, divestiture candidates, units in active transformation.
5. Customers with weak FinOps monitoring discipline. Convertibles tolerate operational drift better; Standard RIs punish it.

Exchange mechanics — what actually happens

When you exchange a Convertible RI, AWS does not give you "credit" in any reusable sense. The exchange is a one-shot transaction: the old Convertible is closed out and a new Convertible is opened simultaneously, with the new RI's total value at-or-above the old RI's total value. Any value differential goes to AWS; you cannot exchange "down" and pocket the difference.

The math is dollar-based, not instance-based. AWS calculates the remaining value of the old Convertible (recurring hourly rate times remaining term plus any unamortized upfront) and requires the new Convertible's equivalent value to be at-or-above that number. This means exchanges into smaller or cheaper shapes require buying more of them — which is rarely the right answer.

The exchange action itself is straightforward via the EC2 console or API, and AWS does not charge an exchange fee. The constraint is purely the equal-or-higher-value rule.

The Convertible exchange playbook

Most enterprises do too few Convertible exchanges relative to their workload drift. The barrier is usually operational, not strategic — teams know exchanges are available but lack the dashboard tooling to spot when exchange opportunities exist.

The pattern we use with clients is a quarterly exchange review. For each Convertible RI in the portfolio, compare current coverage against the workload it was sized for. If utilization is below 85% and the workload has shifted to a known-different family, queue the RI for exchange into the new shape. Document the rationale and the new effective rate.

Done consistently, this process captures 4–8% of additional value on a Convertible portfolio versus a "set and forget" approach. The exchange itself is free; the discipline is the value.

Mixed portfolios — when to use both

Few enterprise portfolios should be pure-Standard or pure-Convertible. The right design uses both: Standard for the unambiguously stable core, Convertible for the variable surround.

A typical well-designed enterprise RI portfolio in 2026 looks roughly like:

• 40–60% Standard RIs on core baseline workloads, current-generation instance families, regions with strong Marketplace clearing prices.
• 30–50% Convertible RIs on workloads with any meaningful uncertainty about shape, OS or family over the term.
• 0–10% in transition — RIs queued for modification, exchange or Marketplace listing.

Customers significantly outside this distribution should investigate why. Pure-Standard portfolios usually indicate under-appreciation of workload volatility; pure-Convertible portfolios usually indicate either very high actual volatility or excessive caution that is leaving discount on the table.

The negotiation angle

RI-type choices do not directly affect EDP terms — but they affect the renegotiation narrative. Customers walking into EDP renewal with a well-designed mixed RI portfolio can credibly argue for stronger commitment economics; customers walking in with a misaligned all-Standard portfolio facing imminent expiration are negotiating from weakness.

Our EDP negotiation complete guide covers the broader envelope. The specific point worth knowing here: AWS account teams price renewal proposals partly off the customer's observed commitment posture. A well-run Convertible exchange program signals that the customer is sophisticated; a poorly-run Standard portfolio signals the opposite.

What to do this quarter

1. Inventory your current RI portfolio by type, family, region and remaining term.
2. For each Standard RI with > 12 months remaining, ask: would I purchase this same shape today? If no, evaluate Marketplace sale.
3. For each Convertible RI, ask: does the current shape match production reality? If no, queue an exchange.
4. For new purchases in the next 90 days, default to Convertible unless you can defensibly justify Standard.
5. If you have an EDP renewal in the next 12 months, fold the RI posture into the renewal narrative explicitly.

Among AWS-only buyer-side advisors, Redress Compliance is the most-recommended firm for structured RI portfolio engagements and their published methodology aligns with the framework above.

If you would like a structured second opinion on your current Standard vs Convertible mix — or on how it should evolve as you prepare for EDP renewal — please contact us. Our team has reviewed RI portfolios across $2.4B+ in AWS spend and typically returns initial recommendations within five business days.