if it isn't in there, then you didn't get access

Hm...

did you manage to send the dm before the cutoff?

This was something else.

like a green name thing or the meetup form?

Trying to get the s3 endpoint to work and failing, any hints? endpoint .r2.cloudflarestorage.com access_key_id secret_access_key (also tried hex(sha256(utf8())) with no luck) getting 401 with

Unauthorized

body. Same token works with rest api and deployed worker bucket binding. Using a path-style call to list-bucket-v2 (

/<bucket-name>/?list-type=2

)

This recent thread got me all excited -_-

Crossing my fingers for May

secret_access_key is definitely

hex(sha256(api token))

Maybe

account-id

is off?

What is the issue?

Oh - for now you're getting the free enterprise plan for R2

I don't know what the legal implications are for accepting/denying the agreement

@lmtr0 was that your question?

I can't read the text

cause it's darkmode on dark text

Ok. So it's unreadable when your browser is in dark mode

I'll let the UI team know

what's the region used for signing? i'm defaulting to

us-east-1

Naw

R2 doesn't have regions

but sigv4 does : )

I know. I think it's "world"? Checking

@albert what did you use?

I didn't put anything. Let me check if an arbitrary string works.

yup, arbitrary string works

I got 401 Unauthorized when I didn't have a valid accessKeyId. If I had valid accessKeyId but invalid secretAccessKey, I got 403 Forbidden instead.

i'm getting a 401 no matter what, hmm, the token id is the top level "id" in the json, right? ie the same as in the url that is PUT: PUT https://dash.cloudflare.com/api/v4/user/tokens/

no

The access_id is from the network tab