mountpoint-s3

A more solid (especially when it comes to caching) solution would be appreciated. I thought that would be their https://github.com/awslabs/mountpoint-s3 . But no mention about this one either. S3 files does have the advantage of having a "shared" cache via EFS, but then that would probably also make the cache slower.

AWS has this "mountpoint for s3" thingy https://github.com/awslabs/mountpoint-s3

How does this compare to https://github.com/awslabs/mountpoint-s3 ?

... or does "S3 file system" mean https://github.com/awslabs/mountpoint-s3 - a Rust project by AWS Labs that provides "a simple, high-throughput file client for mounting an Amazon S3 bucket as a local file system" ?

Looks like support for S3 Express was merged in with version 1.30 just a few hours ago https://github.com/awslabs/mountpoint-s3/pull/642

mountpoint-s3 is AWS’ first party solution for mounting s3 buckets as file systems: https://github.com/awslabs/mountpoint-s3 Haven’t used it but it looks cool, if a bit immature.

There's some really confusing use of unsafe going on. For example I'm not sure what they're doing here: https://github.com/awslabs/mountpoint-s3/blob/main/mountpoin...

This is really interesting and something I've been thinking about for a while now. The SEMANTICS[1] doc details what is and isn't supported from a POSIX filesystem API perspective, and this stands out: Write operations (write, writev, pwrite, pwritev) are not currently supported. In the future, Mountpoint for Amazon S3 will support sequential writes, but with some limitations: Writes will only be supported to new files, and must be done sequentially. Modifying existing files will not be supported. Truncation will not be supported. The sequential requirement for writes is the part that I've been mulling over whether or not it's actually required in S3. Last year I discovered that S3 can do transactional I/O via multipart upload[2] operations combined with the CopyObject[3] operation. This should, in theory, allow for o