AWS S3 Bucket - 403 Signing Error.

[AyJayHam]

Hi, I am actually also facing issues when setting up Codalab with amazon s3 bucket.

I do get an 403 error as well. Digging into the requests I was able to find out that the reason i get this error is that Amazon throws. an error:The request signature we calculated does not match the signature you provided. Check your key and signing method. - which comes with the 403.

My .env file is set up correctly with the IAM user and the initial requests are successfully going through. But once Codalab tries to store the zip competition bundle file in the bucket the signing fails.

My env:

I looked through #3054 but it did not help.

It might have something todo with the boto3 being used.

Happy for any help!

[AyJayHam]

I was able to resolve my issue.
The error was related to the AWS-S3_HOST. It needs to be without the region as given in the example file.

For having it working self hosted however 2 things still need to be updated:

1. the rabbitmq docker image needs to be set to a newer version as otherwise installation fails
2. the max_size for image_url_base in the django model files needs to be increased as the generated amazon urls which are pasted into that field when using s3 will have more than 350 chars.

[Didayolo]

Glad to hear you could solve your issue!