Tags are used to identify cloud resources. Tags allow you to categorize, search for, and aggregate cloud resources that have the same characteristics from different dimensions. This facilitates resource management.


You can use tags to perform the following operations:

  • Search for resources.

    Add tags to resources and search for resources by tag in the Resource Management console or by calling a tag-related API operation. For more information, see Use tags to query cloud resources.

  • Implement automated O&M.

    Add different tags to environments such as production and test environments, operating systems such as Windows and Linux, or mobile platforms such as iOS and Android. Then, create a template in Operation Orchestration Service (OOS) and execute the template to implement automated O&M for your resources. For more information, see Overview.

  • Control access to resources.

    You can use tags in Resource Access Management (RAM) to manage the access and operation permissions of RAM users on different resources. For more information, see Create a resource with a specific tag and Use tags to control access to ECS resources.


The Tag service provides the following benefits:
  • Convenience: A unified, visualized console is provided to manage the resources to which tags are added.
  • Flexibility: You can add, remove, modify, or query one or more tags in the console or by calling an API operation.
  • Visibility: You can use tags to manage separate bills for departments, products, and projects.


Term Description
key-value pair

A tag consists of a key-value pair.

custom tag A custom tag is created by a user. For more information, see Add a custom tag.
preset tag A preset tag is a tag that you create in advance and is added to the resources in all regions. You can create preset tags in the stage of tag planning and add them to specific cloud resources in the stage of tag implementation. The system provides some common built-in types for preset tags. This allows you to quickly plan tag systems. For more information, see Create a preset tag.
system tag A system tag is defined by the system. You can only query system tags. System tags present data relationships in a standard manner. In some specific cases, you can use system tags to assist in processing your business. For example, a cluster is associated with an Elastic Compute Service (ECS) instance, and the system automatically adds the system tag of the cluster ID to the ECS instance. This way, you can determine the attribution of the ECS instance based on the system tag. For more information, see View system tags and the resources to which the system tags are added.
tag editor A tag editor is a tool that is used to manage resource tags in a centralized manner. You can use a tag editor to search for resources that belong to different Alibaba Cloud services and reside in different regions. In addition, you can use a tag editor to add, modify, or remove tags for multiple resources at a time, and export resource lists.

Cloud services that support tags

A series of core Alibaba Cloud services support tags, such as ECS, ApsaraDB RDS, Object Storage Service (OSS), Virtual Private Cloud (VPC), Server Load Balancer (SLB), and Container Service for Kubernetes (ACK). Alibaba Cloud intends to add tag support for other services. For more information, see Alibaba Cloud services that support tags.


Item Limit
Maximum number of tags that can be added to a single resource 20
Whether tag information can be shared across regions

No. For example, in the China (Shanghai) region, you cannot view tags created in the China (Hangzhou) region.

Tag key A tag key must be 1 to 128 characters in length and cannot contain http:// or https://. It cannot start with aliyun or acs:.
Tag value A tag value must be 1 to 128 characters in length and cannot contain http:// or https://. It cannot start with aliyun or acs:.
Adding tags to resources

Each tag key on a resource can have only one tag value. If you create a tag that has the same key as an existing tag, the value of the existing tag is overwritten.

For example, the city:shanghai tag is added to a resource. If you add the city:newyork tag to the resource, the city:shanghai tag is automatically removed from the resource.