mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #369] Multiple SFTP clients #190
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#190
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 @willembressers on GitHub (Mar 3, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/369
I've managed to setup the SFTP upload for me (ec2-user).
If I want to upload files, I connect to the instance (with filezilla), navigate to the
/mnt/bucketand upload a file to theuploadsfolder.This is fine (for me) but I want to give access to a third party to the specific (
/mnt/bucket/uploads) folder only, preferably without navigation and an *.ppk key, but with (username: password) credentials.Is this feasible? and if so how?
I'm quite new to FTP (regarding setting up the server).
Cheers
Willem
@RobbKistler commented on GitHub (Mar 4, 2016):
Hi Willem. It's feasible but this is more of a general Unix and EC2/S3 question. S3fs-fuse provides normal Unix user/group access control as long as you start it with the -oallow_other flag. You can create a Unix user in the instance with a password login, add the group to the user, and then give that group access. s3fs-fuse will always authenticate access to the bucket with the S3 access key you configure it with. It doesn't try to map Unix users to S3 IAM users, AFAIK.
@willembressers commented on GitHub (Mar 4, 2016):
Thanks Robb