What I really should do though is dump the canonical request in the logs modulo secrets - that might
What I really should do though is dump the canonical request in the logs modulo secrets - that might be a good debugging thing
Lhave a great time at the gym :)
Lmaybe another time :) we should take a break. I mean, I have already spent more than 5 hours on the same problem.....
CNot too helpful, but I would just try re-creating and double checking what you did.
i.e make a new key, get sha256sum of it
Someone way earlier mentioned that one of their keys was just borke until it was remade.
For me on windows at least, that command works fine without issue, so it shouldn't be something with R2 not supporting something thataws s3api is sending
https://r2-sharex.chaika.dev/file/2022/03/powershell_BV5F3QKUH7.png
i.e make a new key, get sha256sum of it
echo -n "$CLOUDFLARE_API_TOKEN" | sha256sum | cut -f 1 -d " ", and try again.Someone way earlier mentioned that one of their keys was just borke until it was remade.
For me on windows at least, that command works fine without issue, so it shouldn't be something with R2 not supporting something thataws s3api is sending
https://r2-sharex.chaika.dev/file/2022/03/powershell_BV5F3QKUH7.png
LI will try with a new bucket
Lsame error
Lgenerate a new api key
L
Lat least the sha256sum starts with 69
Lfelling good now
L
Lsame error
L
Lall the same error
Lhmmmmmm
Ls3 api is a pain.....
CStrange, I just generated a new key with the same permissions, grabbed the ID, sha256sum, ran aws configure and popped in the new values, and ran it no issues
Lhmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
Lis the problem in my machine?
Lnop, same error in fly.io
Lmaybe the logs will tell us something
Lbut thats only on monday
Lnonetheless thank you for your time, happy weekend
CWhat's your use case? Big files enough that you can't use CF Workers to proxy, or something else?
Ecc @andrew_nyr, dont forget to set your sharex region to
i will try and update the image guide i pinned now
earth so it doesnt break in futurei will try and update the image guide i pinned now
Aoh yeah thx for ping!
Eupdated the pinned sharex guide with this new information
Lsome files will problably be small
Lsome big
CAh, I was going to say for now you could just Make a worker linked to your bucket and and handle uploads/etc through it
Lthats an opt
Lbut then I would need to write the s3 api on a worker......
CNah you would just use R2 bindings, to use r2 directly
CIt's pretty close to a KV Binding, docs aren't great right now though, pretty much only options are looking at existing code i.e cherryjimbo's sharex worker (https://github.com/Cherry/ShareX-R2-Cloudflare-Workers/blob/main/src/routes.mjs) and the Cf Worker Types which includes typings for all the r2 stuff
HStore large amounts of unstructured data without egress fees.
COops, there is some info on the docs. As far as I can see that's the same info as it on the live docs, and still is using outdated stuff like the internal bindings
I.e get mentions
const { value } = await MY_BUCKET.get(key);
Which doesn't work anymore
I.e get mentions
const { value } = await MY_BUCKET.get(key);
Which doesn't work anymore
JI’ve been meaning to make a PR to fix that one. That was the old internal bindings, yeah
HR2 Docs(May be a little behind for now, while the team is constantly pushing changes):
https://developers.cloudflare.com/r2/
https://developers.cloudflare.com/r2/
HDone
Erepinned the first message to keep it on the top of the list
JJhehe
Ji usually just send graphql queries constructed myself and process the response as any other json api, no generic framework needed for a known query or two