I want to write something for this repo about the S3 permissions that we use for buckets that serve personal feeds and likes. Also for static public info that the server itself generates.
This is a screen shot of the top of the Permissions page that I use for data.feedland.org.
We don't block public access, and confirm that the content is publicly accessible.
Skimming the rest of the permissions page, everything else is set as you would expect. Basically the public has read-only access to all the content in this bucket.
I want to write something for this repo about the S3 permissions that we use for buckets that serve personal feeds and likes. Also for static public info that the server itself generates.
This is a screen shot of the top of the Permissions page that I use for data.feedland.org.
We don't block public access, and confirm that the content is publicly accessible.
The bucket policy is:
Skimming the rest of the permissions page, everything else is set as you would expect. Basically the public has read-only access to all the content in this bucket.