Amazon SageMaker
Developer Guide

Overview of Managing Access Permissions to Your Amazon SageMaker Resources

Every AWS resource is owned by an AWS account, and permissions to create or access a resource are governed by permissions policies. An account administrator can attach permissions policies to IAM identities (that is, users, groups, and roles). Some services (such as AWS Lambda) also support attaching permissions policies to resources.


An account administrator (or administrator user) is a user with administrator privileges. For more information, see IAM Best Practices in the IAM User Guide.

When granting permissions, you decide who is getting the permissions, the resources they get permissions for, and the specific actions that you want to allow on those resources.

Amazon SageMaker Resources and Operations

In Amazon SageMaker, the primary resource is a notebook instance. Amazon SageMaker also supports additional resource types: training jobs, models, endpoint configurations, endpoints, and tags. These additional resources are referred to as subresources. In a policy, you use an Amazon Resource Name (ARN) to identify the resource that the policy applies to.

Except for tags, these resources and subresources have unique ARNs associated with them, as shown in the following table. Tags use the ARN of the resource that they are modifying. For example, when used on a model, the AddTag action uses the same ARN as the model resource.

Resource Type ARN Format
Batch Transform Job arn:aws:sagemaker:region:account-id:transform-job/transformJobName


Endpoint Config


Hyperparemeter Tuning Job arn:aws:sagemaker:region:account-id:hyper-parameter-tuning-job/hyperParameterTuningJobName
Model arn:aws:sagemaker:region:account-id:model/modelName
Notebook Instance arn:aws:sagemaker:region:account-id:notebook-instance/notebookInstanceName
Notebook Instance Lifecycle Configuration arn:aws:sagemaker:region:account-id:notebook-instance-lifecycle-config/notebookInstanceLifecycleConfigName
Training Job arn:aws:sagemaker:region:account-id:training-job/trainingJobName

Amazon SageMaker provides a set of operations to work with Amazon SageMaker resources. For a list of available operations, see the Amazon SageMaker API Reference.

Understanding Resource Ownership

The AWS account owns the resources that are created in the account, regardless of who created the resources. Specifically, the resource owner is the AWS account of the principal entity (that is, the root account, an IAM user, or an IAM role) that authenticates the resource creation request. The following examples illustrate how this works:

  • If you use the root account credentials of your AWS account to create a notebook instance, your AWS account is the owner of the resource (in Amazon SageMaker, the resource is a notebook instance).

  • If you create an IAM user in your AWS account and grant permissions to create a notebook instance to that user, the user can create a notebook instance. However, your AWS account, to which the user belongs, owns the notebook instance resource.

  • If you create an IAM role in your AWS account with permissions to create a notebook instance, anyone who can assume the role can create a notebook instance. Your AWS account, to which the user belongs, owns the notebook instance resource.

Managing Access to Resources

A permissions policy describes who has access to what. The following section explains the options for creating permissions policies.


This section discusses using IAM in the context of Amazon SageMaker. It doesn't provide detailed information about the IAM service. For complete IAM documentation, see What Is IAM? in the IAM User Guide. For information about IAM policy syntax and descriptions, see AWS IAM Policy Reference in the IAM User Guide.

Permissions policies attached to an IAM identity are referred to as identity-based policies (IAM polices). Permissions policies attached to a resource are referred to as resource-based policies. Amazon SageMaker supports only identity-based permissions policies.

Identity-Based Policies (IAM Policies)

You can attach permissions policies to IAM identities. For example, you can do the following:

  • Attach a permissions policy to a user or a group in your account – To grant a user permissions to create a Amazon SageMaker resource, such as a notebook instance, you can attach a permissions policy to a user or to a group that the user belongs to.

  • Attach a permissions policy to a role (grant cross-account permissions) – You can attach an identity-based permissions policy to an IAM role to grant cross-account permissions. For example, the administrator in account A can create a role to grant cross-account permissions to another AWS account (for example, account B) or an AWS service as follows:

    1. Account A administrator creates an IAM role and attaches a permissions policy to the role that grants permissions on resources in account A.

    2. Account A administrator attaches a trust policy to the role identifying account B as the principal who can assume the role.

    3. Account B administrator can then delegate permissions to assume the role to any users in account B. Doing this allows users in account B to create or access resources in account A. The principal in the trust policy can also be an AWS service principal if you want to grant an AWS service permissions to assume the role.

    For more information about using IAM to delegate permissions, see Access Management in the IAM User Guide.

