Skip to content
K = 0.731Subscribe

AWS Details Cost Attribution and Spending Controls for AI Tools on Amazon Bedrock

2 reports 1 reporting sources first reported Updated 13 hours ago

Understand the event

AI overview

AWS explains how to attribute Amazon Bedrock inference costs to individual users of AI coding and productivity tools, then compare ways to control their usage. The guide configures IAM Identity Center session identities and tags for CUR 2.0 reporting, with Athena queries and dashboard options for analyzing per-user costs. It also compares AWS Budgets, CloudWatch alarms with Lambda, DynamoDB quotas, and LLM gateways as spending controls. AWS’s earlier walkthrough covers tracking Bedrock costs by IAM user or role with cost allocation tags, Cost Explorer or CUR 2.0, and AWS Budgets actions that attach a Deny policy. Budgets refresh up to three times a day, so spending can exceed a threshold before an action runs. Newly applied cost allocation tags can take up to 24 hours to appear and another 24 hours after activation to populate billing data. A Deny policy on a shared role blocks everyone using that role.

Generated by AI from reports · Updated 13 hours ago

Latest development11/14 02:44 (UTC+8)
How to Attribute and Control AI Tool Costs on Amazon BedrockAWS Machine Learning Blog

Read next

More changes in today’s briefingGoogle Expands Antigravity Teamwork for Research and Engineering

Developments

2 developments

  1. 11/14 02:44 (UTC+8) · 1 reports
    AWS Explains Cost Attribution and Controls for AI Tools on Amazon Bedrock
    AWS Machine Learning Blog：How to Attribute and Control AI Tool Costs on Amazon Bedrock
  2. 11/13 03:29 (UTC+8) · 1 reports
    AWS Explains Tracking and Capping Amazon Bedrock Spend per IAM Principal
    AWS Machine Learning Blog：How to Track and Cap Amazon Bedrock Spend by IAM Principal

Report timeline

Follow the reports to explore different sides of the event.

11/14
  1. AWS Machine Learning Blog
    How to Attribute and Control AI Tool Costs on Amazon Bedrock

    AWS authors explain how to track per-user costs for AI coding and productivity tools that route inference through Amazon Bedrock. The guide configures IAM Identity Center session identities and tags for CUR 2.0, then covers Athena queries and dashboard options. It also compares spending controls, including AWS Budgets, CloudWatch alarms with Lambda, DynamoDB quotas, and LLM gateways.

11/13
  1. AWS Machine Learning Blog
    How to Track and Cap Amazon Bedrock Spend by IAM Principal

    AWS authors explain how to track Amazon Bedrock costs by IAM user or role and enforce spend limits using cost allocation tags, Cost Explorer or CUR 2.0, and AWS Budgets. The walkthrough covers principal and session tags, Athena queries for detailed reporting, and budget actions that attach a Deny IAM policy. Budget data refreshes up to three times a day, and a shared role’s Deny action blocks everyone using it.

Keep up with AI, one email a day

Model releases, price changes and compute developments, with original sources. Free, confirmed by email, and easy to unsubscribe. Read a past issue

Event heat trend

Current within comparable coverage
7
Peak within comparable coverage
1011/13 04:00 (UTC+8)
24-hour change
-3%

Trends compare the same continuously observed participants, which may cover fewer sources than current heat. Point or click to inspect hourly heat, or use left and right arrow keys.