Try it now and let us know what you think. Switch to the new look >>
You can return to the original look by selecting English in the language selector above.
Amazon SQS Cost Allocation Tags
To organize and identify your Amazon SQS queues for cost allocation, you can add metadata
tags that identify a queue's purpose, owner, or environment.
—this is especially useful when you have many queues. For information about
managing Amazon SQS queue tags using the AWS Management Console or the AWS SDK for
Java (and the TagQueue, UntagQueue, and
ListQueueTags actions), see the Adding, Updating, and Removing Tags from an Amazon SQS Queue tutorial.
You can use cost allocation tags to organize your AWS bill to reflect your own cost structure. To do this, sign up to get your AWS account bill to include tag keys and values. For more information, see Setting Up a Monthly Cost Allocation Report in the AWS Billing and Cost Management User Guide.
Each tag consists of a key-value pair that you define. For example, you can easily identify your production and testing queues if you tag your queues as follows:
| Queue | Key | Value |
|---|---|---|
MyQueueA |
QueueType |
Production |
MyQueueB |
QueueType |
Testing |
Note
When you use queue tags, keep the following guidelines in mind:
-
We don't recommend adding more than 50 tags to a queue.
-
Tags don't have any semantic meaning. Amazon SQS interprets tags as character strings.
-
Tags are case-sensitive.
-
A new tag with a key identical to that of an existing tag overwrites the existing tag.
-
Tagging actions are limited to 5 TPS per AWS account. If your application requires a higher throughput, file a support request.
For a full list of tag restrictions, see Limits Related to Queues.
You can't add tags to a new queue when you create it using the AWS Management Console (you can add tags after the queue is created). However, you can add, update, or remove queue tags at any time using the Amazon SQS actions.
