Tags let you categorize and manage ApsaraDB RDS instances at scale. Each tag is a key-value pair — group instances by environment, team, project, or any other dimension that fits your workflow.
Use cases
Cost tracking: Group instances by team or project to attribute infrastructure costs.
Automation: Trigger scripts or maintenance workflows by filtering instances with specific tags.
Environment separation: Distinguish production, staging, and development instances without relying on naming conventions alone.
Limitations
Each RDS instance supports up to 20 tags. Tag keys must be unique per instance — if you add a tag with a key that already exists, the new tag overwrites the existing one.
Batch tagging supports up to 50 instances at a time.
Tags are scoped to a region. Instances in different regions do not share the same tag namespace.
After you remove a tag from an instance, ApsaraDB RDS checks whether the tag is attached to any other instance. If not, the tag is deleted automatically.
Add a tag to a single 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 Tags column of the target instance, click the
icon, then click Edit.In the Configure Tags dialog box, set 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.
If Edit Tag is not visible, scroll to the bottom of the instance list.
In the Configure Tags dialog box, set the Tag Key and Tag Value, then click OK.
API reference
To tag instances programmatically, use the TagResources operation.