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

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.

AI 根据报道生成 · 13 小时前更新

1. 11月14日 02:44 · 1篇报道
   AWS Explains Cost Attribution and Controls for AI Tools on Amazon Bedrock
   AWS Machine Learning Blog：如何在 Amazon Bedrock 上归属和控制 AI 工具成本
2. 11月13日 03:29 · 1篇报道
   AWS Explains Tracking and Capping Amazon Bedrock Spend per IAM Principal
   AWS Machine Learning Blog：如何按 IAM 主体跟踪并限制 Amazon Bedrock 支出