Amazon SageMaker
Developer Guide

The AWS Documentation website is getting a new look!
Try it now and let us know what you think. Switch to the new look >>

You can return to the original look by selecting English in the language selector above.

How Amazon SageMaker Works with IAM

Before you use IAM to manage access to Amazon SageMaker, you should understand what IAM features are available to use with Amazon SageMaker. To get a high-level view of how Amazon SageMaker and other AWS services work with IAM, see AWS Services That Work with IAM in the IAM User Guide.

Amazon SageMaker 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 SageMaker 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 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 AWS API operation. The action is used in a policy to grant permissions to perform the associated operation.

Policy actions in Amazon SageMaker use the following prefix before the action: sagemaker:. For example, to grant someone permission to run an Amazon SageMaker training job with the Amazon SageMaker CreateTrainingJob API operation, you include the sagemaker:CreateTrainingJob action in their policy. Policy statements must include either an Action or NotAction element. Amazon SageMaker 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": [ "sagemaker:action1", "sagemaker: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": "sagemaker:Describe*"

To see a list of Amazon SageMaker actions, see Actions Defined by Amazon SageMaker in the IAM User Guide.

Resources

Amazon SageMaker does not support specifying resource ARNs in a policy.

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, 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, AWS evaluates them using a logical AND operation. If you specify multiple values for a single condition key, AWS 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 an IAM user permission to access a resource only if it is tagged with their IAM user name. For more information, see IAM Policy Elements: Variables and Tags in the IAM User Guide.

Amazon SageMaker 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 in the IAM User Guide.

Amazon SageMaker supports a number of service-specific condition keys that you can use for fine-grained access control for the following operations:

To see a list of Amazon SageMaker condition keys, see Condition Keys for Amazon SageMaker in the IAM User Guide. To learn with which actions and resources you can use a condition key, see Actions Defined by Amazon SageMaker.

For examples of using Amazon SageMaker condition keys, see the following:

Examples

To view examples of Amazon SageMaker identity-based policies, see Amazon SageMaker Identity-Based Policy Examples.

Amazon SageMaker Resource-Based Policies

Amazon SageMaker does not support resource-based policies.

Authorization Based on Amazon SageMaker Tags

You can attach tags to Amazon SageMaker resources or pass tags in a request to Amazon SageMaker. To control access based on tags, you provide tag information in the condition element of a policy using the sagemaker:ResourceTag/key-name, aws:RequestTag/key-name, or aws:TagKeys condition keys. For more information about tagging Amazon SageMaker resources, see Control Access to Amazon SageMaker Resources by Using Tags.

To view an example identity-based policy for limiting access to a resource based on the tags on that resource, see Control Access to Amazon SageMaker Resources by Using Tags.

Amazon SageMaker IAM Roles

An IAM role is an entity within your AWS account that has specific permissions.

Using Temporary Credentials with Amazon SageMaker

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 AWS STS API operations such as AssumeRole or GetFederationToken.

Amazon SageMaker supports using temporary credentials.

Service-Linked Roles

Amazon SageMaker doesn't support service-linked roles.

Service Roles

This feature allows a service to assume a service role 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 SageMaker supports service roles.

Choosing an IAM Role in Amazon SageMaker

When you create a notebook instance, training job, hosted endpoint, or batch transform job resource in Amazon SageMaker, you must choose a role to allow Amazon SageMaker to access Amazon SageMaker on your behalf. If you have previously created a service role or service-linked role, then Amazon SageMaker provides you with a list of roles to choose from. It's important to choose a role that allows access to the AWS operations and resources you need. For more information, see Amazon SageMaker Roles .