Tags

The Tags column represents the set of tags assigned to tag sources that also account for potential provider-defined or user-defined tag evaluations. Tags are commonly used for scenarios like adding business context to cost and usage data to identify and accurately allocate charges. Tags may also be referred to by providers using other terms such as labels.

A tag becomes finalized when a single value is selected from a set of possible tag values assigned to the tag key. When supported by a provider, this can occur when a tag value is set by provider-defined or user-defined rules.

The Tags column adheres to the following requirements:

• Tags MUST be present in a FOCUS dataset when the provider supports setting user or provider-defined tags.
• Tags MUST conform to KeyValueFormat requirements.
• Tags MAY be null.
• When Tags is not null, Tags adheres to the following additional requirements:
  • Tags MUST include all user-defined and provider-defined tags.
  • Tags MUST only include finalized tags.
  • Tags SHOULD include tag keys with corresponding non-null values for a given resource.
  • Tags MAY include tag keys with a null value for a given resource depending on the provider's tag finalization process.
  • Tag keys that do not support corresponding values, MUST have a corresponding true (boolean) value set.
  • Provider SHOULD publish tag finalization methods and semantics within their respective documentation.
  • Provider MUST NOT alter tag values unless applying true (boolean) to valueless tags.
• Provider-defined tags adhere to the following additional requirements:
  • Provider-defined tag keys MUST be prefixed with a predetermined, provider-specified tag key prefix that is unique to each corresponding provider-specified tag scheme.
  • Provider SHOULD publish all provider-specified tag key prefixes within their respective documentation.
• User-defined tags adhere to the following additional requirements:
  • Provider MUST prefix all but one user-defined tag scheme with a predetermined, provider-specified tag key prefix that is unique to each corresponding user-defined tag scheme when the provider has more than one user-defined tag scheme.
  • Provider MUST NOT prefix tag keys when the provider has only one user-defined tag scheme.
  • Provider MUST NOT allow reserved tag key prefixes to be used as prefixes for any user-defined tag keys within a prefixless user-defined tag scheme.