Project

Profile

Help

Issue #4455

S3 doesn't work if you follow the guide in our docs

Added by daviddavis 8 months ago. Updated 6 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Severity:
2. Medium
Version:
Platform Release:
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

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 8 months ago

+1 to updating the docs temporarily and linking to this issue in there as well.

#2 Updated by CodeHeeler 8 months ago

  • Triaged changed from No to Yes

#3 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF