Spin up Jupyter notebooks at scale and enhance your productivity
summary
Demonstrates that Amazon SageMaker Studio runs JupyterLab-based notebooks at scale by launching per-notebook compute that users can switch without managing servers, using remote kernels backed by a shared EFS home so files persist across instances. Admins get IAM/SSO, VPC, end-to-end encryption, internet‑free mode and containerized SageMaker images for dependency distribution; users get quick defaults, GPU or CPU switching, terminal access co-located with kernels, and shareable notebook links. Notes that there are over 10 million public Jupyter notebooks on GitHub.
AI-written summary · about
chapters (7)
- 0:00Introduction to Jupyter
- 7:30Enterprise challenges with Jupyter
- 12:13Amazon SageMaker Studio overview
- 16:32Admin setup of SageMaker Studio
- 21:13End user experience in SageMaker
- 29:03Collaboration and sharing features
- 30:52Summary and conclusion
related talks
32mHow to use fully managed Jupyter notebooks in Amazon SageMaker
20mAWS On Air ft. Amazon SageMaker Studio Lab
34mMoving notebooks into the cloud: challenges and lessons learned
24mJupyter Notebooks for Ops
34mDeploying a Machine Learning System That Only Runs Locally
28mBuild a data studio in your notebook with jupyter-fs
37mJupyterLab
28mHosting Notebooks for 100,000 Users