Docs

Elastic Compute Service

Tags

UntagResources - Deletes tags (new version)

Call the UntagResources operation to delete tags from one or multiple resources.

Usage notes

Warning

This page describes the tag-targeted operation of the new version, which is strongly recommended for new users. Learn more.

Tag-targeted operations of the earlier version may no longer be maintained in the future. If you still need to use them, refer to:

CreateTags - Creates tags (earlier version)

DeleteTags - Deletes tags (earlier version)

DescribeTags - Queries tagged resources (earlier version)

Usage notes

This operation supports deleting a maximum of 20 tags per query.

Repeatedly disassociating a tag overrides the original result and updates the tag value.

Debugging

API Explorer

You can initiate calls online through API Explorer without paying attention to the signature generation process and quickly obtain the call results.

Go to debug

Request parameters

Only the request parameters specific to this operation and some common parameters are listed below. For more information, refer to Common parameters.

Action string required Sample value: UntagResources

The action that you want to perform. Value: UntagResources.

Version string required Sample value: 2020-04-01

The version of the API. Valid value: 2020-04-01.

ResourceIds.N string[] required Sample value: ResourceIds.1=i-l8u0p77yseabkpak****&ResourceIds.2=i-l8u0p7xyseabkbak****

The resource ID.

Argument - N: indicates the serial number of the resource. Valid range: 1-50.

Separate resources with &.

ResourceType string required Sample value: instance

The resource type. Valid values:

instance: instance

image: image

reservedinstance: Reserved Instances (RI)

scheduledinstance: Elastic Scheduled Instances (ESI)

key pair: key pair

TagKeys.N string[] required Sample value: TagKeys.1=k1

The key of the custom tag to be deleted from the resource.

Argument - N: specifies the serial number of the tag key. Valid range: 1–20.

Separate multiple tag keys with &.

Naming rules:

Cannot start with volc: or sys: in any case form.

Tags that start with volc: or sys: are reserved for the system. You cannot create tags starting with them.

It can contain only language characters, digits, spaces, and English symbols of " _", ".", ":", "/", "=", "+", "-", and "@".

It must be 1 to 128 characters in length.

Response parameters

Only the response parameters specific to this operation are listed below. For more information, refer to the response structure.

RequestId string Sample value: 202308101209161A3FE8E1FC09E29F****

The request ID.

Sample request

Sample response

Error codes

The table below lists the business-related error codes of the operation. For more information, refer to Common error codes.

Status code	Error code	Error message	Description
400	IdempotentParameterMismatch	The request uses the same client token as a previous, but non-identical request. Do not reuse a client token with different requests, unless the requests are identical.	The idempotent parameters are inconsistent.
400	InvalidArgument	The specified argument is invalid.	The specified parameter is invalid.
400	InvalidClientToken.Malformed	The specified ClientToken is malformed.	The specified ClientToken is invalid.
400	InvalidTagKey.Malformed	The specified TagKey is malformed.	The specified tag key is invalid.
400	LimitExceeded.MaximumResourceIds	You've reached the limit on the number of ResourceIds that you can set.	The specified number of resource IDs exceeds the limit.
400	LimitExceeded.MaximumTagKeys	You've reached the limit on the number of TagKeys that you can set.	The specified tag key is out of range.
404	InvalidResourceId.NotFound	The specified ResourceId does not exist.	The specified resource does not exist.
404	InvalidResourceType.NotFound	The specified ResourceType does not exist.	The specified resource type does not exist.
404	InvalidTagKey.NotFound	The specified TagKey does not exist.	The specified tag key does not exist.
412	IdempotentProcessing	The request uses the same client token as a previous one that is still in process.	The previous idempotent request is still being processed. Please try again later.
500	InternalError	An internal error has occurred.	An internal error occurred. Try again. If multiple attempts fail, submit a ticket.

Last updated: 2026.04.17 10:57:33