Tagging Amazon Glacier Resources
You use the Amazon Glacier console, AWS Command Line Interface (AWS CLI), or Amazon Glacier API to complete the following tasks:
Adding tags to a vault
Listing the tags for a vault
Removing tags from a vault
For information about how to add, list, and remove tags, see Tagging Your Amazon Glacier Vaults.
You can use tags to categorize your vaults. For example, you can categorize vaults by purpose, owner, or environment. Because you define the key and value for each tag, you can create a custom set of categories to meet your specific needs. For example, you might define a set of tags that helps you track vaults by owner and purpose for the vault. Following are a few examples of tags:
Purpose: Video archives
Basic tag restrictions are as follows:
The maximum number of tags for a resource (vault) is 50.
Tag keys and values are case-sensitive.
Tag key restrictions are as follows:
Within a set of tags for a vault, each tag key must be unique. If you add a tag with a key that's already in use, your new tag overwrites the existing key-value pair.
Tag keys cannot start with
aws:because this prefix is reserved for use by AWS. AWS can create tags that begin with this prefix on your behalf, but you can't edit or delete them.
Tag keys must be from 1 to 128 Unicode characters in length.
Tag keys must consist of the following characters: Unicode letters, digits, white space, and the following special characters:
_ . / = + - @.
Tag value restrictions are as follows:
Tag values must be from 0 to 255 Unicode characters in length.
Tag values can be blank. Otherwise, they must consist of the following characters: Unicode letters, digits, white space, and any of the following special characters:
_ . / = + - @.
Tracking Costs Using Tagging
You can use tags to categorize and track your AWS costs. When you apply tags to any AWS resources, including vaults, your AWS cost allocation report includes usage and costs aggregated by tags. You can apply tags that represent business categories (such as cost centers, application names, and owners) to organize your costs across multiple services. For more information, see Use Cost Allocation Tags for Custom Billing Reports in the AWS Billing and Cost Management User Guide.
Managing Access Control with Tagging
You can use tags as a condition in an access policy statement. For example, you can set up
a legal hold tag and include it as a condition in a data retention policy that states that
“archive deletion from everyone will be denied if the legal hold tag value is set to
You can deploy the data retention policy and set the legal hold tag to
False under normal
conditions. If your data must be put on hold to assist an investigation, you can easily turn
on the legal hold by setting the tag value to
True and removing the hold in a similar way
later on. For an example, see Example 2: Deny
Deletion Permissions Based on a Tag.