Sample IAM policies for Session Manager
Use the samples in this section to help you create Amazon Identity and Access Management (IAM) policies that provide the most commonly needed permissions for Session Manager access.
Note
You can also use an Amazon KMS key policy to control which IAM entities (users or roles) and Amazon Web Services accounts are given access to your KMS key. For information, see Overview of Managing Access to Your Amazon KMS Resources and Using Key Policies in Amazon KMS in the Amazon Key Management Service Developer Guide.
Topics
Quickstart end user policies for Session Manager
Use the following examples to create IAM end user policies for Session Manager.
You can create a policy that allows users to start sessions from only the Session Manager console and Amazon Command Line Interface (Amazon CLI), from only the Amazon Elastic Compute Cloud (Amazon EC2) console, or from all three.
These policies provide end users the ability to start a session to a particular managed node and the ability to end only their own sessions. Refer to Additional sample IAM policies for Session Manager for examples of customizations you might want to make to the policy.
In the following sample policies, replace each example
resource placeholder with your own information.
Choose from the following tabs to view the sample policy for the range of session access you want to provide.
1
SSM-SessionManagerRunShell is the default name of the
SSM document that Session Manager creates to store your session configuration
preferences. You can create a custom Session document and specify it in this
policy instead. You can also specify the Amazon-provided document
AWS-StartSSHSession for users who are starting sessions
using SSH. For information about configuration steps needed to support
sessions using SSH, see (Optional) Allow and control permissions for SSH connections through Session Manager.
2 If you
specify the condition element,
ssm:SessionDocumentAccessCheck, as
true, the system checks that a user has explicit access to
the defined Session document, in this example
SSM-SessionManagerRunShell, before a session is
established. For more information, see Enforce a
session document permission check when starting a session.
3 The
kms:GenerateDataKey permission enables the creation of a
data encryption key that will be used to encrypt session data. If you will
use Amazon Key Management Service (Amazon KMS) encryption for your session data, replace
key-name with the Amazon Resource Name (ARN)
of the KMS key you want to use, in the format
arn:aws-cn:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-12345EXAMPLE.
If you won't use KMS key encryption for your session data, remove the
following content from the policy.
, { "Effect": "Allow", "Action": [ "kms:GenerateDataKey" ], "Resource": "key-name" }
For information about using Amazon KMS for encrypting session data, see Turn on KMS key encryption of session data (console).
4 The permission for SendCommand is needed for cases where a user attempts to start a session from the Amazon EC2 console, but the SSM Agent must be updated to the minimum required version for Session Manager first. Run Command is used to send a command to the instance to update the agent.
Quickstart administrator policy for Session Manager
Use the following examples to create IAM administrator policies for Session Manager.
These policies provide administrators the ability to start a session to
managed nodes that are tagged with
Key=Finance,Value=WebServers, permission to create, update, and
delete preferences, and permission to end only their own sessions. Refer to
Additional sample
IAM policies for Session Manager for examples
of customizations you might want to make to the policy.
You can create a policy that allows administrators to perform these tasks from only the Session Manager console and Amazon CLI, from only the Amazon EC2 console, or from all three.
In the following sample policies, replace each example
resource placeholder with your own information.
Choose from the following tabs to view the sample policy for the access scenario you want to support.
1 The permission for SendCommand is needed for cases where a user attempts to start a session from the Amazon EC2 console, but a command must be sent to update SSM Agent first.