I
Loh
Lwelll
Lstill doesn't work
LI created a new token with read permissions
Lstill the same thing
BBash substitutes just fine as long as it's not in single quotes (& I think you mean
${} right? - $() is a subshell invocation)
IYeah, I do 
INot my area of expertise haha
Jif its a sig failure, try
--debug, will dump the string to sign and canonical reqB@lmtr0 unfortunately I can't help you anymore. It's the weekend and I need to take a break & hit the gym. I hope the community manages to help you out. I think I've seen people get the aws command-line tool to work but I'm not sure what's different
BAll I can give you really is the signature we computed for your request
BBut to me one sha256 string being different from another isn't generally helpful
Lok, thank you for your help, I have spent all day today trying to make this work. I need a break too.
Maybe later the problem will solve itself lol
Maybe later the problem will solve itself lol
BWhat 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
Lboth
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.
