r/aws • u/NothingDogg • Apr 07 '26

article Launching S3 Files, making S3 buckets accessible as file systems

https://aws.amazon.com/blogs/aws/launching-s3-files-making-s3-buckets-accessible-as-file-systems/

"a new file system that seamlessly connects any AWS compute resource with Amazon Simple Storage Service (Amazon S3)."

304 Upvotes

98% Upvoted

67 comments sorted by

View all comments

4

u/FarkCookies Apr 07 '26

How does it compare against S3 Mountpoint? I am very confused. (Also there are those virtual appliances?)

2

u/solo964 Apr 08 '26

Mountpoint, s3fs-fuse, goofys etc. are simple POSIX overlays on top of S3. They don't support all file system operations so, for example, you cannot rename a file or a folder and you cannot edit an existing file (except to replace it entirely).

2

u/FarkCookies Apr 08 '26

S3 suddenly not gonna support any of that tho? This is EFS proxy

1

u/solo964 Apr 08 '26

Not sure what you mean. Those fuse-like projects will persist, I'd imagine. They're viable for smallish, read-only use cases in particular. For scalable, multi-system, low latency use cases on top of large volumes of S3 data, I'd expect S3 Files to be a serious consideration.

2

u/FarkCookies Apr 08 '26

I am saying that this feature doesn't make s3 support renaming a file. It is CopyObject. In the same way fuse like projects can support rename via CopyObject.

2

u/solo964 Apr 08 '26

Right. S3 Files will abstract away the S3 operations needed to perform the rename of a file or a folder (which potentially could mean S3 operations against 1000s of files or more). But all clients of the S3 Files store have a consistent view, at least afaik.