mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #128] Getting Error "s3fs: could not determine how to establish security credentials" #81
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#81
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @qspencer on GitHub (Feb 23, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/128
set_moutpoint_attribute(3482): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755)
s3fs: could not determine how to establish security credentials
Any solutions or suggestions of things to try would be greatly appreciated!
@ggtakec commented on GitHub (Mar 3, 2015):
"s3fs: could not determine how to establish security credentials" message means that s3fs could not find any credential(/etc/passed-s3fs, $HOME/.passwd-s3fs etc...).
It seems that your procedure is no problem, but you got this message.
So I think that HOME environment is something wrong as possible.
If you can, you try to copy your $HOME/.passwd-s3fs to /etc/passwd-s3fs and cheek to run s3fs.
Regards,
@qspencer commented on GitHub (Mar 3, 2015):
thank you, I tried what you suggested and it worked!
@jcomeauictx commented on GitHub (Jan 29, 2017):
if you ran the
s3fscommand withsudo, but had the.passwd-s3fsfile in your own account's$HOME, that could account for why it failed, and also why it mentionedPROC(uid=0, gid=0)in the output. it may have been looking for the file in root's home directory.@railsfans commented on GitHub (Jul 22, 2017):
把/etc/passwd-ossfs的权限改成你要启动的普通用户就行了。
@stormm2138 commented on GitHub (Feb 22, 2018):
Note that for me using fstab didn't auto-remount on reboot, likely due to networking services not being enabled at the time of the boot mount, so I'm creating a service to boot after networking services are enabled per https://github.com/s3fs-fuse/s3fs-fuse/issues/412
@blurayne commented on GitHub (Aug 31, 2018):
You could use a bash wrapper script to support a custom credential parameter using AWS CLI ENV variables - see here:
http://blog.evolution515.net/2018/08/31/autofs-indirect-user-automounter-for-aws-s3-using-either-s3fs-or-goofyfs/
@treii28 commented on GitHub (Mar 17, 2022):
my EC2 should have S3 permissions in it's default assumed role. is there any way to avoid this error when using such authentication?