Automated tagging policy management

Key role(s)


Implement an automated tagging strategy


Ensure comprehensive tagging with reduced effort

As with chargeback, there are, again, choices to be made in order to ensure that all components are correctly tagged without requiring superhuman effort. Among others, we will think of the following points:

Missing tag detection

Define the default values (if possible according to the component in question, the associated components, the associated application...) as well as the mandatory tags and then set up an alert to detect missing tags.

Destruction of resources

Define a process for the destruction of non-conforming components.

Default BU

Define a process to be attached or not to a transversal BU when it is not specified (for example so that it appears clearly in the KPIs and knowing that this value should tend towards 0).

Proprietary applications and BU

Create a mapping table of applications with their owners and their original BU, to facilitate the automation of tagging (for example, you only have to fill in the application ID and the rest is completed automatically).

Typology and application role

Similarly create a table of service typologies and the application role played (for example, the creation of an RDS database will be automatically tagged "database").

Mail order companies and environments

Create a correspondence table of mail order and environment types knowing that they are normally distinct (e.g. a component created on the development mail order will be automatically tagged "Dev").


For all this you can code your own scripts or reuse already written scripts (to come in this section) but it is of course possible to use tools from suppliers or CMPs on the market.

Example of open source scripts for tagging in AWS : Graffiti Monkey.

See previous card


ID 2G3

See next card

Rationalizing Shared Services

ID 2B2