Configuration JupyterLab in Virtual Environment

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

https://github.com/aws-samples/amazon-sagemaker-notebook-instance-lifecycle-config-samples/blob/master/scripts/install-lab-extension/on-start.sh