Our organization uses tag keys of the form org:billto:costcenter for common cost tagging across all AWS resources, which we adopted under guidance from the AWS Cost and Usage Report team. The AWS::CloudFormation::StackSet resource schema forbids tags of this form since they contain colons. We cannot easily fold together alternative tags declared as org/billto/costcenter, for example, using the AWS-provided cost aggregation functions.
I understand reserving tag namespaces like aws:, but is there an obstacle to supporting such a common AWS-endorsed tagging scheme?
Our organization uses tag keys of the form
org:billto:costcenter
for common cost tagging across all AWS resources, which we adopted under guidance from the AWS Cost and Usage Report team. TheAWS::CloudFormation::StackSet
resource schema forbids tags of this form since they contain colons. We cannot easily fold together alternative tags declared asorg/billto/costcenter
, for example, using the AWS-provided cost aggregation functions.I understand reserving tag namespaces like
aws:
, but is there an obstacle to supporting such a common AWS-endorsed tagging scheme?