Inference Public

FinOps

Who is responsible for the part of the AWS bill nobody recognises?

Shared networking, logging and security costs do not become somebody else's problem because they sit outside an application account.

Plain counters grouped in trays, with a separate group between them.

The service owners recognise their own accounts. Then finance adds the shared-platform line and the meeting becomes more animated. Nobody disputes that networking and security are necessary. They dispute why their service should pay that particular amount.

This illustrative situation is an allocation problem before it is an optimisation problem. You cannot have a useful conversation about a service's running cost while a material part of it is distributed by a rule nobody can explain.

Separate three questions

Who operates the shared component? Who authorises its budget? How is its cost attributed to the services that benefit? Those questions can have three different answers. Assigning an application owner a share of a network bill does not give that person authority to change the network.

Start with a cost boundary and period. Record which accounts, services, support charges, commitments, credits and taxes are included. Choose a consistent cost basis and retain the source that makes it reproducible. Comparing a discounted amortised view in one month with a different basis in the next can manufacture a trend that has no engineering cause.

Choose an allocation rule that supports a decision

There is no universally correct rule for every shared service. Useful options include keeping an agreed foundation cost central, distributing a fixed part equally, allocating a variable part by measured consumption, or using a proxy such as an agreed service tier.

Each changes incentives. Allocation by account count encourages consolidation even when separation is useful. Allocation by traffic can penalise an efficient shared integration. Allocation by team size may be easy to administer while saying little about actual consumption. A proxy can be defensible if its limits are explicit and everyone understands the purpose.

The FinOps Foundation's allocation guidance provides the broader capability context. The engineering and finance work is to choose a rule for this cost pool, keep it explainable and review it when the estate changes.

Work through a small example

All amounts below are invented for illustration. They are not AWS prices, client data or a savings claim.

Suppose a monthly shared cost pool is GBP 3,000. The organisation agrees that GBP 1,200 represents a common foundation split equally between three services. The remaining GBP 1,800 follows an agreed measured-use ratio of 50%, 30% and 20%.

ServiceEqual foundation shareMeasured-use shareTotal allocation
AGBP 400GBP 900GBP 1,300
BGBP 400GBP 540GBP 940
CGBP 400GBP 360GBP 760
TotalGBP 1,200GBP 1,800GBP 3,000

The arithmetic reconciles. That establishes only that the pool has been distributed without losing or adding money. It does not establish that the split is fair, causally accurate or appropriate for every future month. The decision record must identify the measurement, its quality, exclusions, approver and review date.

If measured-use data covers only 80% of the variable pool, say what happens to the remainder. Do not silently redistribute it across the known services and report 100% attribution as though the data were complete.

Keep an explicit unallocated category

An unresolved cost is useful information. It might be an account with no owner, an inherited commitment, a shared service with incomplete measurement or a resource whose purpose has been forgotten.

Give unresolved amounts an investigation owner and a next action. Avoid assigning everything to 'shared services' merely to remove the unallocated bar from a chart. That changes the label without improving understanding.

AWS Cost Categories can group costs using rules that reflect the organisation's structures. Tags, account boundaries and usage information can contribute to those rules. The tools apply a model; they do not decide who should own an ambiguous service or whether an allocation proxy is acceptable.

Keep cost attribution separate from savings

Moving GBP 400 from a central budget to a service budget does not reduce total expenditure. It changes who sees or pays for it. Likewise, rightsizing a shared component and reallocating its remaining cost are distinct changes. Record them separately so the same benefit is not counted twice.

After an engineering change, compare the observed bill with the baseline while considering workload demand, discounts, service level and one-off credits. Show estimated opportunity, implemented changes and observed financial effect as different fields. A budget presentation should not turn all three into a single savings total.

Give the review somewhere to land

A monthly review needs a finance contact, an engineer who understands the running service and an owner authorised to decide the trade-offs. Bring the few material unresolved allocations and candidate changes, not an undifferentiated export of every billing line.

For each proposed engineering change, record the affected service, expected effect, operational constraint, implementation owner and verification method. An alert without a response owner and a recommendation without change capacity are observations, not a cost-management practice.

Start with one shared cost pool. Reconcile it, document the allocation and make one decision it supports. That creates a repeatable basis for understanding the next month's bill.

Use the cloud cost and ownership worksheet, read about FinOps, or discuss a scoped cost review.

Further reading

FinOps Foundation: allocation

FinOps Foundation: unit economics

AWS: organising costs using Cost Categories

All insights

Start a conversation

Let’s talk about what you need to build.

Bring the service, the constraint or the engineering question. We’ll work through a sensible starting point.

Discuss a project