Product Introduction

Overview

Features

Scenarios

Use Limits

Resource Types Supporting Tag APIs

Purchase Guide

Getting Started

Creating Tags and Binding Resources

Querying Resources by Tag

Operation Guide

Creating Tags

Tagging Resources

Unbinding Tags

Unbinding or Modifying Tags in Batches

Deleting Tags

Viewing Tagged Resources

Querying and Editing Resource Tags

Setting Tag Quotas

Exporting Resource Tags

Query Tag Modification Record

CreatedBy

Tag Policy

Exporting a Tag List

API Documentation

History

Introduction

API Category

Making API Requests

Write APIs

Read APIs

Project APIs

Data Types

Error Codes

FAQs

Glossary

Overview

PDF

Mode fokus

Ukuran font

Terakhir diperbarui: 2025-01-02 14:54:12

Tag policies are a type of policy that can help you standardize tags across resources. In a tag policy, you can specify tagging rules applicable to resources when they are tagged. Compliant tags can help you improve management efficiency in scenarios such as cost allocation by tag, tag authentication, and automated Ops.
The tag policies support two modes: single-account mode and multi-account mode. You can use tag policies to standardize tag usage based on your business needs at different stages. For multi-account management based on the corporate account system, see Tag Policy Overview.
Note：
The tag policy is currently in public beta testing across the entire network. If you have any suggestions while using this service, we warmly welcome your feedback at any time. You may submit a ticket.
Product Advantages
The application scenarios and value of tag policies are primarily manifested in the following aspects:
Organizing Resources: By assigning tags to sub-users within tag policies, they can manage and organize resources more effortlessly, enhancing the accuracy of tags. For instance, if a tag policy stipulates that sub-users must attach tags such as "Project: project1" and "Department: Technical Division 1", any incorrect tag assignments by sub-users can be rectified by the policy, thereby aligning more closely with the internal tagging standards of the organization.
Cost Allocation: Tag policies facilitate users in tracking and analyzing the cost of resource utilization more effectively. By assisting sub-users in attaching and correcting precise tags, and then by enabling cost allocation tags, you can view the expenses of each resource in the billing section of the cost center. This allows for a better understanding of resource consumption across various projects or departments.
Security and Compliance: Tag policies enhance access control and compliance management of resources. For example, you might use tag-based authorization to restrict user access only to resources with specific tags. However, if sub-users misassign tags, the scope of authorization changes. Tag policies assist in rectifying such issues, thereby ensuring the security of resources.
Automation: Tag policies offer the option of automatic correction, which can be used in conjunction with CAM - During tag-based authentication, only tag key matching is supported, to achieve automated resource management. For example, in access management policies, sub-users are required to attach certain types of tags when performing specific actions. Tag policies can then automatically correct any misassigned tags during modification by sub-users. An option for automatic assignment is available, for instance, if creating a resource requires attaching four tags, this can simplify the cumbersome process of entering tags for sub-users.
Use Limits
Type
Default Upper Limit
Handling Rule in Case of Exceeding the Upper Limit
Is Increase Supported
Method of Increase
The number of tag policies under a single root account
A maximum value of 100
Saving a tag policy is not allowed when it is created.
Yes
﻿Submitting a ticket﻿
The number of tag policies that can be bound to a single root account or sub-account user
A maximum value of 10
Binding a tag policy to the user is not allowed.
No
-
The number of tag keys in an effective policy
A maximum value of 50
Excess tag keys will not be merged when an effective policy is generated.
No
-
The maximum number of characters for a single tag policy
A maximum value of 4,096 characters
Saving a tag policy is not allowed when the number of its characters exceeds the limit.
Yes
﻿Submitting a ticket﻿
Supporting a separate increase for root accounts and sub-accounts
Supported Resource Types
For products and resource types supported by tag policies, see Resource Types Supporting Tag APIs.
Supported Scenarios
Feature Name
Effect Before Setting
Effect After Setting
Flexible Scope of Effectiveness for Tag Policies
There is no policy, and users bind tags on their own.
When linked to a root account, it can take effect on that account
When bound to a specific sub-user, it can exclusively affect that sub-user.
You can bind certain sub-users in batches as needed.
Automatic Repair Scenarios
User settings are wrong and hard to detect, and can only be manually modified after self-inspection.
For existing resources that are not tagged, if a sub-user adds a tag that is inconsistent with the constraints within the tag policy, automatic correction is supported
Automatic Assignment Scenarios
Users need to input each tag to be searched for and selected and remember which key values need to be bound.
When creating or editing resource tags, it can automatically display tag keys or tag values for sub-users by default, thereby reducing the steps sub-users need to take or preventing omissions.
Mandatory Interception Scenarios
User settings are wrong and not detected, and need to be corrected after being discovered.
When tags are edited for existing resources, if the key value does not comply with constraints within the tag policy, the binding will be intercepted. For example, if a sub-user is required to bind  Product: Product A , but the sub-user edits it as  Product: Product B , the binding will be intercepted.
Tag Policy Key Value Limits
Users need to search among all key values.
After this feature is enabled, effective policy keys will be displayed first when tag keys are set for resources. When tag values are set, only the value agreed for the tag key in the effective policy can be selected, and all tag values cannot be selected. This includes creating new resources or editing existing resources.
﻿

Bantuan dan Dukungan

Apakah halaman ini membantu?

Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.

masukan

Type	Default Upper Limit	Handling Rule in Case of Exceeding the Upper Limit	Is Increase Supported	Method of Increase
The number of tag policies under a single root account	A maximum value of 100	Saving a tag policy is not allowed when it is created.	Yes	Submitting a ticket
The number of tag policies that can be bound to a single root account or sub-account user	A maximum value of 10	Binding a tag policy to the user is not allowed.	No	-
The number of tag keys in an effective policy	A maximum value of 50	Excess tag keys will not be merged when an effective policy is generated.	No	-
The maximum number of characters for a single tag policy	A maximum value of 4,096 characters	Saving a tag policy is not allowed when the number of its characters exceeds the limit.	Yes	Submitting a ticket Supporting a separate increase for root accounts and sub-accounts

Feature Name	Effect Before Setting	Effect After Setting
Flexible Scope of Effectiveness for Tag Policies	There is no policy, and users bind tags on their own.	When linked to a root account, it can take effect on that account When bound to a specific sub-user, it can exclusively affect that sub-user. You can bind certain sub-users in batches as needed.
Automatic Repair Scenarios	User settings are wrong and hard to detect, and can only be manually modified after self-inspection.	For existing resources that are not tagged, if a sub-user adds a tag that is inconsistent with the constraints within the tag policy, automatic correction is supported
Automatic Assignment Scenarios	Users need to input each tag to be searched for and selected and remember which key values need to be bound.	When creating or editing resource tags, it can automatically display tag keys or tag values for sub-users by default, thereby reducing the steps sub-users need to take or preventing omissions.
Mandatory Interception Scenarios	User settings are wrong and not detected, and need to be corrected after being discovered.	When tags are edited for existing resources, if the key value does not comply with constraints within the tag policy, the binding will be intercepted. For example, if a sub-user is required to bind `Product: Product A` , but the sub-user edits it as `Product: Product B` , the binding will be intercepted.
Tag Policy Key Value Limits	Users need to search among all key values.	After this feature is enabled, effective policy keys will be displayed first when tag keys are set for resources. When tag values are set, only the value agreed for the tag key in the effective policy can be selected, and all tag values cannot be selected. This includes creating new resources or editing existing resources.

tencent cloud

Tag

Overview

Product Advantages

Use Limits

Supported Resource Types

Supported Scenarios

Bantuan dan Dukungan