I created a new token with read permissions

still the same thing

Bash substitutes just fine as long as it's not in single quotes (& I think you mean

${}

right? -

$()

is a subshell invocation)

Yeah, I do 🙂

Not my area of expertise haha

if its a sig failure, try

--debug

, will dump the string to sign and canonical req

@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

All I can give you really is the signature we computed for your request

But to me one sha256 string being different from another isn't generally helpful

ok, 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

What I really should do though is dump the canonical request in the logs modulo secrets - that might be a good debugging thing

have a great time at the gym :)

maybe another time :) we should take a break. I mean, I have already spent more than 5 hours on the same problem.....

Not 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

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

I will try with a new bucket

same error

generate a new api key

at least the sha256sum starts with 69

felling good now

same error

all the same error

hmmmmmm

s3 api is a pain.....

Strange, 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

hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm

is the problem in my machine?

nop, same error in fly.io