AWS awsaccountbilling documentation change
Summary
Added documentation about viewing user attributes in Cost and Usage Reports (CUR 2.0) with tag prefix disambiguation
Security assessment
The change clarifies tagging implementation details for cost allocation reporting. While it improves documentation around data organization, there is no evidence of addressing security vulnerabilities or describing security controls.
Diff
diff --git a/awsaccountbilling/latest/aboutv2/user-attributes-cost-allocation.md b/awsaccountbilling/latest/aboutv2/user-attributes-cost-allocation.md index 033541fad..f1ee1bd7f 100644 --- a//awsaccountbilling/latest/aboutv2/user-attributes-cost-allocation.md +++ b//awsaccountbilling/latest/aboutv2/user-attributes-cost-allocation.md @@ -5 +5 @@ -OverviewHow User-Based Cost Allocation WorksKey BenefitsPrerequisitesSetting Up User Attributes for Cost Allocation +OverviewHow User-Based Cost Allocation WorksKey BenefitsPrerequisitesSetting Up User Attributes for Cost AllocationViewing User Attributes in Cost and Usage Reports @@ -19 +19 @@ Once you enable user attributes for cost allocation, when employees use AWS appl -Once you enable user attributes for cost allocation, you can map usage to internal organizational structures. You can use user attributes to see which teams, departments, or cost centers are consuming AWS services and at what rate, enabling data-driven decisions about resource allocation, budget planning, and optimization opportunities. This includes subscription-based charges and feature-specific overage charges, giving organizations a complete picture of their AWS application cost and usage. It works with existing AWS Cost Management like Cost Explorer and Cost and Usage Reports while gaining access to this new dimension of cost analysis. +Once you enable user attributes for cost allocation, you can map usage to internal organizational structures. You can use user attributes to see which teams, departments, or cost centers are consuming AWS services and at what rate, enabling data-driven decisions about resource allocation, budget planning, and optimization opportunities. This includes subscription-based charges and feature-specific overage charges, giving organizations a complete picture of their AWS application cost and usage. It works with existing AWS Cost Management tools like Cost Explorer and Cost and Usage Reports (CUR2.0 and FOCUS), giving you access to this new dimension for cost analysis. @@ -74,0 +75,4 @@ By enabling User-Based Cost Allocation, user attributes stored in AWS IAM Identi +## Viewing User Attributes in Cost and Usage Reports + +After completing the setup, user attributes will appear in your Cost and Usage Report 2.0 (CUR 2.0) alongside other cost allocation tags. When viewing cost data in CUR 2.0, tags from different sources (resources, user attributes, accounts, and cost categories) are distinguished by prefixes to prevent conflicts when the same tag key is used across multiple contexts. For detailed information about how tag prefixes work and examples of overlapping tag keys, see the [CUR 2.0 Tags Column documentation](https://docs.aws.amazon.com/cur/latest/userguide/table-dictionary-cur2-tag-columns.html). +