Currently, the only location to declare the AWS access key and secret is in the settings.php file. This is inadequate for sites storing files containing sensitive information.

Providing optional integration with the Key module would improve security as AWS credentials could be stored in an external location such as Lockr or Townsend Security.

A patch providing this integration will be posted shortly.

CommentFileSizeAuthor
#3 interdiff_2-3.txt421 bytestame4tex
#3 flysystem_s3-key_module_integration-3057133-3.patch8.79 KBtame4tex
#2 flysystem_s3-key_module_integration-3057133-2.patch9.14 KBtame4tex

Comments

tame4tex created an issue. See original summary.

tame4tex’s picture

tame4tex commented
Status: Active » Needs review
StatusFileSize
new flysystem_s3-key_module_integration-3057133-2.patch9.14 KB

Please find attached a patch which optionally integrates Flysystem S3 with the Key module for more secure AWS key and secret storage.

An AWS credentials specific Key type plugin has been created for use when adding the new Key. There is also a new Configuration Settings Form to select the key to use.

This integration is optional. If the key module is not installed, no keys are created and declared or the AWS key and secret are declared in the settings.php file, then the module will continue function as it currently does.

I have also added detailed instructions to the README for how to use.

tame4tex’s picture

tame4tex commented
StatusFileSize
new flysystem_s3-key_module_integration-3057133-3.patch8.79 KB
new interdiff_2-3.txt421 bytes

Fixed issue with the original patch. Removed an unused use statement.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Given that there can be multiple S3 file systems enabled on the same site, this would need to support more than one key/secret?