Using Cost-Tracking Tags
Cost-tracking tags are only relevant when you set budgets.
Required IAM Policy
Cost tracking is a feature of defined tags. To allow users to work with cost tracking, use the same IAM policy for working with tag namespaces and tags. For more information, see Required Permissions for Working with Defined Tags.
If you're new to policies, see Getting Started with Policies and Common Policies. If you want to dig deeper into writing policies for groups or other IAM components, see Details for IAM without Identity Domains.
Working with Cost-Tracking Tags
Suppose you have a defined tag key definition called Finance.CostCenter. You enable this tag key definition for cost tracking. You apply the tag with a value of "W1" (Finance.CostCenter="W1") to some resources, and you apply the tag with a value of "C2" (Finance.CostCenter="C2") to other resources. These tags enables the following scenario:
- Create one budget for resources tagged "Finance.CostCenter=W1" and a second budget for resources tagged "Finance.CostCenter=C2". If spending surpasses a certain amount or is forecast to exceed a particular threshold, you can set up alerts that notify you.
Limits on Cost-Tracking Tags
- You can have a maximum of 10 tag key definitions enabled for cost-tracking in your tenancy at a time. For example, you could enable the Project tag key as a cost-tracking tag and have 75 different departments, but it only takes up 1 tag.
Using the Console
Using the API
For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.
- ListCostTrackingTags - lists the tags that have been enabled for cost-tracking (can be performed in the root compartment only)