@thejellopy you can use a denoflare in front of each bucket, and assign your own distinct access key id and secret access key credentials for each, and not have to share your global r2 token's s3 compatibility credentials... at least for read access... https://github.com/skymethod/denoflare/releases/tag/v0.5.0
Basically every object storage provider implements an S3 compatible API - it's the industry standard for object storage and if you don't implement it, you're kneecapping yourself.
All of the AWS SDKs are best documented by AWS, they wrote them. If Cloudflare tried to, it'd be an immense workload on PCX & the engineers who need to give it a review.
That being said, the current examples could do with showing retrieving and uploading objects - but there's so many use-cases that are already covered by the SDK's documentation
I see plenty of SSL validation failed for <r2 S3 endpoint> TLS/SSL connection has been closed (EOF) (_ssl.c:997) when trying to delete some old objects. Issues with R2?