Amazon SageMaker Studio spaces - Amazon SageMaker
Access spaces
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon SageMaker Studio spaces

Important

Custom IAM policies that allow Amazon SageMaker Studio or Amazon SageMaker Studio Classic to create Amazon SageMaker resources must also grant permissions to add tags to those resources. The permission to add tags to resources is required because Studio and Studio Classic automatically tag any resources they create. If an IAM policy allows Studio and Studio Classic to create resources but does not allow tagging, "AccessDenied" errors can occur when trying to create resources. For more information, see Provide Permissions for Tagging SageMaker Resources.

Amazon Managed Policies for Amazon SageMaker that give permissions to create SageMaker resources already include permissions to add tags while creating those resources.

Important

As of November 30, 2023, the previous Amazon SageMaker Studio experience is now named Amazon SageMaker Studio Classic. The following section is specific to using the updated Studio experience. For information about using the Studio Classic application, see Amazon SageMaker Studio Classic.

Spaces are used to manage the storage and resource needs of some Amazon SageMaker Studio applications. Each space has a 1:1 relationship with an instance of an application. Every supported application that is created gets its own space. The following applications in Studio run on spaces:

A space is composed of the following resources:

  • A storage volume.

    • For Studio Classic, the space is connected to the shared Amazon Elastic File System (Amazon EFS) volume for the domain.

    • For other applications, a distinct Amazon Elastic Block Store (Amazon EBS) volume is attached to the space. All applications are given their own Amazon EBS volume. Applications do not have access to the Amazon EBS volume of other applications. For more information about Amazon EBS volumes, see Amazon Elastic Block Store (Amazon EBS).

  • The application type of the space.

  • The image that the application is based on.

Spaces can be either private or shared:

  • Private: Private spaces are scoped to a single user in a domain. Private spaces cannot be shared with other users. All applications that support spaces also support private spaces.

  • Shared: Shared spaces are accessible by all users in the domain. For more information about shared spaces, see Collaborate with shared spaces.

Spaces can be created in domains that use either Amazon IAM Identity Center or Amazon Identity and Access Management (IAM) authentication. The following sections give general information about how to access spaces. For specific information about creating and accessing a space, see the documentation for the respective application type of the space that you're creating.

For information about viewing, stopping, or deleting your applications, instances, or spaces, see Delete or stop your Studio running instances, applications, and spaces.

Access spaces

The following sections show how to access the list of spaces associated with the user profile in the domain. 

To access spaces from the Amazon SageMaker console

  1. Open the Amazon SageMaker console at https://console.amazonaws.cn/sagemaker/.

  2. Under Admin configurations, choose Domains.

  3. From the list of domains, select the domain that contains the spaces.

  4. On the Domain details page, select the Space management tab. For more information about managing spaces, see Collaborate with shared spaces.

  5. From the list of spaces for that domain, select the space to launch.

  6. Choose Launch Studio for the space that you want to launch.

Follow these steps to access spaces from Studio for a specific application type.

To access spaces from Studio

  1. Open Studio by following the steps in Launch Amazon SageMaker Studio.

  2. Select the application type with spaces that you want to access.

The following sections show how to access a space from the Amazon Command Line Interface (Amazon CLI). The procedures are for domains that use Amazon Identity and Access Management (IAM) or Amazon IAM Identity Center authentication.

IAM authentication

The following procedure outlines generally how to access a space using IAM authentication from the Amazon CLI.

  1. Create a presigned domain URL specifying the name of the space that you want to access.

    aws \
    --region region \
    sagemaker \
    create-presigned-domain-url \
    --domain-id domain-id \
    --user-profile-name user-profile-name \
    --space-name space-name

  2. Navigate to the URL.

Accessing a space in IAM Identity Center authentication

The following procedure outlines how to access a space using IAM Identity Center authentication from the Amazon CLI.

  1. Use the following command to return the URL associated with the space.

    aws \
    --region region \
    sagemaker \
    describe-space \
    --domain-id domain-id \
    --space-name space-name

  2. Append the respective redirect parameter for the application type to the URL to be federated through IAM Identity Center. For more information about the redirect parameters, see describe-space.

  3. Navigate to the URL to be federated through IAM Identity Center.