You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When setting STORAGE_TYPE=s3 the requests to /storage-data/uploaded/?filepath=upload/1/somefile result in generated URLs for AWS presigned with the old format: URL?AWSAccessKeyId=AKIA...redacted...&Signature=F1H25pgUkZwDhV0S2b%2F48rPibWk%3D&Expires=1696592186.
We should introduce an environment variable that enable us to override the setting to s3v4, the only supported version in AWS S3, but keeps the existing behaviour by default so as not to break existing setups.
Describe alternatives you've considered
I think this is the best option, as it keeps the existing behaviour but allows it to be overridden to the latest version.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When setting
STORAGE_TYPE=s3
the requests to/storage-data/uploaded/?filepath=upload/1/somefile
result in generated URLs for AWS presigned with the old format:URL?AWSAccessKeyId=AKIA...redacted...&Signature=F1H25pgUkZwDhV0S2b%2F48rPibWk%3D&Expires=1696592186
.This is due to this call to the Django S3Boto3Storage class and, because the setting for the signature version in the Django setting AWS_S3_SIGNATURE_VERSION is
None
, the old signature version is being used.Describe the solution you'd like
We should introduce an environment variable that enable us to override the setting to
s3v4
, the only supported version in AWS S3, but keeps the existing behaviour by default so as not to break existing setups.Describe alternatives you've considered
I think this is the best option, as it keeps the existing behaviour but allows it to be overridden to the latest version.
The text was updated successfully, but these errors were encountered: