If you’ve found yourself marveling at how cryptic and impenetrable understanding AWS services, then you are definitely not alone. For much too long...
For further actions, you may consider blocking this person and/or reporting abuse
I believe
arn:aws:s3:::*/*will allow access to objects on any bucket the IAM user has access to. You should probably usearn:aws:s3:::NAME_OF_YOUR_BUCKET_GOES_HERE/*if you want to restrict access just to that bucket.I was leaning on the S3 policy builder for feedback and mid-interpreted its recommendation. Always learning 😁 thanks for the catch. I’ve updated the post to reflect this.
Note that the
s3:ListBucketpermission still needs to be on the bucket resource, i.e.arn:aws:s3:::NAME_OF_YOUR_BUCKET_GOES_HERE. This permission allows you to list objects in the bucket, which is needed for ActiveStorage's#delete_prefixed.Ahh - that must be what was causing my validation warning in the editor! How does this look?