Set defaults from the SageMaker console
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 Studio Classic application. For information about using the updated Studio experience, see Amazon SageMaker Studio.
You can set default lifecycle configuration scripts from the SageMaker console for the following resources.
-
Domains
-
User profiles
You cannot set default lifecycle configuration scripts for shared spaces from the SageMaker console. For information about setting defaults for shared spaces, see Set defaults from the Amazon CLI.
The following sections outline how to set default lifecycle configuration scripts from the SageMaker console.
Topics
Prerequisites
Before you begin, complete the following prerequisites:
-
Onboard to SageMaker domain by following the steps in Amazon SageMaker domain overview.
-
Create a lifecycle configuration following the steps in Create and associate a lifecycle configuration.
Set a default lifecycle configuration for a domain
The following procedure shows how to set a default lifecycle configuration for a domain from the SageMaker console.
-
Open the Amazon SageMaker console at https://console.amazonaws.cn/sagemaker/
. -
From the list of domains, select the name of the domain to set the default lifecycle configuration for.
-
From the Domain details page, choose the Environment tab.
-
Under Lifecycle configurations for personal Studio apps, select the lifecycle configuration that you want to set as the default for the domain. You can set distinct defaults for JupyterServer and KernelGateway applications.
-
Choose Set as default. This opens a pop up window that lists the current defaults for JupyterServer and KernelGateway applications.
-
Choose Set as default to set the lifecycle configuration as the default for its respective application type.
Set a default lifecycle configuration for a user profile
The following procedure shows how to set a default lifecycle configuration for a user profile from the SageMaker console.
-
Open the Amazon SageMaker console at https://console.amazonaws.cn/sagemaker/
. -
From the list of domains, select the name of the domain that contains the user profile that you want to set the default lifecycle configuration for.
-
From the Domain details page, choose the User profiles tab.
-
Select the name of the user profile to set the default lifecycle configuration for. This opens a User Details page.
-
From the User Details page, choose Edit. This opens an Edit user profile page.
-
From the Edit user profile page, choose Step 2 Studio settings.
-
Under Lifecycle configurations attached to user, select the lifecycle configuration that you want to set as the default for the user profile. You can set distinct defaults for JupyterServer and KernelGateway applications.
-
Choose Set as default. This opens a pop up window that lists the current defaults for JupyterServer and KernelGateway applications.
-
Choose Set as default to set the lifecycle configuration as the default for its respective application type.