Allow configuring the S3 endpoint, region, and other parameters

[paride]

In the Amazon S3 yml configuration read and use the following parameters, here shown with sample values:

s3:
  endpoint: https://my-host.net/
  region: us-east-1
  pathStyleAccess: true
  signerAlgorithm: AWSS3V4SignerType

Being able to specify them allows to self-host an S3 service. The aws-sdk has been updated too, removing the calls to some deprecated methods.

[gine]

it can be useful

[ZennouRachid]

@paride Hi, i want to use minio for self-host an S3 service
my yml file configuration look like this:
s3:
accessKey: 1PAVK1425juiUAH
accessSecret: inhoKJSHDUIIrichskiY7Fpc9
attachmentsBucket: bucket
endpoint: http://127.0.0.1:9000
region: us-east-1
pathStyleAccess: true
signerAlgorithm: AWSS3V4SignerType
but it doesn't work, when i try to send an attachment the signal application give my this error "signal has stoped" .
do youi have an idea?

[vadmeste]

Hey @paride,

Could you update us on the current status of this PR ?

A fast test of this PR shows that Signal-Server doesn't contact the Minio server at all. Even when I replace Minio with nc -l -p 9000, this latter doesn't receive any data.

Regards,

[paride]

@vadmeste It's working fine for me. Normally it is the client that contacts the S3/Minio server, Signal-Server just builds a "Signed Url" that the client then uses to upload the attachment. Of course if you use endpoint: http://127.0.0.1 the client won't be able to contact it.

Edit: https://docs.aws.amazon.com/AmazonS3/latest/dev/PresignedUrlUploadObject.html