I'm pretty sure I'm missing something painfully obvious, but I can't figure out what. (Yes, I know, possible security issues, we'll worry about those once we have it working and before it's deployed into production) Relevant fstab line: dvoijen /s3mounts/dvoijen fuse.s3fs _netdev,noauto,url= 0 0

I've tried setting the umask in fstab to 000, but it's had no effect. Samba.log isn't terribly more informative, merely saying chdir (/s3mounts/dvoijen) failed, reason: Permission denied However, when I try to make a samba share out of the s3fs mount point, windows reports a 'permission denied'.

We tried to work around the problem by creating a samba 'proxy' that mounts the S3 storage devices, then shares that mount to the windows network.īoth samba and s3fs seem to be configured correctly I can mount the S3 storage points, and I can turn directories into samba shares. However, not all of our customers have the ability to work with S3 storage due to old hardware/software. At work we've recently deployed several S3 storage servers.

Cyberduck s3 bucket path