Sippy
Hi can someone help here. I am trying to enable sippy for one of my bucket. But the curl execution fails with error {"success":false,"errors":[{"code":10063,"message":"Invalid upstream credentials"}],"messages":[],"result":null}
I have checked the token is active and correct. Please help as I am completly stuck
18 Replies
Unknown User•5mo ago
Message Not Public
Sign In & Join Server To View
Thanks for replying! I have recreated the cred again and tried but the same error. I rechecked the AWS creds as well but same error.
I whave already moved some 820GB files to CF bucket.
Unknown User•5mo ago
Message Not Public
Sign In & Join Server To View
Is is that I am doing something wrong with the curl
Unknown User•5mo ago
Message Not Public
Sign In & Join Server To View
yes but may be I am not putting things at the right place
Yes I coped from doc is seems very simple but then when I execute it I am getting error all time.
can you check if the curl is correct
curl -X PUT https://api.cloudflare.com/client/v4/accounts/22b9d/r2/buckets/bucket/sippy --header "Authorization: Bearer -v29Lf"
--data '{"provider": "AWS", "bucket": "bucket", "zone": "eu-central-1","key_id": "AdsdsPS3SMI3ZF64X", "access_key":"ccdv", "r2_key_id": "fdfdfdf", "r2_access_key": "fdfdd"}'
Unknown User•5mo ago
Message Not Public
Sign In & Join Server To View
sure its already changes and not usefull Just want you to check if it looks correct syntatically
Unknown User•5mo ago
Message Not Public
Sign In & Join Server To View
yes
is it something to do with eu
Unknown User•5mo ago
Message Not Public
Sign In & Join Server To View
I select hint APAC when creating the bucket
Unknown User•5mo ago
Message Not Public
Sign In & Join Server To View
okay then what could go wrong. I am trying since 2 days with no luck.
Unknown User•5mo ago
Message Not Public
Sign In & Join Server To View
We have an ios app and the IOS dev was not able to use AWSS3 library to upload a file. That is where sippy came into consideration.
I will try again after generating CF r2 credentials and validate the aws credentials as well and see.
But please shed some light on AWSS3 library for IOS. the dev tried with custom endpoint but then he got
some : Error Domain=com.amazonaws.AWSS3ErrorDomain Code=0 "(null)" UserInfo={Code=NotImplemented, Message=STREAMING-AWS4-HMAC-SHA256-PAYLOAD not implemented, ResponseObjectError={
Code = NotImplemented;
Message = "STREAMING-AWS4-HMAC-SHA256-PAYLOAD not implemented";
}}
Hi @Sid | R2 I tried again after recreating both aws and r2 keys and access but still the same error. I even tried using python request but same error {"success":false,"errors":[{"code":10063,"message":"Invalid upstream credentials"}],"messages":[],"result":null}
This needs to be fixed else all our effort to move the data to CF r2 will be void because neither AWSS3 library is working on IOS nor sippy is getting enabled. We are completely stuck. What should I do?
Unknown User•5mo ago
Message Not Public
Sign In & Join Server To View
let me try
This is working for both the aws and r2
I will get back with more details on stresmin upload. Which I dont think is the case. We simply upload files that are ready to be uploaded like images and small videao under 10-50MB