Amazon S3
You’ll need to set the following CORS Configuration to your bucket:
<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
<AllowedOrigin>*PIMENTA_CHAT_DOMAIN*</AllowedOrigin>
<AllowedMethod>PUT</AllowedMethod>
<AllowedMethod>POST</AllowedMethod>
<AllowedMethod>GET</AllowedMethod>
<AllowedMethod>HEAD</AllowedMethod>
<MaxAgeSeconds>3000</MaxAgeSeconds>
<AllowedHeader>*</AllowedHeader>
</CORSRule>
</CORSConfiguration>
Important: Replace *PIMENTA_CHAT_DOMAIN* with the domain of your pimentaCHAT installation, e.g. https://chat.example.com. If for some reason you want to make your CORS configuration ridiculously insecure, you can set it to * to allow CORS requests from any host on the Internet, but do so at your own risk.
Basic configuration
You’ll need to set the following fields:
| Config. Name | Description |
|---|---|
| Amazon S3 bucket name | The bucket name you’ve created on Amazon S3 |
| Amazon S3 AWSAccessKeyId | Your Amazon Access Key ID (optional) |
| Amazon S3 AWSSecretAccessKey | Your Amazon Secret Access Key (optional) |
Note: If no AWSAccessKeyId and AWSSecretAccessKey are set, the underlying AWS SDK will fallback to trying to retrieve credentials from the usual locations.
Advanced configuration
The following fields are optional, you don’t need to set them to get upload to S3 working.
| Config. Name | Description |
|---|---|
| Region | If you have created your bucket on region different from the US Standard, you have to set their code here (see a list of region codes here) |
| Amazon S3 acl | A Canned ACL configuration (see a full list here) |
| CDN domain for downloads | If you had set a CDN for your bucket, put it here |
| Bucket URL | Override URL to which files are uploaded. This URL will also be used for downloads unless a CDN is given. |
