SYSTEM Cited by 2 sources
AWS Cost Explorer¶
What it is¶
AWS Cost Explorer is AWS's cost-analysis UI + API over the billing data exposed by AWS Organizations' consolidated billing. Dimensions: account, service, Region, tag, usage type, time. Supports forecasting and saved reports.
Role in account-per-tenant cost attribution¶
In an account-per-tenant architecture, tenant cost reporting is trivial:
"AWS Cost Explorer and linked accounts make it straightforward to report and charge back costs on a per-tenant basis. For SaaS providers with consumption-based pricing models, this becomes a strong advantage." (Source: sources/2026-02-25-aws-6000-accounts-three-people-one-platform)
The account boundary is the attribution boundary: every dollar spent in an account belongs to exactly one tenant, no tag-hygiene discipline required. This is one of the more under-appreciated benefits of account-per-tenant — in a shared-account SaaS, accurate per-tenant cost attribution requires every resource to be correctly tagged, every API call to propagate tags, and every shared service to be cost-split — a pile of work that account-per- tenant elides entirely.
Stub page.
Role in shared-application Bedrock attribution¶
For a shared Amazon Bedrock application, the account and IAM principal can both be too coarse: all departments use one application role. AWS's application inference profiles add a tagged resource boundary instead. The application selects a profile ARN for a trusted department; after the payer activates the Team cost-allocation tag, Cost Explorer can group the resulting Bedrock spend by that tag at daily or monthly granularity. This preserves a single application role while making the resource choice reportable. (Source: sources/2026-08-13-aws-track-generative-ai-costs-with-amazon-bedrock-inference-profiles)
This is billing-plane observability, not a real-time control loop: the source reports a 24–48-hour delay before newly activated tagged costs become visible. In Organizations, activation happens in the management account and member-account usage consolidates there. See chargeback-cost-attribution.
Seen in¶
- sources/2026-08-13-aws-track-generative-ai-costs-with-amazon-bedrock-inference-profiles — Cost Explorer groups shared-application Bedrock usage by activated
Teamtags applied to selected application inference profiles; reporting delay is 24–48 hours. - sources/2026-02-25-aws-6000-accounts-three-people-one-platform — canonical "transparent cost attribution" benefit of account- per-tenant.