Issue #4455
S3 doesn't work if you follow the guide in our docs
Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation
Sprint:
Quarter:
Description
You get a permission denied error if you set up pulp + S3 according to our docs. This warning somewhat explains the problem:
The default behavior of S3Boto3Storage is insecure and will change in django-storages 2.0. By default files and new buckets are saved with an ACL of 'public-read' (globally publicly readable). Version 2.0 will default to using the bucket's ACL. To opt into the new behavior set AWS_DEFAULT_ACL = None, otherwise to silence this warning explicitly set AWS_DEFAULT_ACL.
More info https://github.com/jschneier/django-storages/issues/381
The temporary fix is to set AWS_DEFAULT_ACL to 'None' in our settings. Not sure if we should update our docs since this is a temporary problem that should be resolved in django-storages 2.0.
History
#1
Updated by bmbouter over 2 years ago
+1 to updating the docs temporarily and linking to this issue in there as well.
#2
Updated by CodeHeeler over 2 years ago
- Triaged changed from No to Yes
#3
Updated by bmbouter over 2 years ago
- Tags deleted (
Pulp 3)
#4
Updated by daviddavis about 1 year ago
- Tags Documentation added
Please register to edit this issue
.