Resource tags

RunsOn supports tagging resources with custom tags. This is useful to identify resources in your AWS account, and help with cost allocation.

How it works

RunsOn will tag all infrastructure resources with the CostAllocationTag key (default key: stack, value: the CloudFormation stack name).

For ephemeral resources (ec2 instances, disks, etc), RunsOn will tag them with the cost allocation tag, and any custom tags that you have defined.

Types of custom tags

Custom tags can be set in different places:

1. custom tags defined in the RunnerCustomTags stack parameters.

2. custom tags defined in a specific custom property of your GitHub repository settings. The custom property must be named runs-on-custom-tags, and the value is a comma-separated list of tag keys and values, e.g. key1=value1,key2=value2.

3. custom tags defined for a runner specification in the runs-on.yml file.

If the same tag name is defined in multiple places, the precedence is as follows:

1. Stack-level tags
2. Custom property
3. runs-on.yml file

Note

RunsOn does not support adding custom tags to resources directly within the runs-on: attribute of your workflows, because labels have a limited size and have format constraints. It also would make for very long labels.