# Identity and access management for AWS User Notifications AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources. IAM administrators control who can be *authenticated* (signed in) and *authorized* (have permissions) to use User Notifications resources. IAM is an AWS service that you can use with no additional charge. **Topics** + [Audience](#security_iam_audience) + [Authenticating with identities](#security_iam_authentication) + [Managing access using policies](#security_iam_access-manage) + [How AWS User Notifications works with IAM](security_iam_service-with-iam.md) + [AWS User Notifications identity-based policy examples](security_iam_id-based-policy-examples.md) + [Resource-level permissions in AWS User Notifications](resource-level-permissions.md) + [Using Service-Linked Roles for User Notifications](using-service-linked-roles.md) + [AWS managed policies for AWS User Notifications](security-iam-awsmanpolicy.md) + [Troubleshooting AWS User Notifications identity and access](security_iam_troubleshoot.md) ## Audience How you use AWS Identity and Access Management (IAM) differs based on your role: + **Service user** - request permissions from your administrator if you cannot access features (see [Troubleshooting AWS User Notifications identity and access](security_iam_troubleshoot.md)) + **Service administrator** - determine user access and submit permission requests (see [How AWS User Notifications works with IAM](security_iam_service-with-iam.md)) + **IAM administrator** - write policies to manage access (see [AWS User Notifications identity-based policy examples](security_iam_id-based-policy-examples.md)) ## Authenticating with identities Authentication is how you sign in to AWS using your identity credentials. You must be authenticated as the AWS account root user, an IAM user, or by assuming an IAM role. You can sign in as a federated identity using credentials from an identity source like AWS IAM Identity Center (IAM Identity Center), single sign-on authentication, or Google/Facebook credentials. For more information about signing in, see [How to sign in to your AWS account](https://docs.aws.amazon.com/signin/latest/userguide/how-to-sign-in.html) in the *AWS Sign-In User Guide*. For programmatic access, AWS provides an SDK and CLI to cryptographically sign requests. For more information, see [AWS Signature Version 4 for API requests](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html) in the *IAM User Guide*. ### AWS account root user When you create an AWS account, you begin with one sign-in identity called the AWS account *root user* that has complete access to all AWS services and resources. We strongly recommend that you don't use the root user for everyday tasks. For tasks that require root user credentials, see [Tasks that require root user credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks) in the *IAM User Guide*. ### IAM users and groups An *[IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html)* is an identity with specific permissions for a single person or application. We recommend using temporary credentials instead of IAM users with long-term credentials. For more information, see [Require human users to use federation with an identity provider to access AWS using temporary credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp) in the *IAM User Guide*. An [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html) specifies a collection of IAM users and makes permissions easier to manage for large sets of users. For more information, see [Use cases for IAM users](https://docs.aws.amazon.com/IAM/latest/UserGuide/gs-identities-iam-users.html) in the *IAM User Guide*. ### IAM roles An *[IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)* is an identity with specific permissions that provides temporary credentials. You can assume a role by [switching from a user to an IAM role (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html) or by calling an AWS CLI or AWS API operation. For more information, see [Methods to assume a role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage-assume.html) in the *IAM User Guide*. IAM roles are useful for federated user access, temporary IAM user permissions, cross-account access, cross-service access, and applications running on Amazon EC2. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*. ## Managing access using policies You control access in AWS by creating policies and attaching them to AWS identities or resources. A policy defines permissions when associated with an identity or resource. AWS evaluates these policies when a principal makes a request. Most policies are stored in AWS as JSON documents. For more information about JSON policy documents, see [Overview of JSON policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#access_policies-json) in the *IAM User Guide*. Using policies, administrators specify who has access to what by defining which **principal** can perform **actions** on what **resources**, and under what **conditions**. By default, users and roles have no permissions. An IAM administrator creates IAM policies and adds them to roles, which users can then assume. IAM policies define permissions regardless of the method used to perform the operation. ### Identity-based policies Identity-based policies are JSON permissions policy documents that you attach to an identity (user, group, or role). These policies control what actions identities can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*. Identity-based policies can be *inline policies* (embedded directly into a single identity) or *managed policies* (standalone policies attached to multiple identities). To learn how to choose between managed and inline policies, see [Choose between managed policies and inline policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-choosing-managed-or-inline.html) in the *IAM User Guide*. ### Access control lists (ACLs) Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format. Amazon S3, AWS WAF, and Amazon VPC are examples of services that support ACLs. To learn more about ACLs, see [Access control list (ACL) overview](https://docs.aws.amazon.com/AmazonS3/latest/userguide/acl-overview.html) in the *Amazon Simple Storage Service Developer Guide*. ### Other policy types AWS supports additional policy types that can set the maximum permissions granted by more common policy types: + **Permissions boundaries** – Set the maximum permissions that an identity-based policy can grant to an IAM entity. For more information, see [Permissions boundaries for IAM entities](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html) in the *IAM User Guide*. + **Service control policies (SCPs)** – Specify the maximum permissions for an organization or organizational unit in AWS Organizations. For more information, see [Service control policies](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) in the *AWS Organizations User Guide*. + **Resource control policies (RCPs)** – Set the maximum available permissions for resources in your accounts. For more information, see [Resource control policies (RCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html) in the *AWS Organizations User Guide*. + **Session policies** – Advanced policies passed as a parameter when creating a temporary session for a role or federated user. For more information, see [Session policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session) in the *IAM User Guide*. ### Multiple policy types When multiple types of policies apply to a request, the resulting permissions are more complicated to understand. To learn how AWS determines whether to allow a request when multiple policy types are involved, see [Policy evaluation logic](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html) in the *IAM User Guide*. # How AWS User Notifications works with IAM Before you use IAM to manage access to User Notifications, you should understand what IAM features are available to use with User Notifications. To get a high-level view of how User Notifications and other AWS services work with IAM, see [AWS Services That Work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*. **Note** User Notifications uses resource-level permissions and managed policies to define what actions users can take. **Topics** + [User Notifications Identity-based policies](#security_iam_service-with-iam-id-based-policies) + [Authorization based on User Notifications tags](#security_iam_service-with-iam-tags) + [User Notifications IAM roles](#security_iam_service-with-iam-roles) ## User Notifications Identity-based policies With IAM identity-based policies, you can specify allowed or denied actions and resources. You can also specify the conditions under which actions are allowed or denied. User Notifications 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.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html) in the *IAM User Guide*. ### Actions Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Action` element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Include actions in a policy to grant permissions to perform the associated operation. Policy actions in User Notifications use the following prefixes before the action: + `notifications-contacts:` - Used for email contact actions. + `notifications:` - Used for all other actions. For example, to grant someone permission to update notification configurations with the `UpdateNotificationConfiguration` API operation, you include the `notifications:UpdateNotificationConfiguration` action in their policy. Policy statements must include either an `Action` or `NotAction` element. User Notifications 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": [ "notifications:action1", "notifications:action2" ``` You can specify multiple actions using wildcards (\$1). For example, to specify all actions that begin with the word `Get`, include the following action: ``` "Action": "notifications:Get*" ``` ### Resources Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Resource` JSON policy element specifies the object or objects to which the action applies. As a best practice, specify a resource using its [Amazon Resource Name (ARN)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html). For actions that don't support resource-level permissions, use a wildcard (\$1) to indicate that the statement applies to all resources. ``` "Resource": "*" ``` For a list of resource types and their ARNs for User Notifications and User Notifications Contacts, see [Resources Defined by AWS User Notifications ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awsusernotifications.html#awsusernotifications-resources-for-iam-policies) and [Resources Defined by AWS User Notifications Contacts ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awsusernotificationscontacts.html#awsusernotificationscontacts-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 AWS User Notifications ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awsusernotifications.html#awsusernotifications-actions-as-permissions). ### Condition keys Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Condition` element specifies when statements execute based on defined criteria. You can create conditional expressions that use [condition operators](https://docs.aws.amazon.com/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. To see all AWS global condition keys, see [AWS global condition context keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*. User Notifications defines its own set of condition keys and also supports using some global condition keys. To see all AWS global condition keys, see [AWS Global Condition Context Keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*. To see a list of condition keys for User Notifications and User Notifications Contacts, see [Condition Keys for AWS User Notifications ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awsusernotifications.html#awsusernotifications-policy-keys) and [Condition Keys for AWS User Notifications Contacts ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awsusernotificationscontacts.html#awsusernotificationscontacts-policy-keys) in the *IAM User Guide*. To learn with which actions and resources you can use a condition key, see [Actions Defined by AWS User Notifications ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awsusernotifications.html#awsusernotifications-actions-as-permissions) and [Actions Defined by AWS User Notifications Contacts](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awsusernotificationscontacts.html#awsusernotificationscontacts-actions-as-permissions). ### Examples To view examples of User Notifications identity-based policies, see [AWS User Notifications identity-based policy examples](security_iam_id-based-policy-examples.md). ## Authorization based on User Notifications tags You can attach tags to User Notifications resources or pass tags in a request to User Notifications. To control access based on tags, you provide tag information in the [condition element](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) of a policy using the `notifications:ResourceTag/key-name`, `aws:RequestTag/key-name`, or `aws:TagKeys` condition keys. For more information about tagging User Notifications resources, see [Tagging your AWS User Notifications resources](tagging-resources.md). To view an example identity-based policy for limiting access to a resource based on the tags on that resource, see [Viewing User Notifications notification configurations based on tags](security_iam_id-based-policy-examples.md#security_iam_id-based-policy-examples-view-resource-tags). ## User Notifications IAM roles An [IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) is an entity within your AWS account that has specific permissions. ### Service-linked roles [Service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role) allow AWS 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. User Notifications supports service-linked roles. For details about creating or managing User Notifications service-linked roles, see [Using Service-Linked Roles for User Notifications](using-service-linked-roles.md). # AWS User Notifications identity-based policy examples By default, IAM users and roles don't have permission to create or modify User Notifications resources. They also can't perform tasks using the AWS Management Console. An IAM administrator must create IAM policies that grant users and roles permission to perform specific API operations on the specified resources they need. The administrator must then attach those policies to the IAM users or groups that require those permissions. To learn how to create an IAM identity-based policy using these example JSON policy documents, see [Creating Policies on the JSON Tab](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html#access_policies_create-json-editor) in the *IAM User Guide*. **Topics** + [Policy best practices](#security_iam_service-with-iam-policy-best-practices) + [Using the User Notifications console](#security_iam_id-based-policy-examples-console) + [Allow users to view their own permissions](#security_iam_id-based-policy-examples-view-own-permissions) + [Viewing User Notifications notification configurations based on tags](#security_iam_id-based-policy-examples-view-resource-tags) ## Policy best practices Identity-based policies determine whether someone can create, access, or delete User Notifications resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations: + **Get started with AWS managed policies and move toward least-privilege permissions** – To get started granting permissions to your users and workloads, use the *AWS managed policies* that grant permissions for many common use cases. They are available in your AWS account. We recommend that you reduce permissions further by defining AWS customer managed policies that are specific to your use cases. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) or [AWS managed policies for job functions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*. + **Apply least-privilege permissions** – When you set permissions with IAM policies, grant only the permissions required to perform a task. You do this by defining the actions that can be taken on specific resources under specific conditions, also known as *least-privilege permissions*. For more information about using IAM to apply permissions, see [ Policies and permissions in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*. + **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the *IAM User Guide*. + **Use IAM Access Analyzer to validate your IAM policies to ensure secure and functional permissions** – IAM Access Analyzer validates new and existing policies so that the policies adhere to the IAM policy language (JSON) and IAM best practices. IAM Access Analyzer provides more than 100 policy checks and actionable recommendations to help you author secure and functional policies. For more information, see [Validate policies with IAM Access Analyzer](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-policy-validation.html) in the *IAM User Guide*. + **Require multi-factor authentication (MFA)** – If you have a scenario that requires IAM users or a root user in your AWS account, turn on MFA for additional security. To require MFA when API operations are called, add MFA conditions to your policies. For more information, see [ Secure API access with MFA](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_configure-api-require.html) in the *IAM User Guide*. For more information about best practices in IAM, see [Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*. ## Using the User Notifications console To access the AWS User Notifications console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the User Notifications resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (IAM users or roles) with that policy. ## Allow users to view their own permissions This example shows how you might create a policy that allows IAM users to view the inline and managed policies that are attached to their user identity. This policy includes permissions to complete this action on the console or programmatically using the AWS CLI or AWS API. ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "ViewOwnUserInfo", "Effect": "Allow", "Action": [ "iam:GetUserPolicy", "iam:ListGroupsForUser", "iam:ListAttachedUserPolicies", "iam:ListUserPolicies", "iam:GetUser" ], "Resource": ["arn:aws:iam::*:user/${aws:username}"] }, { "Sid": "NavigateInConsole", "Effect": "Allow", "Action": [ "iam:GetGroupPolicy", "iam:GetPolicyVersion", "iam:GetPolicy", "iam:ListAttachedGroupPolicies", "iam:ListGroupPolicies", "iam:ListPolicyVersions", "iam:ListPolicies", "iam:ListUsers" ], "Resource": "*" } ] } ``` ## Viewing User Notifications notification configurations based on tags You can use conditions in your identity-based policy to control access to User Notifications resources based on tags. This example shows how you can create a policy that allows viewing a notification configuration. However, permission is granted only if the notification configuration tag `Owner` has the value of that user's user name. This policy also grants the permissions necessary to complete this action on the console. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "ListNotificationConfigurationsInConsole", "Effect": "Allow", "Action": "notifications:ListNotificationConfigurations", "Resource": "*" }, { "Sid": "ViewNotificationConfigurationIfOwner", "Effect": "Allow", "Action": "notifications:GetNotificationConfiguration", "Resource": "arn:aws:notifications:*:*:configuration/*", "Condition": { "StringEquals": {"aws:ResourceTag/Owner": "${aws:username}"} } } ] } ``` ------ You can attach this policy to the IAM users in your account. If a user named `richard-roe` attempts to view an User Notifications notification configuration, the notification configuration must be tagged `Owner=richard-roe` or `owner=richard-roe`. Otherwise, he is denied access. The condition tag key `Owner` matches both `Owner` and `owner` because condition key names aren't case-sensitive. For more information, see [IAM JSON Policy Elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the *IAM User Guide*. # Resource-level permissions in AWS User Notifications *Resource-level permissions* define the AWS resources that you allow assigned entities (users, groups, and roles) to perform actions on. You specifiy the Amazon Resource Name (ARN) of one or more resources as part of an IAM policy. You can then attach this policy to IAM entities. When the action doesn't act on a named resource, or when you grant permission to perform the action on all resources, the value of the resource in the policy is a wildcard (\$1). **Note** AWS User Notifications doesn't support *resource-based policies*, which are directly attached to AWS resources. For more information about the differences between policies and permissions, see [Identity-based policies and resource-based policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_identity-vs-resource.html) in the *IAM User Guide*. For more information about defining resource-level permissions, see [Creating IAM policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*. ## Supported resource-level permissions for User Notifications API actions This table describes the User Notifications API actions that currently support resource-level permissions, as well as the supported resources for each action, including their ARNs and ARN format. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/notifications/latest/userguide/resource-level-permissions.html) ## Example 1: Full access This policy allows a user to call all available APIs. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "notifications:*", "notifications-contacts:*" ], "Resource": "*" } ] } ``` ------ ## Example 2: ReadOnly access This policy allows a user to use get and list API actions. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "notifications:Get*", "notifications:List*", "notifications-contacts:Get*", "notifications-contacts:List*" ], "Resource": "*" } ] } ``` ------ ## Example 3: Deny a user the ability to update a notification configuration This policy denies a user the ability to update a notification configuration. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Deny", "Action": [ "notifications:UpdateNotificationConfiguration" ], "Resource": "arn:aws:notifications::123456789012:configuration/a01gkn2k10c7spt0a8x8nj55555" } ] } ``` ------ ## Example 4: Allow users to create notification configurations and associate emails to them This policy allows users to create notification configurations and associate emails to those configurations. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "iam:CreateServiceLinkedRole", "notifications:RegisterNotificationHub", "notifications:CreateNotificationConfiguration", "notifications:CreateEventRule", "notifications:AssociateChannel", "notifications-contacts:CreateEmailContact", "notifications-contacts:SendActivationCode", "notifications-contacts:ActivateEmailContact" ], "Resource": "*" } ] } ``` ------ ## Example 5: Allow users full create, read, update, and delete (CRUD) access. This policy allows users full CRUD access. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "iam:CreateServiceLinkedRole", "notifications:*", "notifications-contacts:*" ], "Resource": "*" } ] } ``` ------ ## Example 6: Full read-write access with explicit actions This policy grants a user full read-write access to AWS User Notifications by listing all individual actions explicitly. This includes user-configured notifications, managed notifications, organizations, and tagging permissions. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "UserNotificationsReadWrite", "Effect": "Allow", "Action": [ "iam:CreateServiceLinkedRole", "notifications:RegisterNotificationHub", "notifications:DeregisterNotificationHub", "notifications:ListNotificationHubs", "notifications:CreateNotificationConfiguration", "notifications:UpdateNotificationConfiguration", "notifications:GetNotificationConfiguration", "notifications:DeleteNotificationConfiguration", "notifications:ListNotificationConfigurations", "notifications:CreateEventRule", "notifications:UpdateEventRule", "notifications:GetEventRule", "notifications:DeleteEventRule", "notifications:ListEventRules", "notifications:AssociateChannel", "notifications:DisassociateChannel", "notifications:ListChannels", "notifications:GetNotificationEvent", "notifications:ListNotificationEvents", "notifications:GetManagedNotificationConfiguration", "notifications:ListManagedNotificationConfigurations", "notifications:ListManagedNotificationChannelAssociations", "notifications:AssociateManagedNotificationAccountContact", "notifications:DisassociateManagedNotificationAccountContact", "notifications:AssociateManagedNotificationAdditionalChannel", "notifications:DisassociateManagedNotificationAdditionalChannel", "notifications:GetManagedNotificationEvent", "notifications:ListManagedNotificationEvents", "notifications:GetManagedNotificationChildEvent", "notifications:ListManagedNotificationChildEvents", "notifications:EnableNotificationsAccessForOrganization", "notifications:DisableNotificationsAccessForOrganization", "notifications:AssociateOrganizationalUnit", "notifications:DisassociateOrganizationalUnit", "notifications:ListOrganizationalUnits", "notifications:ListMemberAccounts", "notifications:GetNotificationsAccessForOrganization", "notifications:TagResource", "notifications:ListTagsForResource", "notifications:UntagResource", "notifications-contacts:CreateEmailContact", "notifications-contacts:SendActivationCode", "notifications-contacts:ActivateEmailContact", "notifications-contacts:DeleteEmailContact", "notifications-contacts:GetEmailContact", "notifications-contacts:ListEmailContacts", "notifications-contacts:TagResource", "notifications-contacts:UntagResource", "notifications-contacts:ListTagsForResource" ], "Resource": "*" } ] } ``` ------ ## Example 7: Resource-scoped access for managed notifications This policy demonstrates least-privilege access by scoping managed notification permissions to a specific category (and optionally a specific sub-category) using resource-level ARNs. Replace the category (and optionally the sub-category) in the ARN to match your use case. This example uses AWS Health managed notifications. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "ScopedManagedNotifications", "Effect": "Allow", "Action": [ "notifications:GetManagedNotificationConfiguration", "notifications:ListManagedNotificationConfigurations", "notifications:ListManagedNotificationChannelAssociations", "notifications:AssociateManagedNotificationAccountContact", "notifications:DisassociateManagedNotificationAccountContact", "notifications:AssociateManagedNotificationAdditionalChannel", "notifications:DisassociateManagedNotificationAdditionalChannel", "notifications:GetManagedNotificationEvent", "notifications:ListManagedNotificationEvents", "notifications:GetManagedNotificationChildEvent", "notifications:ListManagedNotificationChildEvents" ], "Resource": "arn:aws::notifications::123456789012:managed-notification-configuration/category/AWS-Health/sub-category/*" } ] } ``` ------ # Using Service-Linked Roles for User Notifications AWS User Notifications uses AWS Identity and Access Management (IAM) [service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role). A service-linked role is a unique type of IAM role that is linked directly to User Notifications. Service-linked roles are predefined by User Notifications and include all the permissions that the service requires to call other AWS services on your behalf. A service-linked role streamlines setting up User Notifications because you don’t have to manually add the necessary permissions. User Notifications defines the permissions of its service-linked roles. Unless defined otherwise, only User Notifications can assume its roles. The defined permissions include the trust policy and the permissions policy. That permissions policy can't be attached to any other IAM entity. For information about other services that support service-linked roles, see [AWS Services That Work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) and look for the services that have **Yes** in the **Service-Linked Role** column. Choose a **Yes** with a link to view the service-linked role documentation for that service. **Topics** + [AWS User Notifications service-Linked Role for calling AWS services, publishing metrics, and using AWS Organizations](slr-call-services.md) + [Supported Regions for User Notifications Service-Linked Roles](#slr-regions) + [Amazon EventBridge managed rules in AWS User Notifications](ev-managed-rules.md) # AWS User Notifications service-Linked Role for calling AWS services, publishing metrics, and using AWS Organizations User Notifications uses the service-linked role named **AWSServiceRoleForAWSUserNotifications**. This role allows User Notifications to call AWS services on your behalf and use AWS Organizations to manage your notification configurations across your organizations. It also allows the role to publish metrics in the `AWS/Notifications` namespace. ## Service-Linked Role Permissions for User Notifications User Notifications uses the service-linked role named **AWSServiceRoleForAWSUserNotifications**. This role allows User Notifications to call AWS services on your behalf and use AWS Organizations to manage your notification configurations across your organizations. It also allows the role to publish metrics in the `AWS/Notifications` namespace. The **AWSServiceRoleForAWSUserNotifications** service-linked role trusts the following services to assume the role: + `notifications.amazonaws.com` You must configure permissions to allow an IAM entity (such as a user, group, or role) to create, edit, or delete a service-linked role. For more information, see [Service-Linked Role Permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#service-linked-role-permissions) in the *IAM User Guide*. When you create a notification hub or a notification configuration, it creates the `AWSUserNotificationsServiceLinkedRolePolicy`. For more information, see [AWS managed policy: AWSUserNotificationsServiceLinkedRolePolicy](security-iam-awsmanpolicy.md#managed-policy-uno) You don't need to take any action to support this role beyond using User Notifications. ## Creating a Service-Linked Role for User Notifications You don't need to manually create a service-linked role. When you create a notification hub or a notification configuration in the AWS Management Console, or when you enable service trust with AWS Organizations, User Notifications creates the service-linked role for you. If you delete this service-linked role and need to create it again later, you can use the same process to recreate the role in your account. When you create a notification hub or a notification configuration, User Notifications creates the service-linked role for you again. ## Editing a Service-Linked Role for User Notifications User Notifications doesn't allow you to edit the AWSServiceRoleForAWSUserNotifications service-linked role. After you create a service-linked role, you can't change the name of the role. This is because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see [Editing a Service-Linked Role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#edit-service-linked-role) in the *IAM User Guide*. ## Manually deleting a Service-Linked Role for User Notifications Under specific circumstances, you can manually delete the AWSServiceRoleForAWSUserNotifications service-linked role. To delete the User Notifications service-linked role, you must first delete all notification configurations in the account. You can delete all User Notifications notification configurations using the User Notifications console. You then use the IAM console, the AWS CLI, or the AWS API to delete the AWSServiceRoleForAWSUserNotifications service-linked role. For more information, see [Deleting a Service-Linked Role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#delete-service-linked-role) in the *IAM User Guide*. **Note** If the User Notifications service is using the role when you try to delete the resources, the deletion might fail. If that happens, wait for a few minutes and try the operation again. **To delete notification configurations** 1. Open User Notifications in the [AWS Management Console](https://console.aws.amazon.com/). 1. In the navigation pane, choose **Notification configurations**. 1. Select the configuration you want to delete. 1. Choose **Delete**. ## Supported Regions for User Notifications Service-Linked Roles User Notifications supports using service-linked roles in all of the Regions where the service is available. For more information, see [AWS Regions and Endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html). # Amazon EventBridge managed rules in AWS User Notifications AWS User Notifications uses Amazon EventBridge managed rules. A managed rule is a unique type of rule that is directly linked to User Notifications. These rules match incoming events and send them to targets for processing. Managed rules are predefined by User Notifications and include event patterns that are required by the service to manage customer notifications, and unless defined otherwise, only the owning service can utilize these managed rules. For more information, see [Rules](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-rules.html) in the *Amazon EventBridge User Guide*. User Notifications managed rules are linked to `notifications.amazonaws.com` service principal. These managed rules are managed through the [`AWSUserNotificationsServiceLinkedRolePolicy` service-linked role](slr-call-services.md). To delete these rules, a special confirmation by the customer is required. For more information, see [Deleting managed rules for AWS User Notifications](#delete-rules). ## Amazon EventBridge managed rules deployed by AWS User Notifications The followng table displays Amazon EventBridge managed rules: | Rule name | Description | Definition | | --- | --- | --- | | AWSUserNotificationsManagedRule- | AWS User Notifications rule for source. This can be any Amazon EventBridge source. For example, `aws.cloudwatch`. | Example: 
{"source": ["aws.cloudwatch"],"detail-type": ["CloudWatch Alarm State Change"]}
| **Note** The managed rule User Notifications creates in EventBridge only contains source and detail-type fields, regardless of whether the User Notifications event rule includes additional filters. User Notifications always filters based on the User Notifications event rule. For example, the User Notifications event rule for Amazon Elastic Compute Cloud instance state changed to "terminated", "stopping", "stopped", or "shutting-down" shows: ``` { "source": ["aws.ec2"], "detail-type": ["EC2 Instance State-change Notification"], "detail": { "state": ["terminated", "stopping", "stopped", "shutting-down"] } } ``` The corresponding EventBridge managed rule shows: ``` { "source": ["aws.ec2"], "detail-type": ["EC2 Instance State-change Notification"] } ``` This rule only generates notifications for Amazon EC2 instance state changed to "terminated", "stopping", "stopped", or "shutting-down". It won't generate notifications for other state changes. ## Creating managed rules for AWS User Notifications You don’t need to manually create Amazon EventBridge managed rules. Managed rules are automatically created for you based on your specified event rules when you create notification configurations. User Notifications creates one managed rule per source (for example, EC2, S3). Newly created event rules correspond to existing managed rules if applicable. If no existing managed rules are found, User Notifications creates a new managed rule. ## Editing managed rules for AWS User Notifications User Notifications doesn't allow you to edit managed rules. The name, description, and event pattern for each managed rule are predefined by User Notifications. ## Deleting managed rules for AWS User Notifications **Warning** Don't delete User Notifications managed rules unless you're certain all dependent event rules are removed. Deleting managed rules that are being used by User Notifications may cause some notifications to stop working. For more information, see [Rules managed by AWS services](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-rules.html#eb-rules-managed) in the *Amazon EventBridge User Guide*. You don’t need to manually delete managed rules. When you delete a notification configuration or specific event rule in a notification configuration, User Notifications cleans up the resources and deletes applicable managed rules owned by User Notifications for you. # AWS managed policies for AWS User Notifications An AWS managed policy is a standalone policy that is created and administered by AWS. AWS managed policies are designed to provide permissions for many common use cases so that you can start assigning permissions to users, groups, and roles. Keep in mind that AWS managed policies might not grant least-privilege permissions for your specific use cases because they're available for all AWS customers to use. We recommend that you reduce permissions further by defining [ customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#customer-managed-policies) that are specific to your use cases. You cannot change the permissions defined in AWS managed policies. If AWS updates the permissions defined in an AWS managed policy, the update affects all principal identities (users, groups, and roles) that the policy is attached to. AWS is most likely to update an AWS managed policy when a new AWS service is launched or new API operations become available for existing services. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) in the *IAM User Guide*. AWS User Notifications does not have service-specific AWS managed policies. However, User Notifications actions are included in the following AWS managed policies: + [https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html#jf_administrator](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html#jf_administrator) – Grants full access to all AWS services, including User Notifications. + [https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html#awsmp_readonlyaccess](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html#awsmp_readonlyaccess) – Grants read-only access to all AWS services, including User Notifications get and list actions. For examples of identity-based policies specific to User Notifications, see [Resource-level permissions in AWS User Notifications](resource-level-permissions.md). ## AWS managed policy: AWSUserNotificationsServiceLinkedRolePolicy You can't attach `AWSUserNotificationsServiceLinkedRolePolicy` to your IAM entities. This policy is attached to `AWSServiceRoleForAWSUserNotifications`, a service-linked role that allows User Notifications to call AWS services on your behalf, publish Amazon CloudWatch metrics, and use AWS Organizations to manage notification configurations across your organizations. For more information, see [Using Service-Linked Roles for User Notifications](using-service-linked-roles.md). **Permissions details** This `AWSUserNotificationsServiceLinkedRolePolicy` is grouped into the following sets of permissions: + `cloudwatch` — allows principals to publish Amazon CloudWatch metrics in the `AWS/Notifications` namespace. + `events` — allows principals to manage Amazon EventBridge rules and targets for User Notifications. + `notifications` — allows principals to manage notification configurations and event rules across an organization. + `organizations` — allows principals to access and list AWS Organizations information, including delegated administrators for the `notifications.amazonaws.com` service principal. To view the permissions for this policy, see [AWSUserNotificationsServiceLinkedRolePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSUserNotificationsServiceLinkedRolePolicy.html) in the *AWS Managed Policy Reference*. ## User Notifications updates to AWS managed policies View details about updates to AWS managed policies for User Notifications since this service began tracking these changes. For automatic alerts about changes to this page, subscribe to the RSS feed on the [Document history for the AWS User Notifications User Guide](doc-history.md) page. | Change | Description | Date | | --- | --- | --- | | [AWSUserNotificationsServiceLinkedRolePolicy](#managed-policy-uno) - Change | Added `organizations:ListDelegatedAdministrators`, `notifications:CreateNotificationConfiguration`, `notifications:DeleteNotificationConfiguration`, `notifications:CreateEventRule`, `notifications:UpdateEventRule`, and `notifications:DeleteEventRule` to the policy. These permissions allow management accounts to distribute notification configurations across an organization. | August 15, 2025 | | [AWSUserNotificationsServiceLinkedRolePolicy](#managed-policy-uno) - Change | Added `organizations:DescribeAccount`, `organizations:DescribeOrganization`, `organizations:DescribeOrganizationalUnit`, `organizations:ListAccounts`, `organizations:ListAWSServiceAccessForOrganization`, `organizations:ListChildren`, and `organizations:ListParents` to the policy. These permissions allow User Notifications to make calls to the AWS Organizations API so users can manage and monitor notifications across their organizations. | January 15, 2025 | | [AWSUserNotificationsServiceLinkedRolePolicy](#managed-policy-uno) - New policy | Allows User Notifications to create, read, update, and delete managed rules in the account. Allows User Notifications to to publish Amazon CloudWatch metrics within the `AWS/Notifications` namespace. | April 20, 2023 | | User Notifications started tracking changes | User Notifications started tracking changes for its AWS managed policies. | April 10, 2023 | # Troubleshooting AWS User Notifications identity and access Use the following information to help you diagnose and fix common issues that you might encounter when working with User Notifications and IAM. **Topics** + [I Am Not Authorized to Perform an Action in User Notifications](#security_iam_troubleshoot-no-permissions) + [I'm an Administrator and Want to Allow Others to Access User Notifications](#security_iam_troubleshoot-admin-delegate) + [I Want to Allow People Outside of My AWS Account to Access My User Notifications Resources](#security_iam_troubleshoot-cross-account-access) ## I Am Not Authorized to Perform an Action in User Notifications If the AWS Management Console tells you that you're not authorized to perform an action, then you must contact your administrator for assistance. Your administrator is the person that provided you with your user name and password. The following example error occurs when the `mateojackson` IAM user tries to use the console to view details about a notification configuration, but does not have `notifications:GetNotificationConfiguration` permissions. ``` User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: notifications:GetNotificationConfiguration on resource: my-example-notificationconfiguration ``` In this case, Mateo asks his administrator to update his policies to allow him to access the `my-example-notificationconfiguration` resource using the `notifications:GetNotificationConfiguration` action. ## I'm an Administrator and Want to Allow Others to Access User Notifications To allow others to access User Notifications, you must grant permission to the people or applications that need access. If you are using AWS IAM Identity Center to manage people and applications, you assign permission sets to users or groups to define their level of access. Permission sets automatically create and assign IAM policies to IAM roles that are associated with the person or application. For more information, see [Permission sets](https://docs.aws.amazon.com/singlesignon/latest/userguide/permissionsetsconcept.html) in the *AWS IAM Identity Center User Guide*. If you are not using IAM Identity Center, you must create IAM entities (users or roles) for the people or applications that need access. You must then attach a policy to the entity that grants them the correct permissions in User Notifications. After the permissions are granted, provide the credentials to the user or application developer. They will use those credentials to access AWS. To learn more about creating IAM users, groups, policies, and permissions, see [IAM Identities](https://docs.aws.amazon.com/IAM/latest/UserGuide/id.html) and [Policies and permissions in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*. ## I Want to Allow People Outside of My AWS Account to Access My User Notifications Resources You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources. To learn more, consult the following: + To learn whether User Notifications supports these features, see [How AWS User Notifications works with IAM](security_iam_service-with-iam.md). + To learn how to provide access to your resources across AWS accounts that you own, see [Providing access to an IAM user in another AWS account that you own](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_aws-accounts.html) in the *IAM User Guide*. + To learn how to provide access to your resources to third-party AWS accounts, see [Providing access to AWS accounts owned by third parties](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html) in the *IAM User Guide*. + To learn how to provide access through identity federation, see [Providing access to externally authenticated users (identity federation)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_federated-users.html) in the *IAM User Guide*. + To learn the difference between using roles and resource-based policies for cross-account access, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.