Multi-account
A reservation's discount does not stay in the account that bought it.
AWS shares a Reserved Instance or Savings Plan discount with every account on the same consolidated bill, by default. A coverage number measured one account at a time is not the truth, and the account that gets the saving is often not the account that has to re-buy it.
First, the mechanic
A Regional RI's discount follows usage, not the account that bought it.
AWS treats every account under one AWS Organization's consolidated bill as a single account for billing purposes. A Regional Reserved Instance bought in one account can discount matching usage in a completely different account. It happens the moment that usage shows up.
AWS states this directly: "The pricing benefits of Reserved Instances are shared when the purchasing account is part of a set of accounts billed under one consolidated billing payer account." Sharing is on by default for every account in the organization. Only the management account can turn it off, for any account, including itself, per AWS's own sharing documentation.
A Zonal RI is the one exception. It reserves capacity only for the owning account, and it never shares, whatever the sharing setting says. Everything else below is about Regional RIs and Savings Plans, which do.
Why it matters
A per-account coverage number is not the truth.
Once a discount can float to a different account than the one that bought it, a single account's own coverage view can read too high or too low. The account that shows the usage isn't always the account holding the reservation.
An account can look under-covered while a reservation in a sibling account is quietly discounting its usage. Or it can look fully covered while the reservation paying for that discount belongs to a team that has since moved on, or closed its own account. Only the payer account's view, rolled up across every member account, tells you which one is true.
Does it reach another account?
Six situations, and whether the discount travels.
Sharing depends on the reservation type, the sharing setting on both sides, and whether an account or an AWS Organization is still in the picture at all.
| Scenario | Reaches another account |
|---|---|
| Regional RI, sharing on in both accounts | ✓the discount follows matching usage to any account on the same consolidated bill |
| Regional RI, sharing off in either account | ✗both the purchasing account and the account with the usage must have sharing turned on |
| Zonal RI | ✗AWS reserves capacity only for the owning account, whatever the sharing setting says |
| Purchasing account closed | ~other accounts keep the discount until the term ends, or until AWS permanently deletes the closed account 90 days after closure, whichever comes first |
| A Savings Plans owner account leaves the organization | ✗that Savings Plan no longer applies to the consolidated bill |
| A second AWS Organization | ✗a discount never crosses from one AWS Organization to another, even under Billing Conductor |
Reaches another account
- ✓Regional RI, sharing on in both accountsthe discount follows matching usage to any account on the same consolidated bill
- ✗Regional RI, sharing off in either accountboth the purchasing account and the account with the usage must have sharing turned on
- ✗Zonal RIAWS reserves capacity only for the owning account, whatever the sharing setting says
- ~Purchasing account closedother accounts keep the discount until the term ends, or until AWS permanently deletes the closed account 90 days after closure, whichever comes first
- ✗A Savings Plans owner account leaves the organizationthat Savings Plan no longer applies to the consolidated bill
- ✗A second AWS Organizationa discount never crosses from one AWS Organization to another, even under Billing Conductor
Two rows are worth spelling out. On the closed account, AWS's own account-closure reference sets the post-closure period at 90 days, counted from the day of closure to the day AWS permanently deletes the account. The discount stops at the end of that window, or at term end, whichever comes first. On the second organization, AWS states the limit plainly: "You can't purchase or share Reserved Instances and Savings Plans across multiple AWS Organizations."
Two more details worth knowing. Every account's active Reserved Instances also count toward a Region-wide volume discount tier, aggregated across the whole consolidated bill, not per account. AWS publishes the exact list-value threshold in its own pricing-tier documentation. And whichever sharing preference is in effect at 23:59:59 UTC on the last day of the month is the one used to calculate that month's final bill, per AWS's own billing documentation.
The renewal consequence
The account that benefits often isn't the account that must re-buy.
A shared discount can quietly become someone else's problem to renew. The team watching usage in one account may never see the reservation that's discounting it, sitting unrenewed in another.
Reserved Instances never auto-renew, on any account, shared or not. See the renewal playbook for the full mechanics. In a shared organization, the failure gets one extra step. Nobody notices the term end, because nobody in the account that benefits owns the reservation in the first place. Name an owner for every reservation, not just an account, or the renewal has nobody watching it.
What to do about it
Leave sharing on, unless finance says otherwise
Sharing is on by default because it raises the discount rate across the whole consolidated bill. AWS's own documentation warns that turning it off for an account can raise that account's monthly bill.
Measure coverage at the payer account, not per account
A single account's coverage number can read too high or too low. The reservation it's counting may have been bought, or claimed, somewhere else. Only the payer account's view, across every member account, is the truth.
Name the owner of every reservation, not just the account
The account that benefits from a shared discount is often not the account that bought the reservation. It is rarely the account that has to re-buy it either. Write down a person or team, not a line on an invoice.
Hold one renewal list for the whole organization
A renewal list kept per account misses a reservation whose benefit floated somewhere else. Keep one list for every account under the consolidated bill, with one owner.
How this scales with you
Two accounts already share a discount. Thousands hide it.
A two-account setup, one for production and one for development, already shares discounts by default. Nobody needs to buy a second reservation for the dev account by mistake; the production account's reservation already covers it.
A handful of accounts on one consolidated bill make sharing easy to overlook. A reservation bought against one team's account can end up discounting a different team's usage, and neither team notices until coverage looks wrong.
Hundreds or thousands of reservations, across many accounts and sometimes more than one AWS Organization. Only the payer account's own view is the truth. Anything measured account by account misses where the discount actually landed.
Where Reserver fits
One coverage map for every account you connect.
Reserver connects to your AWS accounts read-only, one account at a time today, and matches every reservation to the running usage it actually covers, wherever that usage lands. Auto-discovering every member account from a single connection is on our roadmap, not shipping yet. Connect each account in the organization and coverage rolls up across all of them, so the map reflects what the payer account sees, not what any one account sees alone. See features and the coverage playbook for the rest of what a coverage number needs to get right.
Does a Reserved Instance discount really apply to an account that never bought it?
Yes. Under AWS consolidated billing, a Regional RI's discount is shared automatically with every account in the same billing family, not just the account that made the purchase. AWS's own billing documentation states this directly.
Can we turn discount sharing off?
Yes, per account, from the management account's Billing preferences page. Both the account that bought the reservation and the account claiming the discount need sharing turned on for it to apply. AWS's own documentation warns that turning sharing off can raise the monthly bill, since it can leave usage that would have been discounted at the full on-demand rate instead.
What happens if the account that bought a reservation is closed?
The payer account keeps paying for the reservation until its term ends, and other accounts keep the discount during that time. A closed account still has a 90-day post-closure period. AWS permanently deletes the account at the end of it, and the discount stops for everyone at that point.
Does this apply to Savings Plans too?
Yes, the same sharing preference covers both. One difference: a Savings Plan's owner account has to stay active in the sharing preferences for the discount to reach anyone else. If that account leaves the organization, that Savings Plan no longer applies to the consolidated bill.
Sources, fetched and confirmed on 2026-09-08: how billing works with Reserved Instances and consolidated billing; Reserved Instances and Savings Plans discount sharing; Reserved Instance billing behavior across an organization; and the 90-day post-closure period on a closed AWS account.
Stop overpaying for a steady fleet.
Reserver is in early access. Join the list and we'll onboard you as capacity opens up. Your first recommendation lands within minutes of connecting.