Untangling shared costs on AWS.

The reason this matters: you cannot hold a team accountable for spend it cannot see, and you cannot make a sound commitment decision while a quarter of the bill is floating. Here is the order of operations that works.

Where do shared costs come from on AWS?

The Cost and Usage Report is the source of truth, and it makes the problem visible the moment you group by tag and find a large untagged remainder. That remainder is mostly five things. Data transfer is the quiet leader: traffic between availability zones, between regions, and out to the internet rarely carries a team tag, and NAT gateway processing charges ride alongside it. Shared services accounts holding logging, security tooling, and networking are billed centrally. Support fees scale with the estate but land in one place. And the discount from centrally purchased Savings Plans and Reserved Instances is spread across accounts in a way that hides who triggered it.

Tagging fixes part of this but never all of it, because some costs are genuinely shared. The goal is not to tag the untaggable, it is to allocate it with a key you can defend.

Use amortized cost, not blended cost

AWS gives you three cost measures in consolidated billing, and the choice changes every team's number. Blended cost averages the discounted rate across all accounts in the Organization, which is convenient and misleading, because it makes a heavy committer look the same as a team that bought nothing. Unblended cost shows each account the rate it actually paid. Amortized cost spreads the up front and recurring portions of commitments across the periods they cover.

For allocation, use amortized cost. It is the only measure that charges a team the effective rate for what it ran rather than the accident of when finance purchased a commitment. Blended cost is the single most common reason a shared cost allocation does not survive scrutiny: a team disputes its number, you trace it, and discover the figure was an Organization wide average that never described their usage.

Allocate each shared line with a documented key

Once you are on amortized cost, attack the remainder line by line. The principle is the same as anywhere in FinOps: pick a key that tracks the real driver of the cost and apply it identically every month.

Note that the commitment discount mostly allocates itself once you use amortized cost, because the Cost and Usage Report attributes the covered usage to the account that ran it. That removes the largest and most contentious piece of the puzzle before you start hand allocating anything.

Reduce shared cost, do not just allocate it

Allocation makes the cost visible and owned, but the bigger prize is shrinking it. Data transfer and NAT gateways are classic quiet budget eaters, and once a team sees its true network share it usually finds architecture changes worth making, such as VPC endpoints, regional consolidation, or moving chatty services into the same availability zone. Logging volume often turns out to be the driver behind both transfer and storage. The point of untangling is to turn an unowned number into a number a team can act on this week.

Where this fits in the AWS estate

Untangling shared costs is the foundation for accountable budgets and sound commitment decisions across AWS. It pairs directly with disciplined tagging and a clean account structure. Read tagging for cost allocation on AWS to get the inputs clean, and multi account strategy and cost control for the structure that makes allocation tractable. The whole estate picture lives in the AWS cost optimization guide.

Untangle your AWS bill with us

We help enterprises turn an unowned shared cost bucket into accountable, defensible numbers and then cut the spend underneath it. Our guarantee: we reduce your cloud spend or we reimburse our service fee. Pricing is either a Fixed Fee scoped up front or Gainshare, a share of verified savings with no retainer and no risk.