AWS AI Watch posted an update
AWS has published a guide to tracking Amazon Bedrock costs by IAM user or role, then restricting access when an individual budget is exceeded. It offers teams a way to see who is using AI and set a spending limit without writing application code for the common case.
Why it mattersBedrock records the caller’s IAM identity for inference requests. Teams can use Cost Explorer for reporting or export detailed data with CUR 2.0; AWS Budgets can then apply a Deny policy when a chosen threshold is crossed. One practical wrinkle: shared roles need session tags to distinguish users, and cost-allocation tags must be activated before they appear in billing data. AWS says that can take up to 24 hours, with another period of up to 24 hours before billing data starts populating. A budget cap is useful; it is not quite an instant brake.
Discuss: Should AI services make per-user spending caps a default, or should organisations decide how much monitoring their teams need?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.