Cloud concept · Updated

Discount sharing - Discount sharing allows eligible usage across accounts in a common billing group to benefit from pricing discounts available to that group.

In short

Cloud providers can apply unused commitment-based discounts across linked accounts and aggregate eligible usage for volume pricing. This can reduce total costs without combining workloads into one account, but eligibility rules, sharing settings, and internal cost allocation determine who benefits.

Cloud Concepts Hub →

7 key aspects of Discount sharing

Discount sharing improves organization-wide pricing efficiency while preserving eligibility rules, account boundaries, and the need for explicit cost allocation.

01
Shared billing eligibility

Discounts can cross account boundaries only within the provider's eligible billing relationship. In AWS, consolidated billing through AWS Organizations establishes that relationship without merging account resources or permissions.

02
Commitment utilization across accounts

Unused commitment discounts can cover eligible usage in other participating accounts. This reduces stranded discounts when workloads move between accounts or fluctuate independently.

03
Matching rules still apply

Sharing does not remove restrictions such as Region, instance family, platform, or commitment scope. Verify the specific Reserved Instance or Savings Plan rules before estimating savings.

04
Configurable participation

The AWS management account can control which accounts participate in Reserved Instance and Savings Plans discount sharing. Excluding an account can preserve financial separation but reduce opportunities to use otherwise idle benefits.

05
Eligible volume aggregation

Consolidated billing can combine qualifying usage to reach volume-pricing tiers for supported services. This mechanism is separate from sharing discounts purchased through commitments.

06
Cost allocation remains necessary

The commitment owner, discount beneficiary, and organization paying the bill may be different accounts. Use account-level reporting and an explicit allocation policy to distribute commitment costs and savings fairly.

07
Billing benefits are not resource rights

Sharing a discount does not grant access to another account's resources or transfer capacity guarantees. EC2 zonal Reserved Instance capacity benefits remain with the owning account.

Cloud services for Discount sharing

AWS Organizations establishes the consolidated billing relationship, while AWS Billing and Cost Management provides payment visibility and discount-sharing controls. EC2 Reserved Instances and Savings Plans supply commitment-based benefits that can cover eligible usage across participating accounts. AWS Cost Explorer helps teams inspect utilization, coverage, and account-level costs to determine whether sharing is reducing unused commitments. Together, these capabilities support centralized purchasing without requiring centralized workloads. Teams still need an internal allocation policy because the account buying a commitment and the account receiving its discount can differ.

AWS OrganizationsAWS Organizations

Provides the multi-account structure and consolidated billing relationship that enable eligible discount sharing and usage aggregation. The management account pays the consolidated bill while member-account charges remain identifiable.

AWS Billing and Cost Management

Provides billing preferences for controlling Reserved Instance and Savings Plans discount-sharing participation. It also exposes consolidated charges and account-level billing information needed to reconcile shared benefits.

Amazon EC2Amazon EC2

EC2 Reserved Instance billing discounts can apply to matching usage across participating accounts under consolidated billing. Sharing the billing discount does not share a zonal Reserved Instance's capacity reservation benefit.

Savings PlansSavings Plans

Provides commitment-based pricing discounts that can apply across participating accounts when sharing is enabled. Coverage depends on the plan type and eligible usage, rather than on account membership alone.

AWS Cost ExplorerAWS Cost Explorer

Helps engineers analyze costs by linked account and inspect Reserved Instance and Savings Plans utilization and coverage. Amortized cost views help evaluate commitment economics alongside account-level spending.

What is Discount sharing

3 min read

Discount sharing separates the account that acquires a pricing benefit from the accounts whose usage can consume that benefit. In a multi-account cloud environment, one team might purchase a commitment while another team operates matching workloads. If the accounts belong to an eligible billing group and sharing is enabled, the provider can apply otherwise unused discounts across those accounts. The goal is better utilization of purchased commitments, not unrestricted transfer of discounts between unrelated customers.

In AWS Organizations, consolidated billing brings the management account and member accounts onto one consolidated bill. The management account pays the organization's charges, while billing tools retain account-level cost and usage information. Accounts remain separate administrative and security boundaries: consolidated billing does not merge their resources, grant access to another account's workloads, or make all services free between accounts.

Reserved Instance discount sharing is an important application. An Amazon EC2 Reserved Instance provides a billing discount for usage that matches its applicable attributes and rules. AWS first applies its benefit to eligible usage in the purchasing account; an unused benefit can then apply to matching usage in other participating accounts within the consolidated billing family. Sharing is enabled by default, and the management account can control participation through billing preferences. An account excluded from sharing does not share its Reserved Instance discounts with other accounts or receive theirs.

For example, a development account purchases a qualifying regional Reserved Instance but later stops its matching instance. A production account runs matching usage during the same billing hour. With sharing enabled and all eligibility conditions satisfied, the unused discount can reduce the production account's usage charges. The purchase remains associated with the purchasing account. Sharing does not let one reservation cover unlimited simultaneous usage, and an unused hourly benefit cannot be saved for a later hour.

AWS Savings Plans also support cross-account sharing of eligible discounts under consolidated billing. Their matching rules differ from Reserved Instances: a Compute Savings Plan covers a broader set of eligible compute usage, while an EC2 Instance Savings Plan has an instance-family and Region scope. Engineers should evaluate the actual commitment's coverage rather than assume that every discount applies to every workload.

Consolidated billing also aggregates eligible usage for volume-pricing tiers on supported services. This is distinct from sharing a purchased commitment: combining qualifying usage can reach a lower pricing tier without purchasing a Reserved Instance. Aggregation rules depend on the service and pricing dimension, so not every charge receives an organization-wide discount.

The main trade-off is between organization-wide savings and team-level financial independence. Sharing can improve commitment utilization, but the account purchasing a commitment may not be the account receiving every usage discount. Finance and engineering teams should agree on how to allocate upfront fees, recurring commitment charges, and realized savings. Account-level reports, cost allocation tags, and amortized cost views support this analysis; they do not automatically establish an internal chargeback policy.

Finally, a shared billing discount is not shared capacity. An EC2 zonal Reserved Instance's capacity reservation benefit is not shared across accounts, even when its billing discount can be shared. For exam questions, distinguish consolidated payment, eligible usage aggregation, commitment-discount sharing, and resource access: these are related billing considerations, not interchangeable capabilities.