1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
Hi there!
The reason you're seeing this behaviour is the underlying EC2 instance that runs JupyterLab gets terminated when you stop the notebook instance.
You can utilise lifecycle configuration script which is a bash script that runs when the EC2 instance spins back up, in this script, you can re-install extensions so your environment can be set-up properly when you open JupyterLab.
Below links provide examples on how to achieve this:
https://docs.aws.amazon.com/sagemaker/latest/dg/notebook-lifecycle-config.html
답변함 2년 전
관련 콘텐츠
- AWS 공식업데이트됨 3달 전