mountpoint-s3 | Amazon Web Services Ecosystem Directory

Bot releases are visible (Hide)

mountpoint-s3 - mountpoint-s3 v1.6.0 Latest Release

Published by github-actions[bot] 6 months ago

New features

Mountpoint for Amazon S3 now supports specifying an AWS Key Management Service (AWS KMS) key for server-side encryption with KMS (SSE-KMS) when mounting an S3 bucket or prefix. (#839)

Breaking changes

No breaking changes.

Other changes

Mountpoint now retries S3 requests up to a total of 10 attempts (up from 4), which should make file operations more robust to transient failures or throttling. The maximum number of attempts can be overridden by setting the AWS_MAX_ATTEMPTS environment variable. (#830)
Fix an issue where Mountpoint could become unresponsive after opening too many files in write mode. (#832)
Add support for rewinddir by restarting readdir if offset is zero. (#825)

Binaries

x86_64

arm64

mountpoint-s3 - mountpoint-s3 v1.5.0

Published by github-actions[bot] 7 months ago

New features

When caching is enabled, Mountpoint also remembers when objects do not exist, in order to reduce repeated lookups. (#696)

Other changes

Cancel S3 requests when dropped. Addresses an issue where the prefetcher could keep streaming up to 2GB of data that would never be used. (#794)
Improve read throughput in more non-sequential access patterns by better accounting for the progress of in-flight prefetch requests. (#797)
Stop limiting the number of connections based on the number of known IPs when connecting to S3. Improves maximum throughput on S3 Express. (#796)

Binaries

x86_64

arm64

mountpoint-s3 - mountpoint-s3 v1.4.1

Published by github-actions[bot] 8 months ago

Other changes

Fix an issue where read file handles could be closed too early, leading to bad file descriptor errors on subsequent reads. As a consequence of this fix, opening an existing file to overwrite it immediately after closing a read file handle may occasionally fail with an "Operation not permitted" error. In such cases, Mountpoint logs will also report that the file is "not writable while being read". (#751)
File handles are no longer initialized lazily. Lazy initialization was introduced in version 1.4.0 but is reverted in this change. If upgrading from 1.4.0, you may see errors that were previously deferred until read/write now raised at open time. (#751)

Binaries

x86_64

arm64

mountpoint-s3 - mountpoint-s3 v1.4.0

Published by github-actions[bot] 9 months ago

New features

Allow file overwrites when mounting with --allow-overwrite option. The upload will start as soon as Mountpoint receives write request and cannot be aborted. Once it is started the file is guaranteed to be overwritten. (#487)

Breaking changes

No breaking changes.

Other changes

Update default network throughput values for newer EC2 instance types. (#702)
Improve error logging for various unsupported operations. (#699)
Fix a race condition where calling mknod and forget under the same directory could cause Mountpoint to hang indefinitely. (#711)

Binaries

x86_64

arm64

mountpoint-s3 - mountpoint-s3 v1.3.2

Published by github-actions[bot] 9 months ago

Breaking changes

No breaking changes.

Other changes

Log messages now include file names and S3 keys more consistently. (#665)
Successful mount message is now output to stdout for both foreground and background mode. (#668)
Added new metric tracking contiguous reads. This new metric may be used to help understand how much data is being read successfully using prefetching before needing to discard prefetched progress when seeking around the file. (#629)
Fix a race condition where FUSE read operations may have completed and subsequently sent back to the Kernel while locks were still being held on a file handle. If a FUSE release operation was executed while the file handle was still held by read, this would result in the file handle never being deallocated. (#691)

Binaries

x86_64

arm64

mountpoint-s3 - mountpoint-s3 v1.3.1

Published by github-actions[bot] 11 months ago

Breaking changes

No breaking changes.

Other changes

Fix an issue where Mountpoint could crash on launch when overriding the default part size with values that are not multiples of 1024. (#649)

Binaries

x86_64

arm64

mountpoint-s3 - mountpoint-s3 v1.3.0

Published by github-actions[bot] 11 months ago

New features

Mountpoint now supports resolving S3 Express One Zone endpoints and the new SigV4-Express signing algorithm will be used for S3 Express One Zone buckets. Note that readdir results on these buckets will not be ordered because ListObjectsV2 is unordered on S3 Express. (#642)

Breaking changes

No breaking changes.

Other changes

New Mountpoint cache directories will be created with owner access only permission. Additionally, the cache directory will be removed entirely at mount time rather than just the contents. (#637)

Binaries

x86_64

arm64

mountpoint-s3 - mountpoint-s3 v1.2.0

Published by github-actions[bot] 11 months ago

New features

Introduced optional caching of object metadata and content, in order to allow reduced cost and improved performance for repeated reads to the same files. To get started, see the caching section of the configuration documentation. (#622)

Breaking changes

No breaking changes.

Binaries

x86_64

arm64

mountpoint-s3 - mountpoint-s3 v1.1.1

Published by github-actions[bot] 11 months ago

Breaking changes

No breaking changes.

Other changes

Some applications that read directory entries out of order (for example, PHP) will now work correctly. (#581)
Fixed a bug that caused file creation to fail if a file with the same name had previously been created with Mountpoint and then deleted remotely. (#584)
Fixed an issue where Mountpoint could time out or hang on launch if IMDS was not available. (#601)

Binaries

x86_64

arm64

mountpoint-s3 - mountpoint-s3 v1.1.0

Published by github-actions[bot] 12 months ago

Breaking changes

Mountpoint will now complete file uploads at close time, and close will return an error if the upload was not successful. Before this change, close did not wait for the upload to complete, which could cause confusing results for applications that try to read a file they just wrote. (#526)

Other changes

Fixed a bug that caused poor performance for sequential reads in some cases (#488). A workaround we have previously shared for this issue (setting the --max-threads argument to 1) is no longer necessary with this fix. (#556)
Introduced the --user-agent-prefix <PREFIX> CLI argument to optionally allow specifying an additional prefix for the HTTP User-Agent header sent with all S3 requests. (#548)

Binaries

x86_64

arm64

mountpoint-s3 - mountpoint-s3 v1.0.2

Published by github-actions[bot] about 1 year ago

Breaking changes

No breaking changes.

Other changes

New Mountpoint releases are built on CentOS 7 instead of Amazon Linux 2. This lowers the minimum requirement to run Mountpoint to glibc 2.17 or newer. (#517)
Fixed a bug where writing to a file for longer than five minutes will result in a panic. (#513)
Updated the prefetcher to cancel discarded tasks and free up some unused resources on random read workloads. (#505)
Fixed an issue with internal resource cleanup which could lead to Mountpoint hanging after a high number of file uploads. (#529)

Binaries

x86_64

arm64

mountpoint-s3 - mountpoint-s3 v1.0.1

Published by github-actions[bot] about 1 year ago

Breaking changes

The permissions CLI flags --allow-other and --allow-root are now mutually exclusive. --allow-other implies --allow-root, and so should be used if you want the effect of both flags. (#475)

Other changes

Added new metrics for object writes, IO sizes, file handles, and directory operations. The existing fuse.bytes_read metric has been renamed to fuse.total_bytes and is now keyed by operation (read/write). (#461)
When running in background mode (the default), Mountpoint now correctly closes standard input and output once mounting succeeds. This should fix issues with scripts that try to fork Mountpoint as a background process, which may previously have hung. (#489)
Mountpoint can now read objects in the S3 Glacier Flexible Retrieval and S3 Glacier Deep Archive storage classes if they have been restored. Mountpoint cannot issue restore requests, but if you issue a restore request separately, the restored objects will be readable. (#467)

Binaries

x86_64

arm64

mountpoint-s3 - mountpoint-s3 v1.0.0

Published by github-actions[bot] about 1 year ago

This is the first General Availability (GA) release of Mountpoint for Amazon S3.

Breaking changes since alpha

Logging to disk is now disabled by default.
Logs will no longer be written to $HOME/.mountpoint-s3/ and should be configured using --log-directory <DIRECTORY>.
Bucket options of --virtual-addressing is now removed and --path-addressing is changed to --force-path-style.
If --force-path-style is not provided, addressing style of endpoint will be resolved automatically.
The --thread-count option has been removed and replaced with --max-threads which sets the maximum
number of threads the FUSE daemon will dynamically spawn to handle requests.

Other changes

New bucket options of --transfer-acceleration and --dual-stack have been added.
ARN is now also supported as <BUCKET_NAME> to mount the corresponding resource using Mountpoint.