End of support notice: On May 20, 2026, Amazon will end support for Amazon IoT Events. After May 20, 2026, you will no longer be able to access the Amazon IoT Events console or Amazon IoT Events resources. For more information, see [Amazon IoT Events end of support](https://docs.amazonaws.cn/iotevents/latest/developerguide/iotevents-end-of-support.html).
# Identity and access management for Amazon IoT Events
Amazon Identity and Access Management (IAM) is an Amazon service that helps an administrator securely control access to Amazon resources. IAM administrators control who can be *authenticated* (signed in) and *authorized* (have permissions) to use Amazon IoT Events resources. IAM is an Amazon service that you can use with no additional charge.
**Topics**
+ [Audience](#security_iam_audience)
+ [Authenticating with identities](security_iam_authentication.md)
+ [Managing access using policies](security_iam_access-manage.md)
+ [More about identity and access management](#security_iam_learn-more)
+ [How Amazon IoT Events works with IAM](#security_iam_service-with-iam)
+ [Amazon IoT Events identity-based policy examples](security_iam_id-based-policy-examples.md)
+ [Cross-service confused deputy prevention for Amazon IoT Events](cross-service-confused-deputy-prevention.md)
+ [Troubleshoot Amazon IoT Events identity and access](security_iam_troubleshoot.md)
## Audience
How you use Amazon Identity and Access Management (IAM) differs based on your role:
+ **Service user** - request permissions from your administrator if you cannot access features (see [Troubleshoot Amazon IoT Events identity and access](security_iam_troubleshoot.md))
+ **Service administrator** - determine user access and submit permission requests (see [How Amazon IoT Events works with IAM](#security_iam_service-with-iam))
+ **IAM administrator** - write policies to manage access (see [Amazon IoT Events identity-based policy examples](security_iam_id-based-policy-examples.md))
## More about identity and access management
For more information about identity and access management for Amazon IoT Events, continue to the following pages:
+ [How Amazon IoT Events works with IAM](#security_iam_service-with-iam)
+ [Troubleshoot Amazon IoT Events identity and access](security_iam_troubleshoot.md)
## How Amazon IoT Events works with IAM
Before you use IAM to manage access to Amazon IoT Events, you should understand what IAM features are available to use with Amazon IoT Events. To get a high-level view of how Amazon IoT Events and other Amazon services work with IAM, see [Amazon services that work with IAM](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*.
**Topics**
+ [Amazon IoT Events identity-based policies](#security_iam_service-with-iam-id-based-policies)
+ [Amazon IoT Events resource-based policies](#security_iam_service-with-iam-resource-based-policies)
+ [Authorization based on Amazon IoT Events tags](#security_iam_service-with-iam-tags)
+ [Amazon IoT Events IAM roles](#security_iam_service-with-iam-roles)
### Amazon IoT Events identity-based policies
With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied. Amazon IoT Events supports specific actions, resources, and condition keys. To learn about all of the elements that you use in a JSON policy, see [IAM JSON policy elements reference](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_elements.html) in the *IAM User Guide*.
#### Actions
The `Action` element of an IAM identity-based policy describes the specific action or actions that will be allowed or denied by the policy. Policy actions usually have the same name as the associated Amazon API operation. The action is used in a policy to grant permissions to perform the associated operation.
Policy actions in Amazon IoT Events use the following prefix before the action: `iotevents:`. For example, to grant someone permission to create an Amazon IoT Events input with the Amazon IoT Events `CreateInput` API operation, you include the `iotevents:CreateInput` action in their policy. To grant someone permission to send an input with the Amazon IoT Events `BatchPutMessage` API operation, you include the `iotevents-data:BatchPutMessage` action in their policy. Policy statements must include either an `Action` or `NotAction` element. Amazon IoT Events defines its own set of actions that describe tasks that you can perform with this service.
To specify multiple actions in a single statement, separate them with commas as follows:
```
"Action": [
"iotevents:action1",
"iotevents:action2"
```
You can specify multiple actions using wildcards (\*). For example, to specify all actions that begin with the word `Describe`, include the following action:
```
"Action": "iotevents:Describe*"
```
To see a list of Amazon IoT Events actions, see [Actions Defined by Amazon IoT Events](https://docs.amazonaws.cn/IAM/latest/UserGuide/list_awsiotevents.html#awsiotevents-actions-as-permissions) in the *IAM User Guide*.
#### Resources
The `Resource` element specifies the object or objects to which the action applies. Statements must include either a `Resource` or a `NotResource` element. You specify a resource using an ARN or using the wildcard (\*) to indicate that the statement applies to all resources.
The Amazon IoT Events detector model resource has the following ARN:
```
arn:${Partition}:iotevents:${Region}:${Account}:detectorModel/${detectorModelName}
```
For more information about the format of ARNs, see [Identify Amazon resources with Amazon Resource Names (ARNs)](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference-arns.html).
For example, to specify the `Foobar` detector model in your statement, use the following ARN:
```
"Resource": "arn:aws-cn:iotevents:us-east-1:123456789012:detectorModel/Foobar"
```
To specify all instances that belong to a specific account, use the wildcard (\*):
```
"Resource": "arn:aws-cn:iotevents:us-east-1:123456789012:detectorModel/*"
```
Some Amazon IoT Events actions, such as those for creating resources, cannot be performed on a specific resource. In those cases, you must use the wildcard (\*).
```
"Resource": "*"
```
Some Amazon IoT Events API actions involve multiple resources. For example, `CreateDetectorModel` references inputs in its condition statements, so a user must have permissions to use the input and the detector model. To specify multiple resources in a single statement, separate the ARNs with commas.
```
"Resource": [
"resource1",
"resource2"
```
To see a list of Amazon IoT Events resource types and their ARNs, see [Resources Defined by Amazon IoT Events](https://docs.amazonaws.cn/IAM/latest/UserGuide/list_awsiotevents.html#awsiotevents-resources-for-iam-policies) in the *IAM User Guide*. To learn with which actions you can specify the ARN of each resource, see [Actions Defined by Amazon IoT Events](https://docs.amazonaws.cn/IAM/latest/UserGuide/list_awsiotevents.html#awsiotevents-actions-as-permissions).
#### Condition keys
The `Condition` element (or `Condition` *block*) lets you specify conditions in which a statement is in effect. The `Condition` element is optional. You can build conditional expressions that use [condition operators](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), such as equals or less than, to match the condition in the policy with values in the request.
If you specify multiple `Condition` elements in a statement, or multiple keys in a single `Condition` element, Amazon evaluates them using a logical `AND` operation. If you specify multiple values for a single condition key, Amazon evaluates the condition using a logical `OR` operation. All of the conditions must be met before the statement's permissions are granted.
You can also use placeholder variables when you specify conditions. For example, you can grant a user permission to access a resource only if it is tagged with their user name. For more information, see [IAM policy elements: Variables and tags](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_variables.html) in the *IAM User Guide*.
Amazon IoT Events does not provide any service-specific condition keys, but it does support using some global condition keys. To see all Amazon global condition keys, see [Amazon global condition context keys](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*."
#### Examples
To view examples of Amazon IoT Events identity-based policies, see [Amazon IoT Events identity-based policy examples](security_iam_id-based-policy-examples.md).
### Amazon IoT Events resource-based policies
Amazon IoT Events does not support resource-based policies." To view an example of a detailed resource-based policy page, see [https://docs.amazonaws.cn/lambda/latest/dg/access-control-resource-based.html](https://docs.amazonaws.cn/lambda/latest/dg/access-control-resource-based.html).
### Authorization based on Amazon IoT Events tags
You can attach tags to Amazon IoT Events resources or pass tags in a request to Amazon IoT Events. To control access based on tags, you provide tag information in the [condition element](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_elements_condition.html) of a policy using the `iotevents:ResourceTag/{{key-name}}`, `aws:RequestTag/{{key-name}}`, or `aws:TagKeys` condition keys. For more information about tagging Amazon IoT Events resources, see [Tagging your Amazon IoT Events resources](tagging-iotevents.md).
To view an example identity-based policy for limiting access to a resource based on the tags on that resource, see [View Amazon IoT Events inputs based on tags](security_iam_id-based-policy-examples-view-input-tags.md).
### Amazon IoT Events IAM roles
An [IAM role](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_roles.html) is an entity within your Amazon Web Services account that has specific permissions.
#### Using temporary credentials with Amazon IoT Events
You can use temporary credentials to sign in with federation, assume an IAM role, or to assume a cross-account role. You obtain temporary security credentials by calling Amazon Security Token Service (Amazon STS) API operations such as [AssumeRole](https://docs.amazonaws.cn/STS/latest/APIReference/API_AssumeRole.html) or [GetFederationToken](https://docs.amazonaws.cn/STS/latest/APIReference/API_GetFederationToken.html).
Amazon IoT Events does not support using temporary credentials.
#### Service-linked roles
[Service-linked roles](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_roles.html#id_roles_terms-and-concepts) allow Amazon services to access resources in other services to complete an action on your behalf. Service-linked roles appear in your IAM account and are owned by the service. An IAM administrator can view but not edit the permissions for service-linked roles.
Amazon IoT Events does not support service-linked roles.
#### Service roles
This feature allows a service to assume a [service role](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_roles.html#id_roles_terms-and-concepts) on your behalf. This role allows the service to access resources in other services to complete an action on your behalf. Service roles appear in your IAM account and are owned by the account. This means that an IAM administrator can change the permissions for this role. However, doing so might break the functionality of the service.
Amazon IoT Events supports service roles.