Support for second bucket for private files

Created on 9 March 2016, almost 9 years ago
Updated 4 January 2025, 4 days ago

As per the advise of my local sys admin, it would be better to have a second bucket for private files. Also for peace of mind of clients who have sensitive information. This can be an optional setting. I'm thinking along these lines:

  • The user with the aws credentials will have the same access policies to the first bucket and private bucket.
  • The buckets should be live in the same region.
  • We won't have to change anything in the db tables since the changes will be done in the Stream Wrappers.
  • If set, the private bucket will be used in all private:// files. Else we still use the default bucket.

I've started some basic work on this and just thought to tell you guys. I'll upload patches when I get some ready.

✨ Feature request
Status

Closed: outdated

Version

2.0

Component

Code

Created by

πŸ‡³πŸ‡ΏNew Zealand japo32

Live updates comments and jobs are added and updated live.
  • Security improvements

    It makes Drupal less vulnerable to abuse or misuse. Note, this is the preferred tag, though the Security tag has a large body of issues tagged to it. Do NOT publicly disclose security vulnerabilities; contact the security team instead. Anyone (whether security team or not) can apply this tag to security improvements that do not directly present a vulnerability e.g. hardening an API to add filtering to reduce a common mistake in contributed modules.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States cmlara

    Drupal 7 end-of-life triage:
    Drupal 7 will reach end of life on January 5th.

    The 7.x branches of S3FS do not have any additional planned releases.

    The feature requested in this issue has already been implemented into the 4.x dev branch for inclusion in a future release.

Production build 0.71.5 2024