- Newest
- Most votes
- Most comments
To my knowledge, this is not possible. With the split of SageMaker AI Studio from SageMaker Studio Classic, the offered container images were consolidated down from the previous set (Base, Data Science, per-framework DL images) - to the single, open SageMaker Distribution that includes multiple DL frameworks in one. The new AI Studio JupyterLab spaces cannot use the old SMStudio Classic images directly.
The good news is, as noted here new-style SageMaker AI JupyterLab spaces on recent versions of the SM Distribution image should also be able to connect to EMR clusters.
However, if you're migrating SageMaker versions anyway at the moment, and connecting to Spark/EMR clusters and big data sources is of interest to you - I might also suggest this is a good time to explore SageMaker Unified Studio (preview)? SMUS makes use of the AI Studio JupyterLab spaces under the hood, but tries to bring tighter integration between the previously-separate AI (SageMaker) and analytics (like EMR) service portfolios. For example there's nice built-in capabilities for SQL analytics that go a bit beyond what the SageMaker Classic+EMR integration offered.
I am logged in as Administrator, so this is not a permission issue.
In the "Supported images and kernels to connect to an Amazon EMR cluster from Studio or Studio Classic" section of https://docs.aws.amazon.com/sagemaker/latest/dg/studio-updated-spaces.html , Datascience 3.0 has been listed only under Studio classic.
When I try to create a new space in Studio -> JupyterLab, I don't see Datascience 3.0 listed as a choice. I only see the SageMaker Distribution image. How can I select Datascience 3 as the image in Studio -> JupyterLab -> JuperLab space?
answered a year ago
I apologize, but there seems to be a misunderstanding in your question. Based on the available information, SageMaker Studio and SageMaker Studio Classic are separate offerings, and the DataScience 3.0 image is still supported in SageMaker Studio.
For SageMaker Studio, which uses JupyterLab as its interface, the DataScience 3.0 image is still available and supported. This image comes pre-installed with the sagemaker-studio-analytics-extension and includes a Python 3 kernel. It's one of the images that allows connection to Amazon EMR clusters.
Regarding JupyterLab 4, it's important to note that JupyterLab versioning in SageMaker is separate from the image selection. JupyterLab 4 is the latest version available for SageMaker notebook instances, but it doesn't directly impact the availability of specific images like DataScience 3.0.
If you're not seeing the DataScience 3.0 image listed in your Studio environment, it may be due to your specific Studio configuration or permissions. You might want to check with your AWS administrator to ensure you have the necessary permissions to access all available images.
For the most up-to-date and accurate information about available images and kernels in your specific SageMaker Studio environment, I recommend checking your Studio interface directly or consulting with AWS support.
Sources
User guide - Amazon SageMaker AI
JupyterLab Versioning - Amazon SageMaker AI
JupyterLab versioning - Amazon SageMaker AI
answered a year ago
Relevant content
asked 2 years ago
asked 2 years ago
