Amazon Bedrock Cost Allocation Now Covers the bedrock-mantle Endpoint Too

Hey, how's everyone doing? Shii-chan here! Today's update is a small but genuinely handy one for Bedrock cost management.

AWS What's New aws.amazon.com

What was announced?

According to AWS What's New, Amazon Bedrock's cost allocation by IAM principal (IAM users and roles) now covers model inference requests made through the bedrock-mantle endpoint. This extends a capability that was previously available only for the bedrock-runtime endpoint.

The story so far

Amazon Bedrock is a fully managed service that gives you secure access to a range of foundation models, but when multiple users, teams, and projects share the same Bedrock environment, it's been hard to track whose inference requests are driving costs. IAM-principal-based cost allocation already existed for the bedrock-runtime endpoint, but requests through the bedrock-mantle endpoint weren't covered.

What changes

If you tag your IAM users and roles with attributes like team, project, or cost center and activate them as cost allocation tags, you can now see bedrock-mantle inference costs broken down by those same tags in AWS Cost Explorer or AWS Cost and Usage Report 2.0 (CUR 2.0). That means you can properly attribute inference costs across users, teams, projects, and applications.

Dive Deep

Getting started is straightforward: activate your IAM principal tags in the AWS Billing and Cost Management console. From there, filter or group costs by those tags in Cost Explorer, or when creating a CUR 2.0 data export, select "Include caller identity (IAM principal) allocation data" to get line-item-level detail. This is available in every AWS Region where the bedrock-mantle endpoint is supported.

Wrap-up

• IAM-principal-based cost allocation now covers the bedrock-mantle endpoint
• Previously this only worked for the bedrock-runtime endpoint
• Costs can be attributed using tags like team, project, or cost center
• Viewable in Cost Explorer or at the line-item level in CUR 2.0
• Available in every AWS Region where bedrock-mantle is supported

If your team shares Bedrock across multiple groups and wants clearer visibility into who's spending what, this is a welcome update!