1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 6 Monaten
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren