before, with the s3 mount we were relying on the access point used to provide the implementation that the authenticated user had authorization to access the data. now that we're using efs we have to implement that ourselves.
I think should be simply making a GET call to some RDM route in images/jupyterhub/msdlive-authenticator/msdlive_authenticator/auth.py,
when doing this remove code that makes boto3 calls to see if the dataset is public or not since that RDM get should suffice for both
before, with the s3 mount we were relying on the access point used to provide the implementation that the authenticated user had authorization to access the data. now that we're using efs we have to implement that ourselves.
I think should be simply making a GET call to some RDM route in images/jupyterhub/msdlive-authenticator/msdlive_authenticator/auth.py,
when doing this remove code that makes boto3 calls to see if the dataset is public or not since that RDM get should suffice for both