Open source platform for stress free deployments, measured impact, and smarter decisions.

GrowthBook Users

image.png

Hi, when I try to upload screenshots to experiment, I got this CORS error. I configured to access our S3 bucket. what else I need to configure?

I solved this by add CORS settings in the s3 bucket. but then  I got the new error when calling upload URL

hrmm, hard to tell where that is coming from

<https://github.com/growthbook/growthbook/blob/a125aa638fbcda8ce116f4f3f7aefd48a39d4fc0/packages/back-end/src/services/files.ts#L76>
This upload url should comes from this line of code

```&lt;Error&gt;
&lt;Code&gt;SignatureDoesNotMatch&lt;/Code&gt;
&lt;Message&gt;The request signature we calculated does not match the signature you provided. Check your key and signing method.&lt;/Message&gt;```

my initial guess is this related with these 2 setting? I just makeup 2 random string to set these 2 env values. Am’I wrong?

<@U01T6HCHD0A> I suggest you to change the s3 upload using the v4 version
<https://github.com/aws/aws-sdk-js/issues/1213#issuecomment-259261766>
```var s3 = new AWS.S3({signatureVersion: 'v4'});```

okay, thanks Herb, we'll take a look at this tomorrow, shouldn't be hard

I spoke to Jeremy about it, he was still looking into it

<@U034PEXGVU4> Does your AWS bucket policy require a specific signature version?  According to the docs, both v2 and v4 and allowed by default unless you restrict the signature version in the bucket policy. <https://docs.aws.amazon.com/AmazonS3/latest/API/bucket-policy-s3-sigv4-conditions.html>

I see, looks like v2 is deprecated and any new buckets created only support v4.  I'll update our api to use v4 when signing the url.

Just pushed.  New docker build will be available in about 10 minutes

Hi, <@U01TCPDB58C>  I can see you have made the change and it indeed use the v4 signed url. but I’m still got 400 error…

I’m wondering if something else I’m missing on our bucket

Yes, it’s through our selfhosted growthbook. the file is not uploaded to our s3 bucket.

this 400 request is mean to upload the file to s3. but got 400

if you want to DM me the S3 permissions/config, I can check it against our config

I am running into this exact issue, was there a solution to it?

yes, we solved it: <https://docs.growthbook.io/self-host#updating-to-latest>

<https://docs.growthbook.io/faq#i-cant-upload-to-s3getting-400-error-when-uploading-to-s3>