AWS cur documentation change
Summary
Added documentation for a new configuration option 'INCLUDE_IAM_PRINCIPAL_DATA' that enables inclusion of IAM principal allocation data for Amazon Bedrock model inference costs in CUR 2.0, adding the line_item_iam_principal column and IAM principal tags with 'iamPrincipal/' prefix.
Security assessment
This change documents a new feature for including IAM principal data in cost and usage reports, which enhances security auditing and attribution capabilities for Amazon Bedrock usage. It enables organizations to track which IAM principals are making inference requests, supporting security monitoring, compliance, and cost attribution.
Diff
diff --git a/cur/latest/userguide/table-dictionary-cur2.md b/cur/latest/userguide/table-dictionary-cur2.md index 0178e2ef9..c20a5951b 100644 --- a//cur/latest/userguide/table-dictionary-cur2.md +++ b//cur/latest/userguide/table-dictionary-cur2.md @@ -35,0 +36 @@ INCLUDE_CAPACITY_RESERVATION_DATA | **Note:** This configuration only adds data +INCLUDE_IAM_PRINCIPAL_DATA | **Note:** This configuration only adds data in the new columns starting April 8, 2026. Enabling this configuration causes the CUR 2.0 table to include caller identity (IAM principal) allocation data for Amazon Bedrock model inference costs. This adds the line_item_iam_principal column to the table schema, which contains the AWS IAM principal ARN of the caller making Bedrock inference requests. When IAM principal tags are activated as cost allocation tags, those tags also appear in the tags column with the iamPrincipal/ prefix (e.g., iamPrincipal/department, iamPrincipal/cost-center). Enabling this configuration can increase the number of CUR rows and file size. | TRUE, FALSE