-
Notifications
You must be signed in to change notification settings - Fork 686
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
Access denied on image upload #166
Comments
@simon-asp I ran into the same issue. I was able to fix this by editing my public access list controls for the bucket in AWS. Manage public access control lists (ACLs) I have to admit, I'm not entirely sure what the security vulnerabilities this creates. If you have any info on this I'd love to hear about it. |
@topherolson Thanks! that didn't work for me. Can you show me what you did otherwise? |
I did the standard install. So I would just make sure your Config Vars in Heroku are set properly, i.e. proper naming convention for your Bucket region. |
I'm running into this same issue. @simon-asp were you able to resolve? I have checked my credentials using the aws cli tool and I'm able to upload from there. |
I ran into the Access Denied issue, and later a different issue where the image would successfully i upload but then couldn’t be displayed correctly. Eventually I was able to get the uploads working, though only by unsetting Have you checked whether you can create publicly readable assets from the CLI? |
Followed all of the above and can upload a resource via the CLI with the keys I provided—not sure why this isn't working and would appreciate any help! |
Ah actually updating the bucket policy per this repo seems to have done the trick! |
I had this "Access denied" issue too after blocking public access to my S3 bucket (I use Cloudfront to access images) - realized that the S3 adapter this project uses defaults to a public ACL when adding new images, so specifying a |
Hey! I read all the old issues on the AWS issues, but I can't get it to work.
I used
us-east-1
as mentioned here.What could be wrong?
The text was updated successfully, but these errors were encountered: