Docs

RDS for PostgreSQL

Managing tags

Overview

Tags are used for identifying and categorizing cloud resources. RDS for PostgreSQL supports adding tags to instances for instance classification, retrieval, and aggregation. This topic introduces the functional concepts, application scenarios, and precautions of tags.

Function overview

As the number of cloud resources continues to grow, management complexity increases. Volcano Engine provides tag management features for custom identification and categorized management of cloud service resources from various dimensions. For example, you can categorize cloud resources by different business types, uses, or users through tags. After binding tags to resources, you can quickly query and filter cloud resources of a specified category by tags. RDS for PostgreSQL supports adding tags to instances, enabling instance-level tag management. A tag is a key-value pair consisting of one tag key and one tag value. You can add multiple tags of different categories to each PostgreSQL instance, for example, module:http, city:guangzhou, and so on. Each tag can also be bound to multiple cloud resources, such as setting the same tag owner:zhangsan for two PostgreSQL instances.

Application scenarios

Tag management is recommended for the following scenarios:

Cloud resource classification Managing resources only by instance name is difficult when the number of cloud resources is large. You can classify instances based on business scenarios and assign the same tag to instances within the same business scenario. Once set, you can quickly filter instances by specifying tag keys and tag values.

Cloud resource access control IAM access control service supports authorization and authentication at the tag level. By authorizing different tags, you can grant different IAM users access and operation permissions for different categories of cloud resources.

Billing and cost allocation If your business requires cost allocation by organization or department, you can classify cloud resources using tags. Assign the same tag to resources under the same organization or department, and allocate cloud resource costs to the corresponding entity during periodic billing to achieve cost sharing management.

Precautions

You can add multiple tags of different categories to each instance, but an instance can only have one tag value per tag key. For example, when adding a tag module to instance A, if the tag module:http already exists, adding the module:tcp tag will overwrite the module:http tag.

Tag information is not shared across different regions. For example, tags created in Huabei 2 (Beijing) are not visible in Huadong 2 (Shanghai).

The total number of tags is unlimited, but each instance can bind up to 50 tags. For detailed tag setting rules, refer to Tag setting rules.

Example

For example, a company purchased 5 RDS for PostgreSQL instances on Volcengine, used for payment, shopping cart, and points business modules, serving Users in Beijing, Guangzhou, and Shanghai, maintained by Zhang San, Li Ming, and Han Meimei. To facilitate instance management, you can classify instances by binding tags. In this scenario, the following tags can be designed.

Tag key	Tag value
system	pay、shoppingcart、integral
city	beijing、guangzhou、shanghai
owner	zhangsan、liming、hanmeimei

In this scenario, you can set corresponding tags for each instance.

Instance name	Instance tag
PostgreSQL instance A	system：pay city：beijing owner：zhangsan
PostgreSQL instance B	system：pay city：guangzhou owner：liming
PostgreSQL instance C	system：shopping cartcity：beijing owner：liming
PostgreSQL instance D	system：shoppingcart city：shanghai owner：hanmeimei
PostgreSQL instance E	system：integral city：beijing owner：hanmeimei