Identity-based policy examples for AWS Systems Manager Incident Manager - Incident Manager

Identity-based policy examples for AWS Systems Manager Incident Manager

By default, IAM users and roles don't have permission to create or modify Incident Manager resources. They also can't perform tasks using the AWS Management Console, AWS CLI, or AWS API. An IAM administrator must create IAM policies that grant users and roles permission to perform actions on the resources that 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 in the IAM User Guide.

Policy best practices

Identity-based policies are very powerful. They determine whether someone can create, access, or delete Incident Manager 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 using AWS managed policies – To start using Incident Manager quickly, use AWS managed policies to give your employees the permissions they need. These policies are already available in your account and are maintained and updated by AWS. For more information, see Get started using permissions with AWS managed policies in the IAM User Guide.

  • Grant least privilege – When you create custom policies, grant only the permissions required to perform a task. Start with a minimum set of permissions and grant additional permissions as necessary. Doing so is more secure than starting with permissions that are too lenient and then trying to tighten them later. For more information, see Grant least privilege in the IAM User Guide.

  • Enable MFA for sensitive operations – For extra security, require IAM users to use multi-factor authentication (MFA) to access sensitive resources or API operations. For more information, see Using multi-factor authentication (MFA) in AWS in the IAM User Guide.

  • Use policy conditions for extra security – To the extent that it's practical, define the conditions under which your identity-based policies allow access to a resource. For example, you can write conditions to specify a range of allowable IP addresses that a request must come from. You can also write conditions to allow requests only within a specified date or time range, or to require the use of SSL or MFA. For more information, see IAM JSON policy elements: Condition in the IAM User Guide.

Using the Incident Manager console

To access the AWS Systems Manager Incident Manager console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the Incident Manager 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.

You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that you're trying to perform.

To ensure that users and roles can resolve incident using the Incident Manager console, also attach the Incident Manager IncidentManagerResolverAccess AWS managed policy to the entities. For more information, see Adding permissions to a user in the IAM User Guide.


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": "*" } ] }

Accessing a response plan

In this example, you want to grant an IAM user in your Amazon Web Services account access to one of your Incident Manager response plans, exampleplan. You also want to allow the user to add, update, and delete the response plan.

The policy grants the ssm-incidents:ListResponsePlans, ssm-incidents:GetResponsePlan, ssm-incidents:UpdateResponsePlan and ssm-incident:ListResponsePlan permissions to the user.

{ "Version":"2012-10-17", "Statement":[ { "Sid":"ListResponsePlans", "Effect":"Allow", "Action":[ "ssm-incidents:ListResponsePlans" ], "Resource":"arn:aws:ssm-incidents:::*" }, { "Sid":"ViewSpecificResponsePlanInfo", "Effect":"Allow", "Action":[ "ssm-incidents:GetResponsePlan" ], "Resource":"arn:aws:ssm-incidents:*:111122223333:response-plan/exampleplan" }, { "Sid":"ManageResponsePlan", "Effect":"Allow", "Action":[ "ssm-incidents:UpdateResponsePlan" ], "Resource":"arn:aws:ssm-incidents:*:111122223333:response-plan/exampleplan/*" } ] }