- Más nuevo
- Más votos
- Más comentarios
Hi,
Did you follow the guidance re. Custom EFS volume for SageMaker Studio: https://docs.aws.amazon.com/sagemaker/latest/dg/domain-custom-efs.html
I twas announced a few months ago; https://aws.amazon.com/about-aws/whats-new/2023/11/amazon-eds-volume-jupyterlab-codeeditor-amazon-sagemaker-studio/
Additionally, did you set up your EFS for write access according to: https://repost.aws/knowledge-center/efs-enable-read-write-access ?
Best,
Didier
Have you read my question at all?
I going to use SageMaker Studio with an existing custom file system (EFS). I followed the instructions comprised in: https://docs.aws.amazon.com/sagemaker/latest/dg/domain-custom-efs.html
Far from expert here, but are you sure you are writing with the correct user profile?
"When you onboard to Studio, SageMaker creates an Amazon Elastic File System (EFS) volume for your domain that is shared by all Studio users in the domain. Each user gets their own private home directory on the EFS volume. This home directory is used to store the user's notebooks, Git repositories, and other data. To prevent other users in the domain from accessing the user's data, SageMaker creates a globally unique user ID for the user's profile and applies it as a POSIX user/group ID for the user’s home directory."
did you try to attach the policy with the sagemaker execution role in place of user role?
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace un año
Hello, did any solution work with you because i'm currently facing the same problem?