Tag Policy allows organizations to encode their internal tagging policy and tagging structure into the application. 

Organizations have these documents internally that layout the structure of how developers/teams should tag their services and resources. Tag Policy is a way of encoding these rules into the Stax Spotlight app, and receiving regular feedback on where they are being broken.

How is this helpful?

Consider the case of a company that wants its various cost centers to have visibility over relevant costs. To achieve this, the company needs to ensure every resource taggable has a tag key of cost-center and a value of one of the org’s cost centers. 

With Tag Policy, an admin can specify that every taggable resource should have a tag key of cost-center and a value of one of the organization’s cost centers. 

Stax Spotlight will then report on new resources that don’t have a cost-center tag, so the issue can be fixed early – within a day – rather than waiting until the next reconciliation.

Who can use it?

This feature is restricted to Stax Spotlight admins. 

How do I use it?

A Tag Policy consists of one or more tag constraints. Visit the Cost->Tag Policy section of Stax Spotlight to enter tag constraints.

Tag constraints can be set to accept either any value for a given tag key or a predefined range of tag values. The decision between these two approaches will come down to the purpose of the tagging and how it relates to your business.

For example, an organization could require every AWS resource to have an ‘owner’ tag. Managing a predefined range of tag values for ‘owners’ would be difficult, since there could be thousands of tag values – no-one wants to regularly negotiate such a long list. 

In that case, we would recommend the customer use a tag constraint that can match any tag value.

But then another organization could require every resource to have an ‘environment’ tag. Since this organization will only ever use their ‘production’, ‘nonproduction’, and ‘quality assurance’ environments, a tag constraint that allows a selection between these tag values would be a more logical choice.

Why does “tag policy” sound familiar?

At the 2019 re:Invent conference AWS launched their own version of Tag Policy (which they called Tag Policies).

A forthcoming update to our Tag Policy feature will allow Stax Spotlight to ingest data from the AWS equivalent, bringing over existing tag policies to the platform and allowing new customers to skip an entire setup task during onboarding. 

We’re always keen to see our customers improving their compliance and overall AWS hygiene, so until that update arrives, feel free to use whichever Tag Policy feature you like to help make tagging easier. Soon, all the data will make its way to Stax Spotlight anyway. Though of course, we’re a pretty big fan of our solution ;)

If you still have questions about the feature, please click below to start a conversation, or email support@stax.io.

Did this answer your question?