Several teams run resources in the same AWS account.
Apply a Team tag to each resource and compare team spending in cost analysis.
Which setup should be made first?
Apply consistent user-defined tags and activate their keys as cost allocation tags so cost tools can use them as dimensions.
Detailed explanation
IAM identities do not classify resource charges by team.
IAM identities do not classify resource charges by team.
AZ placement is not a team classification in billing data.
AZ placement is not a team classification in billing data.
The total alone does not identify which team incurred the cost.
The total alone does not identify which team incurred the cost.
A consistent tag key and Billing activation provide a dimension for cost analysis and reports.
A consistent tag key and Billing activation provide a dimension for cost analysis and reports.
Check official documentation
Compare the following points with the official documentation.
AWS Billingのユーザー定義コスト配分タグの有効化とレポート反映を確認する。
Official references
What to confirm
一貫したタグキーとBilling側の有効化が費用配分の前提だと説明できる。
Key points
- User-defined tags
- Cost allocation tags
- Consistent tag keys
Notes
- Environment:
- Billing features, report formats, and prices can change; confirm current behavior in the AWS documentation before implementation.
Foundation review
Apply versus activate
Tagging a resource and enabling its key for billing analysis are separate operations.
Consistent classification
A controlled vocabulary for tag values makes team totals comparable.