edit: finally figured it out (i swear i looked for a long time before posting) — if you create a nor
edit: finally figured it out (i swear i looked for a long time before posting) — if you create a normal cloudflare API token, and pick workers R2 as the scopes, it won't show an Access Key ID, even if it's transferred to be an R2-speicifc token with per-bucket access controls. you have to start at the R2 token UI in order to create a token that will show an Access Key ID for usage w/ the s3-compatible api
0 Replies