Issue with s3fs, fails with restrictive IAM policy and mounting a path
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
s3fs-fuse (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I just copy/paste that issue from Github. I test on my side the PR and it works fine.
"""
We have a setup that mounts a path under an S3 bucket. The IAM user in question is configured with the minimum necessary permissions, it is restricted to listing and reading objects only under its path prefix in the bucket. It does not have permission to ListBucket on the root of the bucket.
While upgrading from Ubuntu 20.04 to 22.04, s3fs upgraded from 1.86 to 1.90 and experienced a regression in functionality. It worked in 1.86 and fails in 1.90 without any configuration change on our part.
"""
That issue is from https:/
The creator of s3fs rolled back a previous change done on the version 1.90 of s3fs, the version provided in Ubuntu 22.04.
Changed in s3fs-fuse (Ubuntu): | |
status: | New → Fix Committed |
The test was done with the last commit, ie `16bc449`
``` com/s3fs- fuse/s3fs- fuse-latest/ src/s3fs --version /gnu.org/ licenses/ gpl.html>
# ~/github.
Amazon Simple Storage Service File System V1.91 (commit:16bc449) with OpenSSL
Copyright (C) 2010 Randy Rizun <email address hidden>
License GPL2: GNU GPL version 2 <https:/
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
```