AWS IoT Events
Developer Guide

Tagging Your AWS IoT Events Resources

To help you manage and organize your detector models and inputs you can optionally assign your own metadata to each of these resources in the form of tags. This section describes tags and shows you how to create them.

Tag Basics

Tags enable you to categorize your AWS IoT Events resources in different ways, for example, by purpose, owner, or environment. This is useful when you have many resources of the same type. You can quickly identify a specific resource based on the tags you've assigned to it.

Each tag consists of a key and optional value, both of which you define. For example, you could define a set of tags for your inputs that helps you track the devices that send these inputs by their type. We recommend that you create a set of tag keys that meets your needs for each kind of resource. Using a consistent set of tag keys makes it easier for you to manage your resources.

You can search for and filter resources based on the tags you add or apply, use tags to categorize and track your costs, and also use tags to control access to your resources as described in Using Tags with IAM Policies.

For ease of use, the Tag Editor in the AWS Management Console provides a central, unified way to create and manage your tags. For more information, see Working with Tag Editor in Working with the AWS Management Console.

You can also work with tags using the AWS CLI and the AWS IoT Events API. You can associate tags with detector models and inputs when you create them by using the "Tags" field in the following commands:

You can add, modify, or delete tags for existing resources that support tagging by using the following commands:

You can edit tag keys and values, and you can remove tags from a resource at any time. You can set the value of a tag to an empty string, but you can't set the value of a tag to null. If you add a tag that has the same key as an existing tag on that resource, the new value overwrites the old value. If you delete a resource, any tags associated with the resource are also deleted.

Additional information is available in AWS Tagging Strategies.

Tag Restrictions and Limitations

The following basic restrictions apply to tags:

  • Maximum number of tags per resource – 50

  • Maximum key length – 127 Unicode characters in UTF-8

  • Maximum value length – 255 Unicode characters in UTF-8

  • Tag keys and values are case sensitive.

  • Do not use the "aws:" prefix in your tag names or values because it's reserved for AWS use. You can't edit or delete tag names or values with this prefix. Tags with this prefix don't count against your tags per resource limit.

  • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally, allowed characters are: letters, spaces, and numbers representable in UTF-8, and the following special characters: + - = . _ : / @.

Using Tags with IAM Policies

You can apply tag-based resource-level permissions in the IAM policies you use for AWS IoT Events API actions. This gives you better control over what resources a user can create, modify, or use.

You use the Condition element (also called the Condition block) with the following condition context keys and values in an IAM policy to control user access (permissions) based on a resource's tags:

  • Use aws:ResourceTag/<tag-key>: <tag-value> to allow or deny user actions on resources with specific tags.

  • Use aws:RequestTag/<tag-key>: <tag-value> to require that a specific tag be used (or not used) when making an API request to create or modify a resource that allows tags.

  • Use aws:TagKeys: [<tag-key>, ...] to require that a specific set of tag keys be used (or not used) when making an API request to create or modify a resource that allows tags.

Note

The condition context keys and values in an IAM policy apply only to those AWS IoT Events actions where an identifier for a resource capable of being tagged is a required parameter.

Controlling Access Using Tags in the AWS Identity and Access Management User Guide has additional information on using tags. The IAM JSON Policy Reference section of that guide has detailed syntax, descriptions, and examples of the elements, variables, and evaluation logic of JSON policies in IAM.

The following example policy applies two tag-based restrictions. An IAM user restricted by this policy:

  • Cannot give a resource the tag "env=prod" (in the example, see the line "aws:RequestTag/env" : "prod"

  • Cannot modify or access a resource that has an existing tag "env=prod" (in the example, see the line "aws:ResourceTag/env" : "prod").

{ "Version" : "2012-10-17", "Statement" : [ { "Effect" : "Deny", "Action" : "iotevents:*", "Resource" : "*", "Condition" : { "StringEquals" : { "aws:RequestTag/env" : "prod" } } }, { "Effect" : "Deny", "Action" : "iotevents:*", "Resource" : "*", "Condition" : { "StringEquals" : { "aws:ResourceTag/env" : "prod" } } }, { "Effect": "Allow", "Action": [ "iotevents:*" ], "Resource": "*" } ] }

You can also specify multiple tag values for a given tag key by enclosing them in a list, as follows.

"StringEquals" : { "aws:ResourceTag/env" : ["dev", "test"] }

Note

If you allow or deny users access to resources based on tags, you must consider explicitly denying users the ability to add those tags to or remove them from the same resources. Otherwise, it's possible for a user to circumvent your restrictions and gain access to a resource by modifying its tags.