Scenario Overview

To facilitate the customer with a large number of instances to manage instances, Baidu AI Cloud launches the tag features. In this scenario, Users can classify and add the tag to the resources in accordance with various standards (such as purpose, owner or project), to facilitate the customer to classify and identify the resources quickly.

Action Instances

The following takes the site system in the figure above as an example to create a tag name, which includes 6 instances (such as authentication service, API gateway, purchase function, service function and product data server) and a disk mounted to purchase function.

The API Gateway is named as Gateway 001 by following the steps below (key name: Gateway, value: 001):

For the Purchase Funciton and Search Function are of the same type, two tag names are defined with the same key name and different values from the perspective of project management to facilitate the management.

The Purchase Function tag is named as Function 002 (key name: Function, value: 002).

For the Cloud Disk Service is the disk the Purchase Function mounts to, directly click the unified tag button of associated resources CDS and EIP to name it as Function 002 automatically.

The Search Function tag is named as Function 001 (key name: Function, value: 001).

The Authentication Service tag is named as Authentication 001 (key name: Authentication, value: 001).

The Product Database tag is named as Database 001 (key name: Database, value: 001).

The system with the tag name is shown in the figure below, and they are the instance tag names in the dark text box.