mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #530] s3fs on mac #298
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#298
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 @zijwang on GitHub (Feb 9, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/530
Version of s3fs being used (s3fs --version)
_example: 1.80
Version of fuse being used (pkg-config --modversion fuse)
_example: 2.7.3
System information (uname -a)
_command result: 16.4.0 Darwin Kernel Version 16.4.0 Macbook Pro
Details about issue
I've a s3 bucket and I'm used to use it on ec2. Now I want to mount this bucket onto my mac. The mounting process is good and I can read all the files. However, it looks like I do not have the permissions to write existed files. Any thoughts to fix that?
@blip-lorist commented on GitHub (Feb 11, 2017):
Does the user policy for the AWS credentials you used during s3fs setup include the PutObject action? You can check by visiting IAM in AWS console, then looking at the policies on your user account. https://aws.amazon.com/blogs/security/writing-iam-policies-how-to-grant-access-to-an-amazon-s3-bucket/
@ggtakec commented on GitHub (Mar 19, 2017):
@zijwang
If your objects do not have any meta header(x-amz-meta-*), you can see the object like following.
s3fs needs meta header for all object, but if there is no meta information for the obejct, it looks like no permission.
To solve this, you can set meta header to all object.
Or you can use umask/mp_umask/uid/gid option for s3fs.
Regards,
@ggtakec commented on GitHub (Mar 30, 2019):
We kept this issue open for a long time.
I will close this, but if the problem persists, please reopen or post a new issue.