Releases for S3 File System

D10.1 Support

Contributors (1)

cmlara

CSS/JS Changes in Drupal Core 10.1

Drupal Core 10.1 has moved CSS and JS aggregation storage to the "assets://" streamWrapper. This means that in the latest versions of Drupal aggregated CSS and JS files will no longer be stored in the S3 bucket.

Changelog

Issues: 2 issues resolved.

Changes since 8.x-3.2:

D10 support + bugfix

Contributors (4)

cmlara, n4r3n, Project Update Bot, joncjordan

Changelog

Issues: 3 issues resolved.

Changes since 8.x-3.0:

Regression of SA-CONTRIB-2022-057 + 1 additional bugfix

Contributors (1)

cmlara

Changelog

Issues: 2 issues resolved.

Changes since 8.x-3.0-rc1:

The module doesn't sufficiently prevent file access across multiple filesystem schemes stored in the same bucket.

See S3 File System - Moderately critical - Access bypass - SA-CONTRIB-2022-057 for more information.

This module enables you to utilize S3-compatible storage as a Drupal filesystem.

The module doesn't sufficiently prevent file access across multiple filesystem schemes stored in the same bucket.

This vulnerability is mitigated by the fact that an attacker must obtain a method to access arbitrary file paths, the site must have public or private takeover enabled, and the file metadata cache must be ignored.

Compatibility with AWS SDK >= 3.228.0 + other bugfixes

Beta 3 bugfix release
The majority of these are minor edge case bugs.

The biggest issue solved is for those using path based endpoints config validation would fail in 8.x-3.0-beta2 (#3225789).

The remaining 4 bugfixes would have minor impact.

First beta release

This release contains bufixes and features.

Any remaining open bug reports are regarding limitations in Drupal Core, limitations of the SDK, or are caused by other modules.

This release is believed to be stable and ready for final testing prior to a formal stable release.

Improved D9 compatibility, general enhancements and general bugfixes.

This release aims to primarily fix known issues inside of S3FS. This release does not fix all known issues however it is believed this release improves on alpha16, especially as it relates to D9, to justify publication while work continues on the rest of the issue queue.

The issues not included in this fix appear to be primarily related to metadata cache rebuild, file migration and less common bugs. Development will continue on known issues.

A cache rebuild should be performed after deploying this code as this release makes changes to existing services declarations and adds additional services. More information on steps to rebuild the cache can be found in the Clearing the Cache Guide.

Ran through these issues, what was possible to cherry-pick.

https://www.drupal.org/project/s3fs/issues/3025517

Issue #2915322 by mikeryan, semjuel, aguilarm, firewaller, scaldinglake, jansete: Image styles: Error generating image, missing source file
Issue #3106533 by jkswoods, sidharthap, jansete: Drupal 9 Deprecated Code Report
Issue #3111978 by pajor, jansete: Provide a way to alter configuration

Issue #3016824 by nrackleff: Notice: Undefined index: s3fs_use_versioning
Issue #2981730 by ron_s: Copy system images to S3 when rendering direct paths to CSS/JS files
Issue #2969063 by ron_s: Allow domain name to map directly to root path

Issue #2984134 by phjou: Add missing new regions in settings form
Issue #2972251 by mikeryan and jansete: "s3fs_file" table has no primary key

Batch integration (Drush and UI compatible) to improve migrate files performance.
Use new Messenger service instead deprecated drupal_set_message().
Drush 9 port commands.

Important issue:
Issue #2772721 by jansete, MickeA, Berdir, geerlingguy, naveenvalecha, chrowe: Use Settings for AWS S3 secret_key and access_key instead of config system. You must move your secret_key and access_key from $config or settings form to $settings.

Example:
$config['s3fs.settings']['access_key'] now is $settings['s3fs.access_key']
$config['s3fs.settings']['secret_key'] now is $settings['s3fs.secret_key']

Validate configuration in Actions administration form instead in every streamwrapper call. This is a performance update.

Add Advagg integration

Solve image styles generation when redirect module is enabled.

The most important feature is the new callback for generating image styles like Drupal 7.

The main features of 7.x-2.x and 7.x-3.x branches are ported to Drupal 8 and the most important issues are solved. We will resolve issues, add tests and review performance to get beta version.

Issue #2853778 by jansete: Config form does not display region "EU - London (eu-west-2)"
Issue #2821971 by prince_zyxware, jansete: Fix coding standard - spacing issues
Issue #2851983: Removed the largely pointless cache for s3fs_file table reads.
Issue #2858314: Corrected rmdir()'s improper SQL queries.

Issue #2771979 by minakshiPh, chrowe, jansete, naveenvalecha: Update Readme.txt instructions for drupal 8
Issue #2854321 by jansete: Move _s3fs_convert_metadata to S3fsStream class
Issue #2854304 by jansete: Replace deprecated methods and functions
Issue #2854294 by jansete: Replace deprecated check_url by UrlHelper::filterBadProtocol()
Issue #2812747 by rhett.prichard, jansete: drush s3fs-copy-local can not find the exception class?
Issue #2854039 by jansete: Replace deprecated drupal_dirname by \Drupal::service('file_system')->dirname()

Issue #2825806: Wrong bucket policy example in README.
Issue #2833958 by Shashwat Purav: Add Asia Pacific (Mumbai) Region.
Issue #2833981 by Shashwat Purav, krina.addweb: Remove extra single quote from README.txt
Issue #2826372: The new stream_metadata() API is now implemented.
Issue #2464031 by FluxSauce, catbear: Add support for very large object counts

#2496033 by steel-track: Refactored the module to use AWS SDK v3. Also, refactored the stream wrapper to inherit from the AWS SDK's S3 streamwrapper wherever possible.