A tag policy is an AWS Organizations policy that sets the rules for how tags are written across your accounts: which tag keys exist, how they are capitalised, and which values are allowed. It is how a company with several AWS accounts keeps CostCentre from also appearing as costcentre and cost-center.

What a tag policy can and can't do

It canIt can't
Define the exact spelling and capitalisation of a tag keyForce a resource to have a tag at all: untagged resources "aren't evaluated"
Limit a key to a list of allowed valuesJudge tags the policy doesn't define
Report non-compliant tags through Resource GroupsClean up existing bad tags on its own
When enforced, stop non-compliant tagging requests on specified resource typesEnforce on every resource type: enforcement covers only the resource types AWS lists as supported, so check that list for yours

To require that a tag exists, teams pair tag policies with other controls: tags set by default in infrastructure-as-code templates, service control policies that refuse certain actions without a tag, or AWS Config rules that flag untagged resources.

How to start safely

AWS's own advice is to begin with a simple policy on a single account, check its effect in the compliance report, and only then attach it to an organisational unit or switch on enforcement. Enforcing too early can break deployments whose existing tags don't match.

Tag policies matter because cost allocation tags are only as good as their consistency: one misspelt key splits a team's spend into two lines. They usually come in as part of a landing zone set-up. For the wider approach, see Tagging Strategy 101, and for help putting cost ownership in place, a Yemberzal Cost Optimisation Audit.