问题:

I'm following Hartl's railstutorial.org and have arrived at 11.4.4: Image upload in production. What I've done:

Signed up for Amazon Web Services
In Amazon Identity and Access Management I created a user. The user was created succesfully.
In Amazon S3 I created a new bucket.
Set permissions on the new bucket:

Permissions: The tutorial instructs to "grant read and write permission to the user created in the previous step". However, under 'Permissons' for the bucket the new user's name is not mentioned. I could only choose between Everyone, Authenticated users, Log delivery, Me, and a username Amazon seems to have created itself from my name + a number. I have tried it by selecting Authenticated users and checked the boxes for Upload/Delete and View permissions (and not selecting List and Edit permissions). I also tried it by selecting Everyone and checked all the four boxes. The results were the same.

I implemented in my Rails application following the instructions of the tutorial (I don't belief anything wen't wrong there, so I haven't included those steps here to not make it too long).

The initializer carrier_wave.rb is set to the code below. I've added region: 'eu-west-1' to the initializer (an idea I got from here) to get rid of the message connecting to the matching region will be more performant.

if Rails.env.production?   CarrierWave.configure do |config|     config.fog_credentials = {       # Configuration for Amazon S3       :provider              => 'AWS',       :aws_access_key_id     => ENV['S3_ACCESS_KEY'],           # Set these key's using heroku config:set S3_ACCESS_KEY=<access key>       :aws_secret_access_key => ENV['S3_SECRET_KEY'],       :region                => 'eu-west-1'     }     config.fog_directory     =  ENV['S3_BUCKET']   end end

It worked in development and I pushed to Heroku.

Error: When using the uploader in production to upload an image, I get the error We're sorry, but something went wrong. The Heroku server log says:

What have I done wrong? I seems to have something to do with the permissions?

Update: The cause turned out to be the policies granted to the user. If I grant the user standard AmazonS3FullAccess then it works. It doesn't work with just AmazonS3ReadOnlyAccess, since then the user can't save a new image. In my application the user basically only needs 2 rights: upload its own avatar image and read the avatar image. Would it be safe to use AmazonS3FullAccess or should I write my own custom policy?

I tried the custom policy below, which should give the application read and write rights (adopted from here) but that still generated the 403 Forbidden error.

{   "Version": "2012-10-17",   "Statement": [     {       "Effect": "Allow",       "Action": ["s3:ListBucket"],       "Resource": ["arn:aws:s3:::mybucket"]     },     {       "Effect": "Allow",       "Action": [         "s3:PutObject",         "s3:GetObject",         "s3:DeleteObject"       ],       "Resource": ["arn:aws:s3:::mybucket/*"]     }   ] }

回答1:

To enable S3 file Uploads, I had to:

specify my region (us-west)
create an IAM user
add a Bucket Policy specifying that user as a Principal

{     "Version": "2008-10-17",     "Statement": [         {             "Sid": "AllowFileUpload",             "Effect": "Allow",             "Principal": {                 "AWS": "arn:aws:iam::XXXXXXX:user/instaswan"             },             "Action": [                 "s3:GetObject",                 "s3:PutObject",                 "s3:PutObjectAcl"             ],             "Resource": [                 "arn:aws:s3:::instaswan-dev",                 "arn:aws:s3:::instaswan-dev/*"             ]         }     ] }

Be sure to include both the top-level and "/*" Resource, and include any other "Action" attributes you need.

回答2:

In my case s3:PutObjectAcl was the permission that was missing

回答3:

You may be missing a step which is to set your IAM policy if using an IAM user to configure your bucket.

Go to IAM console, select your user, go to the permissions tab, click the attach policy button and add administrator access.

After that the error should go away and you can upload files with no problem ;)

回答4:

The root of the problem indeed turned out to be the permissions. It was necessary to write a custom policy and set the CORS configuration on the bucket. For any future users that want to implement this chapter of the rails tutorial, see Writing an IAM policy and CORS configuration for Amazon S3 for the necessary code.

回答5:

I had the same problem, the thing is Amazon changed their layout so now creating a user policy is a bit different than before. So once you create a policy remember to attach the policy to the user in question or you will get the 403 forbidden error

回答6:

I had both the issues from the tutorial -

Look in your heroku logs -

Forbidden

and

Socket Error

Going round trying to resolve this over a day I basically reset back to basics, Recreated a new IAM user and a new s3 bucket but this time left the REGION as US standard - the only s3 authority I could find to attach as the policy was full access - nothing else - so attached that

Also retyping and confirming ENV variables on heroku as well as COPY AND PASTING the carrier_wave.rb from tutorial - to be sure to be sure .)

first time round I was fiddling and unsure what to do so i might of clicked a few different things- adding groups and permissions, viewing wrong things - sometimes a RESET and STEP through everything especially after exploring AWS and IMS and s3 for the first time.

Interesting that in heroku they INSTRUCT to set the bucket region as US standard and post a warning - Be sure to create a bucket in the same region as your app to take advantage of AWS’s free in-region data transfer rates.

good read for heroku to s3 configuration here -> https://devcenter.heroku.com/articles/s3

转载请标明出处:Trying to set up Amazon's S3 bucket: 403 Forbidden error & setting permissions

文章来源: Trying to set up Amazon's S3 bucket: 403 Forbidden error & setting permissions

标签

aws

Trying to set up Amazon's S3 bucket: 403 Forbidden error &amp; setting permissions