Kthanks i look everywhere in the doc except on the aws because i thought it was not about AWS. Cheers
KOkay thanks sam, i'll try this module
Kwhat is the accessKeyId? in Cloudflare profil > token. I have generated a new token for my r2 bucket and gave it a name ("r2-test"). I thought it was this name the accessKeyId. But the aws-sdk-js-v3 expect a 32 char string for it. The token generated is 40 char so that's probably the secretAccessKey ?
Kokay by clicking roll i got the id and the secret.
Ki do have a signature problem though "SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your secret access key and signing method.". I have only 3 input to provide: endpoint, accessKeyId, secretAccessKey. And i'm pretty confident that the 3 are correct. Am i missing something here
UIt will always work, the way R2 does custom domains is a bit interesting to where the auto detection of hostname certs isnt entirely accurate.
Kit works ! the tokenID and secret from Profil > Token for R2 doesn't work but the one from R2 > Token work. Cloudflare need to test this. And also have 2 differents place to create r2 token is really confusing. Specially when one work and not the other.
PAny plans to allow Location hints for R2 in Wrangler?
KIt already has them, no?
Pthis is all i see on 3.1.1
KHuh, I saw the PR ages ago but it's been closed with no comment.
P:(
Kcc @Sid | R2
K
KAnyway to hide the cloudflare domain and account ID from presigned url? here how a presigned url is https:// {bucket name}.{my account ID}.cloudflarestorage.com/{token} .
EYou can't, for what use-case would you need to? Neither ID is private information
SOh, er let me look for it
KWell it doesn't look professional
KK
KOh
KHaha
KFrom Cloudflare R2 documentation "You will not share presigned URLs directly with end users or browsers, as presigned URLs are used more for internal applications.". So i guess what they mean by this is that they expect people to use a proxy server where the proxy server download the file from R2 and then provide it to the end user ?
PMaybe you could use a worker triggered by a cleaner url/path to do the data transfer?
Pdata.mydomain.com/file?id=blah
something along those lines perhaps
something along those lines perhaps
Ki don't want to pay massive bill for request and bandwidth by using workers
KThe issue is the full URL query params - which has the 'signed' part
Ubandwidth is free fwiw
PI think you'd be really surprised at how affordable it is, but cost is still a consideration
KBut the amount of time running the worker function is not? so if a worker function need to run 1mn to run to download a file to a user. That will be pricey
PI think I'm only paying $5 for this still
Kor i'm missing something.
PI mean you could probably just have the worker generate or find the URL and return a 302 instead
P(I'm not 100% familiar with how the signed links work so I'm just spitballing)
UBundled workers are $0.50/million requests after the first 10 million included in the $5/mo workers plan. There is no duration charges.
Unbound charges for duration but would honestly probably be super fast anyways if all you do is proxy so
Unbound charges for duration but would honestly probably be super fast anyways if all you do is proxy so
K400,000 GB-s, + $12.50/million GB-s
K
UIts like pennies per ms
Unot even pennies
KI wanted to put the crying smiley haha
Ufractions of a penny
KNot when you have million of images to load every day
Knot pennies
U$0.0000000016 per millisecond and a signed url proxy would take like a few ms at most. Would be cheaper than bundled at a per request level but bundled includes more free requests
