When you manage multiple RDS instances across environments, projects, or teams, locating and grouping specific instances becomes difficult without a consistent labeling strategy. Tags let you attach key-value metadata to instances — for example, environment=prod or project=analytics — so you can filter and organize large fleets.
With tags, you can:
Filter and locate specific instances quickly in the console
Group instances by environment, project, or team
Limitations
| Constraint | Details |
| Max tags per instance | 20 |
| Tag key uniqueness | Each tag key must be unique per instance. Adding a tag with an existing key overwrites the earlier tag. |
| Batch instance limit | Up to 50 RDS instances per batch operation |
| Tag namespace scope | Region-specific. Instances in different regions do not share tags. |
| Tag deletion behavior | When you remove a tag from an instance, ApsaraDB RDS checks whether any other instances still use that tag. If none do, the tag is deleted. |
Add a tag to an instance
Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where your instance resides.
In the instance list, click the
icon in the Tags column of the target instance. In the window that appears, click Edit. If you have already added a tag to the instance, you can also click Edit to edit the existing tag.In the Configure Tags dialog box, enter the Tag Key and Tag Value, then click OK.
Add tags to multiple instances at a time
Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where your instances reside.
Select the instances you want to tag, then click Edit Tag below the instance list.
Note If Edit Tag is not visible, scroll to the bottom of the instance list.
In the Configure Tags dialog box, enter the Tag Key and Tag Value, then click OK.
API reference
| Operation | Description |
| TagResources | Add tags to one or more ApsaraDB RDS instances |