- Le plus récent
- Le plus de votes
- La plupart des commentaires
HichamZouarhi@,
Considering you are able to connect to the server and authenticate, the overall Lambda IDP configuration seems to be working. In regards to your error, I believe you need to provide the EFS id within the HomeDirectory
to be able to access. Right now with HomeDirectory: /
, it assumes root of EFS and probably attempts to list available EFS resources. Unless you have permissions for the same, the error would be expected behavior.
Could you update the HomeDirectory to the EFS resource that you are trying to access? Example: HomeDirectory: /fs-000000/user
. Further, you need to ensure that the folder you are trying to access is accessible using the POSIX configuration you specified: (1001, 1001)
in your case.
References:
Let me know if you have follow up questions.
-- Sagar
Thanks Sagar, I thought at first that my SFTP would be linked directly to the efs for which I gave permission on the policy. by adding the file system id to HomeDirectory it worked. Have a nice day :)
Contenus pertinents
- demandé il y a un an
- demandé il y a 6 mois
- demandé il y a 2 ans
- AWS OFFICIELA mis à jour il y a 4 ans
- AWS OFFICIELA mis à jour il y a un mois
Hello Hicham, Sagar,
Could you please attach the Lambda code and secret manager POSIX format that you are using? I am trying to deploy the same configuration but it always returns the error 'Missing POSIX profile' even though secrets manager has a PosixProfile.
Regards, Nitesh D