- Issue created by @frazras
- πΊπΈUnited States cmlara
From the README file:
* If your S3 bucket is configured with BlockPublicAcls then enable the 'upload_as_private' setting. Example: $settings['s3fs.upload_as_private'] = TRUE; * If s3fs will provide storage for s3:// or public:// files the generated links will return 403 errors unless access is granted either with presigned urls or through other external means.
From an S3fs standpoint either is acceptable and is not really an s3fs question but a question of what your policies are around data security for the appropriate choice.
The key information is when you choose
"$settings['s3fs.upload_as_private'] = TRUE;
(which is correct for Bucket ACL's disabled) is that it becomes the responsibility of the bucket owner (yourself) to either create a bucket policy that grants access to the appropriate S3 paths to make them public at the bucket level, to use pre-signing inside the s3fs module (though their are Drupal Cache issues to be aware of with this), or use other external means that allows access to the objects. - Status changed to Fixed
4 months ago 8:50pm 19 August 2024 - πΊπΈUnited States cmlara
Considering this issue resolved as no additional questions were raised after providing feedback.
Automatically closed - issue fixed for 2 weeks with no activity.