Support AWS CUR 2.0 IAM Principal Allocation Data for AWS Bedrock Cost Allocation in Cloudability

Many customers are starting to adopt Generative AI services such as Amazon Bedrock and need more granular visibility into cost allocation and consumption patterns.
AWS recently introduced a new capability in CUR 2.0 called “Include caller identity (IAM principal) allocation data”, which allows AWS usage and costs to be associated with the IAM principal (IAM Role/User) responsible for the consumption. Since IAM Roles can already be tagged, this enables organizations to allocate and report Bedrock costs based on teams, applications, business units, environments, or other governance models tied to IAM Roles.
Currently, this data does not appear to be ingested or exposed in Cloudability.

Why is this useful?

This feature would significantly improve cost transparency and accountability for AI/ML workloads, especially for Amazon Bedrock usage, where costs are often generated dynamically by applications and services assuming different IAM Roles.

By supporting IAM principal allocation data from CUR 2.0, customers would be able to:

• Track Amazon Bedrock costs by IAM Role
• Allocate GenAI costs to specific applications, teams, or business units
• Improve FinOps governance for AI consumption
• Better understand who or what is driving Bedrock consumption
• Leverage existing IAM Role tagging strategies for cost reporting

As GenAI adoption grows, granular visibility into AI-related cloud spend is becoming increasingly important for enterprise customers.

Who would benefit?

This enhancement would benefit:

• Customers using Amazon Bedrock
• Organizations implementing FinOps practices for AI/ML workloads
• Enterprises using IAM Roles for workload segregation and governance
• Cloudability customers looking for more granular AWS cost allocation capabilities
• Customers adopting CUR 2.0 advanced allocation features

This would be especially valuable for large enterprise environments where multiple applications, teams, or internal customers consume Bedrock services through different IAM Roles.

How should it work?

Cloudability should ingest and expose the IAM principal allocation data available in AWS CUR 2.0 when the customer enables the AWS option:

“Include caller identity (IAM principal) allocation data”

Suggested implementation ideas:

• Ingest IAM principal identifiers from CUR 2.0
• Expose IAM Role/User as dimensions within Cloudability
• Allow these dimensions to be used in:
  • Reports
  • Views
  • Dashboards
  • Business mappings
  • Allocation rules
• Support ingestion of IAM Role tags associated with the principal
• Enable filtering/grouping of Bedrock costs based on IAM principal metadata

This would allow customers to fully leverage AWS-native allocation capabilities inside Cloudability.