2 Answers
Facepalm. It was staring me in the face.
In your bucket policy, you are applying your permissions to all of the contents of the bucket, not the bucket itself. I know that might not make sense, but if you remove the "/*" from the end of the Resource key in your policy, you should see the expected result.
Thank you Steven. I will confirm your findings. Any idea why I would receive a down vote for asking this questions? Makes one not want to ask questions if they should expect negative feedback.
What is confusing about this is that in the S3 bucket policy lesson, Ryan specifically demonstrates that you cannot simply use the bucket name in the resource section that in fact it will error if you try and save it that way. He states it is an exam topic and that you will be expected to know that you must add the /* for it to work correctly. Please refer to 9:12 in the bucket policies lesson.
Further experimentation has shown that the requirement for the trailing /* is only required when the action is related to bucket objects and not the bucket itself. Hopefully, the lesson can be updated to indicate this nuance. Thanks
I agree. I will take it up with Ryan to see if the lesson can be clearer about when either or both should be used.
From where are you connecting via CLI? From an EC2 instance, or from the real world?
I’m finding the same thing. Researching.
Good question ! I like.