Docs

Elastic Compute Service

Tags

Tag design principles

Tags are essential grouping tools for personnel, finance, and resource management. This topic mainly describes the design principles of tags and provides common examples. This helps you quickly and accurately use the tagging feature to achieve horizontal resource management.

Tag design principles

When associating tags with resources, refer to the following guidelines to create tags.

Comprehensive plan

This principle means that when planning resources, you need to plan tags comprehensively (with priority given to the design of tag keys). Then, associate the planned tag keys and their corresponding tag values with resources. This helps you group and retrieve resources by tag dimensions later.

Mutual exclusion

This principle means that using two or more tag keys for the same attribute should be avoided. For example, if you use key=owner to mark a resource owner, do not use other tag keys with the same meaning (such as own, belonger).

Simplified design

This principle means the simplified use of tag keys. When you plan tags, use tag keys with fixed dimensions. This reduces errors during operations due to an excessive number of tag keys.

Limited value

This principle mainly applies to the design of tag values. Remove redundant tag values from resources and retain only core ones. This helps to simplify processes, such as resource management, access control, and automatic O&M.

Consider future changes

Changing tags may cause changes in tag-based processes, such as resource management, access control, and automatic O&M. When you plan tags, consider the impact of adding or removing tag values on existing processes in future work to change tags more flexibly.

Tag design examples

The table below lists common tag naming examples by business dimension for your reference.

Business dimension	Tag key	Tag value
Organizational architecture	company department organization team group	Related names
Business architecture	product business module service	Related names
Project-related	project schedule risk subtask	Project-related values
Usage-related	purpose use	Usage-related values
Role architecture	role user	System administrator Network administrator O&M administrator R&D personnel Test personnel
Personnel type	sponsor creator owner member	Personnel type values
Business department (for cost allocation and business tracking)	costcenter businessunit biz financecontact	Department-related values
Finance owner	owner	Names, email addresses, and more
Financial order	order	Order category ID

Last updated: 2026.06.18 17:48:25