Implementing a Tag Strategy
Last updated
Last updated
To implement a Tag strategy, you must implement a tagging strategy in your cloud environment.
Many customers will already have a tagging strategy in place, i.e., OUs and accounts (AWS) or folders and projects (GCP) are tagged with key/value pairs that describe their environment and/or provide business context. Those tags can be added to the Heeler Environments page to dynamically assign Environment Tags to their resources.
In AWS, these tags are defined in the payor account under the Organizations service. These are the tags that will be used to assign Environment Tags to member accounts and resources. E.g.,
Note, there is the flexibility to have multiple key/value pairs map to the same Environment Tag. This mapping is helpful to support inconsistent tagging strategies or tagging strategies that vary by business unit or location.
For example, if a customer has tags that were inherited from different business units that follow a pattern like Environment: Acme Prod and Env: Hooli Production, etc., it is possible to map them both in Heeler to Environment: Production. You do so by
Select settings
Select Environments
Select "Tags" under the Environment you would like to customize, e.g., Production
Enter in the key/value pair you would like to use, e.g., Protection Setting: Crown Jewels, and select Add Tag
Verify that your tag has been entered and select Done
Repeat with as many key/value pairs as required.
