YAS3FS (Yet Another S3-backed File System) is a Filesystem in Userspace (FUSE) interface to Amazon S3. It was inspired by s3fs but rewritten from scratch to implement a distributed cache synchronized by Amazon SNS notifications. A web console is provided to easily monitor the nodes of a cluster.
I am happily using yas3fs with the suggested IAM policy, but it stopped working when I enabled versioning on a bucket. In debug mode I could see log entries such as:
I suspect this may be related to https://github.com/boto/boto/issues/3219 and that the IAM policy needs to include "s3:GetObjectVersion" though I fixed this for the time being by allowing all permissions on my bucket. If I manage to determine the exact permissions required I will update this issue and raise a PR.
Re-tested this today with tighter permissions and it seems s3:GetObjectVersion is the only additional permission needed for yas3fs to work with versioned buckets.
I am happily using yas3fs with the suggested IAM policy, but it stopped working when I enabled versioning on a bucket. In debug mode I could see log entries such as:
I suspect this may be related to https://github.com/boto/boto/issues/3219 and that the IAM policy needs to include
"s3:GetObjectVersion"
though I fixed this for the time being by allowing all permissions on my bucket. If I manage to determine the exact permissions required I will update this issue and raise a PR.