How do I resolve access denied aws s3 files?

user_1176873 0
Viewed 9926

Im trying to make files on my s3 bucket (CSS JS files) accessible to a Django application running in heroku.

I think I have the settings.py configured correctly.

However when I try to make changes to permissions in the S3 bucket i get access denied. Access denied error

I added cors and bucket policy is set to public.

Ultimately when I load the application from heroku Im getting 403 errors when trying to access the static files.

Bucket policy:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AddPerm",
            "Effect": "Allow",
            "Principal": {
                "AWS": "*"
            },
            "Action": "s3:*",
            "Resource": "arn:aws:s3:::NameOfBucket/*"
        }
    ]
}

CORs configuration: 

<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
    <AllowedOrigin>*</AllowedOrigin>
    <AllowedMethod>GET</AllowedMethod>
    <MaxAgeSeconds>3000</MaxAgeSeconds>
    <AllowedHeader>Authorization</AllowedHeader>
</CORSRule>
</CORSConfiguration>

public access settings How can I get the permissions to make changes in the s3 bucket please?

amazon-web-services heroku amazon-s3 django
2 Answers

The option is called Block public and cross-account access if bucket has public policies. When this was TRUE, it meant that the Bucket Policy only applied to the bucket owner.

For details, refer to: Using Amazon S3 Block Public Access - Amazon Simple Storage Service

These four new settings could be considered annoying because they are additional blockages on trying to make content public, but they are probably going to save many organizations a lot of embarrassment by preventing accidental public exposure of data.

user_1747770

New S3 feature - S3 Public block might be blocking your request. You can look at your cloudtrail logs to get more details. More details : https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html

Also looking at your policy, you are allowing s3:* action on your bucket prefix to all AWS principals. Generally, it is not good practice to open all S3 action to all AWS principals. Kindly review your need and scope down policies to achieve better security on your bucket objects.

user_11583510
Related