Some of the Amazon SageMaker actions (for example, CreateTrainingJob) require the user to pass an IAM role to Amazon SageMaker so that the service can assume that role and its permissions. To pass a role (and its permissions) to an AWS service, a user must have permissions to pass the role to the service. To allow a user to pass a role to an AWS service, you must grant permission for the iam:PassRole action. For more information, see Granting a User Permissions to Pass a Role to an AWS Service in the IAM User Guide.

The following is an example permission policy. You attach it to an IAM user.

{ "Version": "2012-10-17", "Statement": [ { "Action": [ "sagemaker:CreateModel" ], "Effect": "Allow", "Resource": "arn:aws:sagemaker:region:account-id:model/modelName" }, { "Action": "iam:PassRole", "Effect": "Allow", "Resource": [ "arn:aws:iam::account-id:role/role-name" ] } ] }

For more information about using identity-based policies with Amazon SageMaker, see Using Identity-based Policies (IAM Policies) for Amazon SageMaker. For more information about users, groups, roles, and permissions, see Identities (Users, Groups, and Roles) in the IAM User Guide.

Resource-Based Policies

Other services, such as Amazon S3, also support resource-based permissions policies. For example, you can attach a policy to an S3 bucket to manage access permissions to that bucket. Amazon SageMaker doesn't support resource-based policies.

Specifying Policy Elements: Resources, Actions, Effects, and Principals

For each Amazon SageMaker resource, the service defines a set of API operations. To grant permissions for these API operations, Amazon SageMaker defines a set of actions that you can specify in a policy. For example, for the Amazon SageMaker notebook instance resource, the following actions are defined: CreateNotebookInstance, DeleteNotebookInstance, and DescribeNotebookInstance. Some API operations can require permissions for more than one action in order to perform the API operation. For more information about resources and API operations, see Amazon SageMaker Resources and Operations and API Reference.

The following are the most basic policy elements:

  • Resource – You use an Amazon Resource Name (ARN) to identify the resource that the identity-based policy applies to. For more information, see Amazon SageMaker Resources and Operations.

  • Action – You use action keywords to identify resource operations that you want to allow or deny. For example, you can use sagemaker:CreateModel to add a model to the notebook instance.

  • Effect – You specify the effect, either allow or deny, when the user requests the specific action. If you don't explicitly grant access to (allow) a resource, access is implicitly denied. You can also explicitly deny access to a resource, which you might do to make sure that a user cannot access it, even if a different policy grants access.

  • Principal – In identity-based policies (IAM policies), the user that the policy is attached to is the implicit principal. Amazon SageMaker doesn't support resource-based policies.

To learn more about IAM policy syntax and to read policy descriptions, see AWS IAM Policy Reference in the IAM User Guide.

For a showing all of the Amazon SageMaker API operations and the resources that they apply to, see Amazon SageMaker API Permissions: Actions, Permissions, and Resources Reference.

Specifying Conditions in a Policy

When you grant permissions, you can use the IAM policy language to specify the conditions under which a policy should take effect. For example, you might want a policy to be applied only after a specific date. For more information about specifying conditions in a policy language, see Conditions in the IAM User Guide.

To express conditions, you use predefined condition keys. There are no condition keys specific to Amazon SageMaker. However, there are AWS-wide condition keys that you can use as appropriate. For an example of AWS-wide keys used in an Amazon SageMaker permissions policy, see Permissions Required to Use the Amazon SageMaker Console. For a complete list of AWS-wide keys, see Available Keys for Conditions in the IAM User Guide.