Create an S3 Bucket for File Uploads

From @jayair on Mon Apr 10 2017 00:57:49 GMT+0000 (UTC)

Link to chapter -

Copied from original issue:

From @alexspark on Sat Aug 12 2017 21:11:36 GMT+0000 (UTC)

Looks like the 3rd part in S3 Bucket creation got an update. Got confused for a few seconds.

From @jayair on Sat Aug 12 2017 22:12:38 GMT+0000 (UTC)

@alexspark Thanks for letting us know. Updated -

From @lucasgonze on Mon Nov 13 2017 19:11:31 GMT+0000 (UTC)

In the screen shot in the chapter, the owner is admin, which is the IAM user created earlier. However when I created the bucket just now the owner was based on the email for the AWS account.

This may be significant down the road, given that permissions can lead to baffling issues. If this is significant I can add a user using the name of the IAM role and grant the same permissions as in the default.

From @jayair on Tue Nov 14 2017 19:32:07 GMT+0000 (UTC)

@lucasgonze Ah. The admin is the username on the account we were using and not an AWS thing. I think for this case the default owner should be fine.

From @ondrejpar on Mon Dec 25 2017 16:30:59 GMT+0000 (UTC)

You should probably mention that using wildcard in CORS configuration is wrong security-wise and definitely should not be used in production environment.

1 Like

From @jayair on Wed Dec 27 2017 22:45:08 GMT+0000 (UTC)

@ondrejpar Good point. Just added a note.

The Set permissions tab in the new S3 bucket wizard has changed. The wording in some of the checkboxes pretty much matches the screenshot in the tutorial, but a couple of them don’t seem to be doing the exact same thing any more. Could we get an updated screenshot based on the updates AWS has done with S3?

1 Like
        "AllowedHeaders": [
        "AllowedMethods": [
        "AllowedOrigins": [
        "ExposeHeaders": [],
        "MaxAgeSeconds": 3000

The CORS config should look like this now :ok_hand:

tks. It’s only missing the “[” in the beginning.

Yup the chapter has been updated.