AWS adds credit splitting, allowing up to 100 splits per credit family
The new capability lets FinOps teams divide credits by dollar amount, percentage or custom rules. It is available in all commercial regions at no extra cost.

Each credit family can be split up to 100 times.1
Each split credit must be at least $100.1
The feature is available in all AWS commercial regions at no additional cost.1
Story
AWS launches credit splitting and transfersOn November 17, 2026 AWS announced that it now supports credit splitting and transfers.1 Previously the service applied credits to the owning account and then shared any excess based on usage.1 The new feature enables FinOps teams to split credits by dollar amounts, percentages, or custom splits.1 Each split retains the original credit’s expiration date and service eligibility.1 With splitting, FinOps teams can assign specific credit amounts to teams instead of depending solely on the prior arrangement, where the owning account used credits first and excess was shared according to usage.1 Dollar-based, percentage-based and custom allocations provide different ways to express a budget, so teams can choose the form that fits how they want credit amounts divided.1 Splitting leaves the original credit’s expiration date and service eligibility in place for each resulting credit.1 That continuity matters for the teams receiving allocations: they get a portion with the same time limit and service scope as the source credit, rather than a credit with different stated conditions.1 The feature is intended to give FinOps teams predictable credit budgets for teams or business units while reducing monthly manual chargeback work.1 The allocation options describe how a credit can be divided, while the retained expiration and service eligibility specify which conditions remain attached to the resulting credits.1
Accounts that receive transferred credits are given first‑priority consumption for those credits.1 Credit splitting works together with existing credit‑level sharing and credit pausing features.1 After a split, customers maintain full control over each resulting credit, including the ability to share or restrict it.1 Customers can also pause a split credit earmarked for a future project and resume it later.1 First-priority consumption means the receiving account gets priority when consuming the transferred credits, an important distinction for teams that have been assigned a specific credit balance.1 The ability to share or restrict each resulting credit gives customers another choice after allocating it: they can allow further sharing or keep that credit limited.1 Pausing and resuming a credit earmarked for a future project lets customers hold that allocation for later use rather than leaving it active throughout the period before the project begins.1 Together, compatibility with sharing and pausing means that splitting does not require customers to give up those existing ways of managing credits.1 The receiving account’s first-priority status applies to the transferred credits, while the controls to share or restrict apply to each credit after a split.1 These features offer customers ways to manage both the destination of credits and whether a credit reserved for a future project is paused or resumed.1
Splits can be created through the AWS Billing Console, the CLI, or the API.1 When a credit is only partially consumed, only the remaining balance is eligible for further splitting.1 Each credit family supports up to one hundred splits.1 The minimum size for any split credit is one hundred dollars.1 Having three ways to create a split gives customers a choice of interface: they can use the Billing Console, CLI, or API to carry out the allocation.1 The limit applies to each credit family, while the minimum applies to each split credit; the two conditions therefore shape both how many allocations can be made and how small an individual allocation can be.1 A customer cannot divide an already-used portion of a credit again: if it has been partially consumed, the available amount for another split is only the balance left.1 These boundaries are relevant to teams designing allocations, since they need to work within the per-family split cap and ensure each resulting split meets the stated minimum.1 The remaining-balance rule means that the amount available to divide can be smaller than the original credit when some of it has already been consumed.1 Taken together, the split cap and minimum size set limits on the number and scale of allocations, while the three supported interfaces determine how customers can create them.1
Splits are permanent and cannot be undone once created.1 The capability is offered in all AWS commercial regions without additional charge.1 FinOps teams report that the feature eliminates hours of monthly manual chargeback work.1 It also provides predictable credit budgets per team or business unit.1 Because splits cannot be reversed, customers need to decide on an allocation before creating one; the split is permanent once made.1 That planning must take account of the minimum split size and the maximum number of splits supported for a credit family, which set limits on allocation choices.1 Availability across all AWS commercial regions and the absence of an additional charge mean that the announcement specifies no regional exclusion or extra feature cost for customers in those regions.1 The reported reduction in monthly manual chargeback work points to a potential operational benefit for FinOps teams, while predictable budgets are described for teams or business units that receive credit allocations.1 For teams weighing the feature, the practical considerations include its permanent nature, the per-family split limit and the minimum size of each split.1 The stated benefits concern FinOps teams’ monthly chargeback work and the predictability of credit budgets for teams or business units.1
Structure
Who is connected to whom- 1Amazon
- invests in →Fact
- ← part ofFact
- operates in →Fact
- ← competes withFact
- uses →Fact
History
How it came to this- November 17, 2026AWS announces credit splitting and transfersAWS says customers can split and transfer credits, expanding on the earlier approach of applying credits to the owning account before sharing any excess based on usage.
- NowAvailable AWS credit splitting and transfers
Impact
Spreading outward, level by level- Level 1Credit allocation
FinOps teams can divide credits by dollar amounts, percentages, or custom splits. Each resulting credit retains the original credit’s expiration date and service eligibility.1
Fact - Level 2Receiving accounts
Accounts receiving transferred credits get first-priority consumption for those credits.1
Fact - Level 3Credit management
Customers can share or restrict each resulting credit and can pause a split credit for a future project, then resume it later; the feature also works with existing credit-level sharing and pausing.1
Fact - Level 4FinOps operations
AWS says the feature eliminates hours of monthly manual chargeback work and provides predictable credit budgets for teams or business units.1
Fact - Level 5Allocation planning
Because splits are permanent, customers may need to plan allocations carefully around the minimum split size and the limit for each credit family.
Analysis
Sources
What each source supportsWritten by AI from the sources listed below: every fact was checked word for word against its source, and inference is marked apart. How we write