How can we help?
Table of Contents
< All Topics

Configure Mandatory Tags

Tags enable you to categorize your cloud resources differently, for example, by purpose, owner, or environment. This is useful when you have many resources of the same type – you can quickly identify a specific resource based on your assigned tags.

A tag is a label that you assign to a cloud resource. Each tag consists of a key and an optional value, both of which you define.

The following diagram illustrates how tagging works. In this example, you’ve assigned two tags to each of your instances—one tag with the key Owner and another with the key Stack. Each tag also has an associated value.

We recommend you devise a set of tag keys that meets your needs for each resource type. Using a consistent set of tag keys makes it easier for you to manage your resources. You can search and filter the resources based on the tags you add. For more information about how to implement an effective resource tagging strategy, see the AWS whitepaper Tagging Best Practices

All assets should be tagged with mandatory tags. Assets without mandatory tags will be marked as non-compliant.


Steps to configure mandatory tags:

To configure mandatory tags follow the below steps.

Step 1:

Connect to Paladin Cloud’s MySQL DB. You can get the DB credentials from your cloud console. Let’s see how we can find them in the AWS console.

  1. Go to the AWS console.
  2. Navigate to RDS.
  3. Under RDS, go to Databases.
  4. There, under Connectivity & security tab, you’ll find –
      Hostname as Endpoint and
      Port as Port

Step 2:

You can find an entry in the pac_config_properties with the key "tagging.mandatoryTags". This will hold the mandatory tags.
To confirm, query this row from mysql using:

SELECT * FROM pacmandata.pac_config_properties where cfKey = 'tagging.mandatoryTags';

Step 3:

Update this row with custom tags. Below is the update query:

update pacmandata.pac_config_properties set value = '<Your_Tags_Here>'  where cfKey = 'tagging.mandatoryTags' and application = 'application' and profile ='prd' and label='latest';

Step 4:

Wait for the next run for policies to update the violations.