Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
pulpbot opened this issue Jan 17, 2022 · 3 comments
Closed

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

pulpbot opened this issue Jan 17, 2022 · 3 comments

Comments

@pulpbot
Copy link
Member

pulpbot commented Jan 17, 2022

Author: daviddavis (daviddavis)

Redmine Issue: 4455, https://pulp.plan.io/issues/4455


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 jschneier/django-storages#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.

@pulpbot
Copy link
Member Author

pulpbot commented Jan 17, 2022

From: @bmbouter (bmbouter)
Date: 2019-02-25T16:55:09Z


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

@dralley dralley removed New labels Feb 1, 2022
@stale
Copy link

stale bot commented May 24, 2022

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

@stale stale bot added the stale label May 24, 2022
@dralley dralley removed the stale label May 25, 2022
@gerrod3
Copy link
Contributor

gerrod3 commented Sep 18, 2024

Outdated.

@gerrod3 gerrod3 closed this as completed Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants