# Amazon — Amazon Bedrock tokenomics data lake

- Company: Amazon (amazon.com)
- Announced: 2026-11-10T16:56:36+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/amazon-bedrock-tokenomics-data-lake/
- Record: https://forck.live/items/34119-amazon-bedrock-tokenomics-data-lake
- Subject: Bedrock / Nova

Amazon published a guide to building a centralized observability data lake for Amazon Bedrock invocations, aimed at platform and ML engineers running Bedrock workloads across many accounts. The problem it addresses is that Bedrock's model invocation logging delivers a full record of requests and responses, but the data stays locked inside individual accounts, so teams see an aggregate bill without knowing what happened inside each call. The design pulls raw invocation logs from linked accounts into CloudWatch, forwards them through subscription filters to a central account, processes them with Amazon Data Firehose, and exposes them through Athena as one queryable table. Each flattened record carries the prompt, the model response, input and output token counts, the model used, the stop reason, the account and timestamp, and the IAM role that sent the prompt. A Lambda function unwraps CloudWatch's batched, compressed events, discards housekeeping messages, and lifts the nested caller identity to the top level. Firehose converts the records from JSON to Parquet and files each object under a date path, and an AWS Glue table lets Athena read the files with ordinary SQL. Everything deploys as infrastructure as code through two CloudFormation templates, with templates, Lambda code and SQL queries in the AWS Sample Bedrock Invocation Data Lake GitHub repository.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/amazon-bedrock-tokenomics-data-lake/:

> If you need an observability data lake for your Amazon Bedrock workloads, you’re not alone. When you’re running thousands of model invocations a day across multiple accounts, after a request is sent you might be wondering, what happened? You can see the aggregate bill, but you can’t see what happened inside each call.
> 
> You might start to ask questions: what prompt was sent, what the model returned, how many tokens it used, which model handled it, and whether the response was any good! If you’re a platform or machine learning (ML) engineer looking after a fleet of Amazon Bedrock workloads across teams, that’s a real problem. You can’t debug a spike, you can’t spot wasteful prompts, and you can’t tell one team’s usage from another’s.
> 
> We built something to help: a centralized observability data lake for your Amazon Bedrock invocations. In this post, I cover what native data you have and how we designed the lake. I also show how to use it to see your prompts and derive the per-invocation cost. The AWS CloudFormation templates, AWS Lambda code, and SQL queries are all in the AWS Sample Bedrock Invocation Data Lake GitHub repository .

---

Record: https://forck.live/items/34119-amazon-bedrock-tokenomics-data-lake
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
