mountpoint-s3 v1.7.0

New features

• Metadata caching can now be configured independently of data caching. When passing the --metadata-ttl <seconds> argument without also specifying --cache <directory>, Mountpoint will cache file metadata in memory for up to the given TTL, but will not cache object data. The --metadata-ttl argument also accepts two special values: minimal to enable only the minimal necessary caching, and indefinite to cache indefinitely. These modes can help accelerate workloads that touch many files but do not need to cache object data for re-use (for example, listing a directory and then reading each file within it once). (#855)

Breaking changes

• The --metadata-ttl 0 setting is no longer supported and will be removed in a future release. The new --metadata-ttl minimal has a similar effect, but behaves better when latency for S3 requests is high. (#855)
• When using the --cache flag, the default metadata TTL is now set to 60 seconds (--metadata-ttl 60) instead of 1 second. (#855)
• Mountpoint now uses STS regionalized endpoints when assuming IAM roles configured in a CLI profile. If you specify a region in your CLI profile and want Mountpoint to use a role from that profile you have to make sure Mountpoint can access STS regionalized endpoints. This allows Mountpoint to assume an IAM role in regions outside of the aws partition. (#877)

Other changes

• The checksum algorithm to use for uploads to S3 can now be chosen with the --upload-checksums <ALGORITHM> command-line argument. The only supported values in this release are crc32c (the default, and the existing behavior) and off, which disables including checksums in uploads. The off value allows uploads to S3 implementations that do not support additional checksums. This option defaults to off when the bucket name is an S3 on Outposts bucket access point (either an ARN or a bucket alias). (#849)
• Fixed an issue where Mountpoint did not send the Content-Length header when creating multi-part uploads. (#875)
• Fixed an issue where Mountpoint could not assume an IAM role specified in a CLI profile with EcsContainer as a credential source. (#875)
• Added support for AWS_ENDPOINT_URL environment variable. (#895)

Binaries

x86_64

• RPM: https://s3.amazonaws.com/mountpoint-s3-release/1.7.0/x86_64/mount-s3-1.7.0-x86_64.rpm
• RPM signature: https://s3.amazonaws.com/mountpoint-s3-release/1.7.0/x86_64/mount-s3-1.7.0-x86_64.rpm.asc
• DEB: https://s3.amazonaws.com/mountpoint-s3-release/1.7.0/x86_64/mount-s3-1.7.0-x86_64.deb
• DEB signature: https://s3.amazonaws.com/mountpoint-s3-release/1.7.0/x86_64/mount-s3-1.7.0-x86_64.deb.asc
• tar.gz: https://s3.amazonaws.com/mountpoint-s3-release/1.7.0/x86_64/mount-s3-1.7.0-x86_64.tar.gz
• tar.gz signature: https://s3.amazonaws.com/mountpoint-s3-release/1.7.0/x86_64/mount-s3-1.7.0-x86_64.tar.gz.asc

arm64

• RPM: https://s3.amazonaws.com/mountpoint-s3-release/1.7.0/arm64/mount-s3-1.7.0-arm64.rpm
• RPM signature: https://s3.amazonaws.com/mountpoint-s3-release/1.7.0/arm64/mount-s3-1.7.0-arm64.rpm.asc
• DEB: https://s3.amazonaws.com/mountpoint-s3-release/1.7.0/arm64/mount-s3-1.7.0-arm64.deb
• DEB signature: https://s3.amazonaws.com/mountpoint-s3-release/1.7.0/arm64/mount-s3-1.7.0-arm64.deb.asc
• tar.gz: https://s3.amazonaws.com/mountpoint-s3-release/1.7.0/arm64/mount-s3-1.7.0-arm64.tar.gz
• tar.gz signature: https://s3.amazonaws.com/mountpoint-s3-release/1.7.0/arm64/mount-s3-1.7.0-arm64.tar.gz.asc