well

it's not working

I generate the api key and I'm confued where I put it as a credential

is it a access_key, session_token?

I tried both

but I'm getting Internal Server error for everything

The library I'm using is using the url

bucket.account.r2.cloudflarestorage.com

sha256 of the api key

that's the secret access key

we have a UI improvement coming for that shortly

I wrote about how to use R2 with S3 in this message https://discord.com/channels/595317990191398933/940663374377783388/967111902197071952

would be awesome to have permissive cors headers set on

account.r2.cloudflarestorage.com

, would allow storage management pwas with no server-in-the-middle

What do you mean?

Access-Control-Allow-Headers: *

response header on

*.r2.cloudflarestorage.com

s3 api calls, would allow a client-side webapp the ability to manage r2 storage

thx

open beta estimate is sometime in Q2 (between now and June) general availability estimate is sometime in H2 (anytime before the end of the year) these are just rough estimates though, the actual timeline my vary

the current state is private beta

oh wow, awesome!

@mr. matthew breaking changes > open devtools first then go to the API Tokens list page what devtools?

Browser devtools.

oh

Hmmm

cant find this request

found it

it was hinding himself lol

Release notes
    Improve parsing of Credential component of SigV4 Auth.
    Improve parsing of SignedHeaders component of SigV4.
    Fix compatibility with clients encoding SigV4 authorization header in a more varied set of ways than expected.

The main thing here is sigv4 parsing should be fixed hopefully. I also added a thing for DropShare to figure out what the

x-amz-acl

value it's sending is

err - jumped the gun

not deployed yet

You will need to open it before the page loads otherwise the request won't be logged with devtools

still internal server error