- Navigation GuideYou are on a Command (operation) page with structural examples. Use the navigation breadcrumb if you would like to return to the Client landing page.
UntagResourceCommand
Removes the association of tags from an Amazon DynamoDB resource. You can call UntagResource
up to five times per second, per account.
-
UntagResource
is an asynchronous operation. If you issue a ListTagsOfResource request immediately after anUntagResource
request, DynamoDB might return your previous tag set, if there was one, or an empty tag set. This is becauseListTagsOfResource
uses an eventually consistent query, and the metadata for your tags or table might not be available at that moment. Wait for a few seconds, and then try theListTagsOfResource
request again. -
The application or removal of tags using
TagResource
andUntagResource
APIs is eventually consistent.ListTagsOfResource
API will only reflect the changes after a few seconds.
For an overview on tagging DynamoDB resources, see Tagging for DynamoDB in the Amazon DynamoDB Developer Guide.
Example Syntax
Use a bare-bones client and the command you need to make an API call.
import { DynamoDBClient, UntagResourceCommand } from "@aws-sdk/client-dynamodb"; // ES Modules import
// const { DynamoDBClient, UntagResourceCommand } = require("@aws-sdk/client-dynamodb"); // CommonJS import
const client = new DynamoDBClient(config);
const input = { // UntagResourceInput
ResourceArn: "STRING_VALUE", // required
TagKeys: [ // TagKeyList // required
"STRING_VALUE",
],
};
const command = new UntagResourceCommand(input);
const response = await client.send(command);
// {};
UntagResourceCommand Input
Parameter | Type | Description |
---|
Parameter | Type | Description |
---|---|---|
ResourceArn Required | string | undefined | The DynamoDB resource that the tags will be removed from. This value is an Amazon Resource Name (ARN). |
TagKeys Required | string[] | undefined | A list of tag keys. Existing tags of the resource whose keys are members of this list will be removed from the DynamoDB resource. |
UntagResourceCommand Output
Parameter | Type | Description |
---|
Parameter | Type | Description |
---|---|---|
$metadata Required | ResponseMetadata | Metadata pertaining to this request. |
Throws
Name | Fault | Details |
---|
Name | Fault | Details |
---|---|---|
InternalServerError | server | An error occurred on the server side. |
InvalidEndpointException | client | |
LimitExceededException | client | There is no limit to the number of daily on-demand backups that can be taken. For most purposes, up to 500 simultaneous table operations are allowed per account. These operations include When you are creating a table with one or more secondary indexes, you can have up to 250 such requests running at a time. However, if the table or index specifications are complex, then DynamoDB might temporarily reduce the number of concurrent operations. When importing into DynamoDB, up to 50 simultaneous import table operations are allowed per account. There is a soft account quota of 2,500 tables. GetRecords was called with a value of more than 1000 for the limit request parameter. More than 2 processes are reading from the same streams shard at the same time. Exceeding this limit may result in request throttling. |
ResourceInUseException | client | The operation conflicts with the resource's availability. For example:
When appropriate, wait for the ongoing update to complete and attempt the request again. |
ResourceNotFoundException | client | The operation tried to access a nonexistent table or index. The resource might not be specified correctly, or its status might not be |
DynamoDBServiceException | Base exception class for all service exceptions from DynamoDB service. |