# Shut Down and Update Amazon SageMaker Studio Classic and Apps Shut Down and Update **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](studio-updated.md). Studio Classic is still maintained for existing workloads but is no longer available for onboarding. You can only stop or delete existing Studio Classic applications and cannot create new ones. We recommend that you [migrate your workload to the new Studio experience](studio-updated-migrate.md). The following topics show how to shut down and update SageMaker Studio Classic and Studio Classic Apps. Studio Classic provides a notification icon (![\[Red circle icon with white exclamation mark, indicating an alert or warning.\]](http://docs.aws.amazon.com/sagemaker/latest/dg/images/icons/Notification.png)) in the upper-right corner of the Studio Classic UI. This notification icon displays the number of unread notices. To read the notices, select the icon. Studio Classic provides two types of notifications: + Upgrade – Displayed when Studio Classic or one of the Studio Classic apps have released a new version. To update Studio Classic, see [Shut Down and Update Amazon SageMaker Studio Classic](studio-tasks-update-studio.md). To update Studio Classic apps, see [Shut Down and Update Amazon SageMaker Studio Classic Apps](studio-tasks-update-apps.md). + Information – Displayed for new features and other information. To reset the notification icon, you must select the link in each notice. Read notifications may still display in the icon. This does not indicate that updates are still needed after you have updated Studio Classic and Studio Classic Apps. To learn how to update [Amazon SageMaker Data Wrangler](https://docs.aws.amazon.com/sagemaker/latest/dg/data-wrangler.html), see [Shut Down and Update Amazon SageMaker Studio Classic Apps](studio-tasks-update-apps.md). To ensure that you have the most recent software updates, update Amazon SageMaker Studio Classic and your Studio Classic apps using the methods outlined in the following topics. **Topics** + [ # Shut Down and Update Amazon SageMaker Studio Classic ](studio-tasks-update-studio.md) + [ # Shut Down and Update Amazon SageMaker Studio Classic Apps ](studio-tasks-update-apps.md) # Shut Down and Update Amazon SageMaker Studio Classic Shut Down and Update **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 AI resources](security_iam_id-based-policy-examples.md#grant-tagging-permissions). [AWS managed policies for Amazon SageMaker AI](security-iam-awsmanpol.md) 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](studio-updated.md). Studio Classic is still maintained for existing workloads but is no longer available for onboarding. You can only stop or delete existing Studio Classic applications and cannot create new ones. We recommend that you [migrate your workload to the new Studio experience](studio-updated-migrate.md). To update Amazon SageMaker Studio Classic to the latest release, you must shut down the JupyterServer app. You can shut down the JupyterServer app from the SageMaker AI console, from Amazon SageMaker Studio or from within Studio Classic. After the JupyterServer app is shut down, you must reopen Studio Classic through the SageMaker AI console or from Studio which creates a new version of the JupyterServer app. You cannot delete the JupyterServer application while the Studio Classic UI is still open in the browser. If you delete the JupyterServer application while the Studio Classic UI is still open in the browser, SageMaker AI automatically re-creates the JupyterServer application. Any unsaved notebook information is lost in the process. The user data in the Amazon EFS volume isn't impacted. Some of the services within Studio Classic, like Data Wrangler, run on their own app. To update these services you must delete the app for that service. To learn more, see [Shut Down and Update Amazon SageMaker Studio Classic Apps](studio-tasks-update-apps.md). **Note** A JupyterServer app is associated with a single Studio Classic user. When you update the app for one user it doesn't affect other users. The following page shows how to update the JupyterServer App from the SageMaker AI console, from Studio, or from inside Studio Classic. ## Shut down and update from the SageMaker AI console 1. Navigate to [https://console.aws.amazon.com/sagemaker/](https://console.aws.amazon.com/sagemaker/). 1. On the left navigation pane, choose **Admin configurations**. 1. Under **Admin configurations**, choose **domains**. 1. Select the domain that includes the Studio Classic application that you want to update. 1. Under **User profiles**, select your user name. 1. Under **Apps**, in the row displaying **JupyterServer**, choose **Action**, then choose **Delete**. 1. Choose **Yes, delete app**. 1. Type **delete** in the confirmation box. 1. Choose **Delete**. 1. After the app has been deleted, launch a new Studio Classic app to get the latest version. ## Shut down and update from Studio 1. Navigate to Studio following the steps in [Launch Amazon SageMaker Studio](studio-updated-launch.md). 1. From the Studio UI, find the applications pane on the left side. 1. From the applications pane, select **Studio Classic**. 1. From the Studio Classic landing page, select the Studio Classic instance to stop. 1. Choose **Stop**. 1. After the app has been stopped, select **Run** to use the latest version. ## Shut down and update from inside Studio Classic 1. Launch Studio Classic. 1. On the top menu, choose **File** then **Shut Down**. 1. Choose one of the following options: + **Shutdown Server** – Shuts down the JupyterServer app. Terminal sessions, kernel sessions, SageMaker images, and instances aren't shut down. These resources continue to accrue charges. + **Shutdown All** – Shuts down all apps, terminal sessions, kernel sessions, SageMaker images, and instances. These resources no longer accrue charges. 1. Close the window. 1. After the app has been deleted, launch a new Studio Classic app to use the latest version. # Shut Down and Update Amazon SageMaker Studio Classic Apps Shut Down and Update Apps **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 AI resources](security_iam_id-based-policy-examples.md#grant-tagging-permissions). [AWS managed policies for Amazon SageMaker AI](security-iam-awsmanpol.md) 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](studio-updated.md). Studio Classic is still maintained for existing workloads but is no longer available for onboarding. You can only stop or delete existing Studio Classic applications and cannot create new ones. We recommend that you [migrate your workload to the new Studio experience](studio-updated-migrate.md). To update an Amazon SageMaker Studio Classic app to the latest release, you must first shut down the corresponding KernelGateway app from the SageMaker AI console. After the KernelGateway app is shut down, you must reopen it through SageMaker Studio Classic by running a new kernel. The kernel automatically updates. Any unsaved notebook information is lost in the process. The user data in the Amazon EFS volume isn't impacted. After an application has been shut down for 24 hours, SageMaker AI deletes all metadata for the application. To be considered an update and retain application metadata, applications must be restarted within 24 hours after the previous application has been shut down. After this time window, creation of an application is considered a new application rather than an update of the previous application. **Note** A KernelGateway app is associated with a single Studio Classic user. When you update the app for one user it doesn't effect other users. **To update the KernelGateway app** 1. Navigate to [https://console.aws.amazon.com/sagemaker/](https://console.aws.amazon.com/sagemaker/). 1. On the left navigation pane, choose **Admin configurations**. 1. Under **Admin configurations**, choose **domains**. 1. Select the domain that includes the application that you want to update. 1. Under **User profiles**, select your user name. 1. Under **Apps**, in the row displaying the **App name**, choose **Action**, then choose **Delete** To update Data Wrangler, delete the app that starts with **sagemaker-data-wrang**. 1. Choose **Yes, delete app**. 1. Type **delete** in the confirmation box. 1. Choose **Delete**. 1. After the app has been deleted, launch a new kernel from within Studio Classic to use the latest version.