Tagging Amazon OpenSearch Service domains
Tags let you assign arbitrary information to an Amazon OpenSearch Service domain so you can categorize and filter on that information. A tag is a key-value pair that you define and associate with an OpenSearch Service domain. You can use these tags to track costs by grouping expenses for similarly tagged resources. AWS doesn't apply any semantic meaning to your tags. Tags are interpreted strictly as character strings. All tags have the following elements:
| Tag Element | Description | Required |
|---|---|---|
| Tag key |
The tag key is the name of the tag. Key must be unique to the OpenSearch Service domain to which they're attached. For a list of basic restrictions on tag keys and values, see User-Defined Tag Restrictions. |
Yes |
| Tag value |
The tag value is the string value of the tag. Tag values can be
|
No |
Each OpenSearch Service domain has a tag set, which contains all the tags assigned to that OpenSearch Service domain. AWS doesn't automatically assign any tags to OpenSearch Service domains. A tag set can contain between 0 and 50 tags. If you add a tag to a domain with the same key as an existing tag, the new value overwrites the old value.
Tagging examples
You can use a key to define a category, and the value could be an item in that category.
For example, you could define a tag key of project and a tag value of
Salix, indicating that the OpenSearch Service domain is assigned to the Salix
project. You could also use tags to designate OpenSearch Service domains as being used for test or
production by using a key such as environment=test or
environment=production. Try to use a consistent set of tag keys to make
it easier to track metadata that is associated with OpenSearch Service domains.
You also can use tags to organize your AWS bill to reflect your own cost structure. To do this, sign up to get your AWS account bill with tag key values included. Then, organize your billing information according to resources with the same tag key values to see the cost of combined resources. For example, you can tag several OpenSearch Service domains with key-value pairs, and then organize your billing information to see the total cost for each domain across several services. For more information, see Using Cost Allocation Tags in the AWS Billing and Cost Management documentation.
Note
Tags are cached for authorization purposes. Because of this, additions and updates to tags on OpenSearch Service domains might take several minutes before they're available.
