- Newest
- Most votes
- Most comments
Hi,
Thanks for sharing more context to your question.
The new SageMaker Studio experience contains a default private space that only you can access and run in JupyterLab or Code Editor. This means that, by default, notebooks won't be shared across profiles/users under domain.
If want to keep having shared notebooks, you're still able to create a new space in SageMaker Studio Classic (previous experience), where content will be shared across all users in your domain.
More information of new Amazon SageMaker Studio spaces (private/shared) can be found here.
Let me know If I can give further support and have a nice weekend!
*If you find this useful and solves your question, please remember to accept anwer.
Hi TMoraru!
Let me recall How do I check what role my Amazon SageMaker Studio user uses, and how do I change this role? post on how can control users permissions.
To cover your question, under existing Amazon Sagemaker roles:
- Ensure users IAM permissions do not include StartNotebookInstance, to avoid runing an specific notebook (or explicitly deny).
- Check UpdateNotebookInstance, to control who can update notebook.
Hi,
Thanks for taking the time to answer! Unfortunately, I think I should have been a bit more clear in my original post. What I am interested in is specifically notebook files within the elastic file system, and not NotebookInstances. Unless I am mistaken, a NotebookInstance is not necessarily associated to just one notebook file, correct? What I am looking for is more along the lines of being able to start a NotebookInstance only for specific notebook files and not others.
It looks like the links you provided discuss permissions on running notebook instances or modifying instance settings, but OP was asking about setting permissions on running and editing specific Jupyter notebooks in SageMaker Studio, not notebook instances.
Thank you both for adding more context to question. Find on my new answer how can address this situation with the new SageMaker Studio.
Relevant content
- asked a month ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
I think this does answer part of my questions, namely "2. Restrict the same users/user profiles to only run specific notebooks". I can see how you can use private/shared spaces to contol which notebooks a user might have access to. However, I am not sure if that answers the part of the question about restricting who can modify said notebooks.