Jupyterhub sharing notebooks between users in Elastic Kubernetes Service

[manics]

EFS is the easiest to setup Setting up EFS storage on AWS — Zero to JupyterHub with Kubernetes documentation

Mounting S3 is theoretically possible, you can see an earlier discussion in

[Request for Implementation] Mapping notebook user identities to cloud provider identities

Many JupyterHub installations provide direct access to cloud resources like object storage (S3, GCS), cloud databases (RDS, Google Cloud SQL, etc) or bespoke cloud-provider specific things (BigQuery, Athena, Spanner, etc). Cloud providers have their own notion of identity (AWS IAM, Google’s Service accounts, etc), and access to cloud resources is granted on the basis of cloud provider identity. So, for access control & auditing purposes, it is important to attach a cloud provider identity to the…

but you’ll need to do some development work

• Jupyter notebook/lab can use S3 as a ContentsManager: GitHub - danielfrg/s3contents: Jupyter Notebooks in S3 - Jupyter Contents Manager implementation
• To setup per-user S3 permissions you’ll need to implement some authenticator or spawner hooks to create the IAM role, and to set the service account corresponding to the IAM role.