Two teams at Parcel run separate APIs for orders and reports on AWS, and both use the same network. When an engineer reviewing the monthly bill asks who owns an EC2 charge, the orders team points out that its API runs on App Runner. Another team suspects the shared network. The AWS service name identifies what AWS billed, so the engineer needs the details of the charge to find the app or team that used the resource.
Start with the account, Region, usage type, and resource details on the billing line. Match those details to your inventory before assigning an owner. If you find a resource that several apps share, record the rule you use to divide its charge so the teams can check their shares.
Save the charge before looking for its owner
Parcel is a hypothetical example, and the amounts below are illustrative. The engineer saves the billing period and the exact line, including the account, Region, service, usage type, amount, and cost measure. The record also shows whether AWS listed the line as usage, a fee, a credit, tax, or another adjustment.
With the dates and filters, another person can find the same billing line after new data changes the total they see in the console.
In Cost Explorer, filter to the account and service, then narrow by Region and usage type. Group by an active owner or app tag when one is available. The detail you can see depends on the report and underlying data. AWS Cost Explorer filters
Keep the same cost measure as you move between views. If one person uses a different measure, the amounts may disagree even when both have selected the same resource.
Match full identities rather than short names
Parcel has a service named orders in both staging and production. A name match alone could send the charge to the wrong team budget. The engineer checks the full resource identifier where available, along with the account and Region.
Use the inventory to connect the resource to its app, environment, repository, and owner. If the billing detail lacks a resource identifier, record that gap and check infrastructure records, deployment dates, and how long the possible resources ran to narrow the match.
A resource can appear on a bill after someone has deleted it, so search records from the billed period if you cannot find a match in today's console.
Keep each conclusion tied to its evidence. “This identifier belongs to the production orders database” is stronger than “the amount looks about right for orders.” A guess can stay in the investigation note until someone confirms it.
Use tags to keep the match easy next month
Parcel tags a resource with app=orders, environment=production, and owner=checkout-team. The values match the inventory, so a new teammate can look up the resource and contact the people who know why it exists.
Adding tags to a resource and activating them for billing are separate steps. AWS requires cost allocation tags to be activated for reports, and tags can take time to appear. Check coverage for the period under review before expecting a new tag to explain an old charge. Keep secrets and personal data out of tag values. AWS cost allocation tags
Tags also need upkeep. A resource may move between teams while keeping an old owner value. Review tags when ownership changes and when new resources are created. The goal is for the report and the real service owner to agree.
Keep a shared charge visible
Parcel's orders and reports APIs use one network path that the platform team owns. The engineer can identify the owner from the inventory, then decide with both app teams how to budget for the shared cost. They can leave it with the platform team, agree to a fixed split, or divide it using a measurement that reflects the billed work. Record why the teams chose that rule.
Suppose Parcel has a $40 shared line and a matching measurement that attributes 75 percent of the relevant bytes to orders. If the teams agree to use that rule, orders receives a $30 share and reports receives $10.
| Amount | What the record should say |
|---|---|
| $40 | Charge tied to the shared network resource |
| $30 | Share assigned to orders using the agreed bytes rule |
| $10 | Share assigned to reports using the same rule |
The split is called an allocation. AWS billed one shared resource, and Parcel assigned shares of that charge using the agreed rule. Record the measurement period and any traffic the measurement missed so each team can see how much of the billed work the split represents.
Ask the owner to confirm what ran
Once the engineer has a likely match, the owner should review the charge row, resource identity, and app mapping. For a shared cost, include the allocation rule too. Ask what work ran during that period.
A nightly export, a forgotten staging service, or a temporary database can explain a charge that the app's request count misses. The owner's context helps test the match. Save their conclusion in the cost record so the next review can start there.
Keep unresolved amounts in an unassigned row so the next reviewer can see where tags, inventory, or billing detail need work.
Carry the same ownership record into Forte
For a Forte Service, connect its project, Service name, repository, and owner in your inventory. Review provisioned instances, active compute, and builds as separate units. Keep managed databases on their own line so their owner can check storage and usage. Forte pricing and quotas
Forte lists observability, managed ingress, and data transfer without separate add-on fees. Those inclusions change which rows you budget for. AWS resources and outside services that remain in use still need their own ownership records. Forte service rates
More than one provisioned Service instance or a non-default Service size requires verified billing. Databases have their own tier limits and access requirements. Check those details against the workload before comparing a Forte estimate with an allocated AWS charge.
Once Parcel confirms the owner and any shared rule for the charge, the team can use the pricing guide to compare the same workload. Keep the record with the inventory so the next reviewer knows whom to ask when the charge changes.