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.