s
April 5, 2024, 5:35 a.m. |

Simon Willison's Weblog simonwillison.net

s3-credentials 0.16


I spent entirely too long this evening trying to figure out why files in my new supposedly public S3 bucket were unavailable to view. It turns out these days you need to set a PublicAccessBlockConfiguration of {"BlockPublicAcls": false, "IgnorePublicAcls": false, "BlockPublicPolicy": false, "RestrictPublicBuckets": false}.


The "s3-credentials --create-bucket --public" option now does that for you. I also added a "s3-credentials debug-bucket name-of-bucket" command to help figure out why a bucket isn't working as expected.

aws false figure files projects public s3 s3 bucket set view

Artificial Intelligence – Bioinformatic Expert

@ University of Texas Medical Branch | Galveston, TX

Lead Developer (AI)

@ Cere Network | San Francisco, US

Research Engineer

@ Allora Labs | Remote

Ecosystem Manager

@ Allora Labs | Remote

Founding AI Engineer, Agents

@ Occam AI | New York

AI Engineer Intern, Agents

@ Occam AI | US