S3
You are able to add your preferred S3 provider, like AWS, DigitalOcean, Exoscale or Infomaniak. However, if you don't
want to store your files on a S3 bucket, you don't have to. Consider that this feature is DISABLED per default.
Configuration
You can configure your S3 provider and bucket by going to the configuration page in your admin dashboard /admin/config/s3.
| Key | Description | Value |
|---|---|---|
| enabled | This property enables the storage location on your configured S3 bucket. | true |
| endpoint | The host for your S3 bucket. Endpoint formats vary by provider and some may include the bucket name in the FQDN. Ensure this is configured correctly, as an incorrect value may break some features. | sos-ch-dk-2.exo.io |
| region | This property is the region where the bucket is located. | sos-ch-dk-2 |
| bucketName | This property is the name of your S3 bucket. | my-bucket |
| bucketPath | This property defines the folder where you want to store your files which are uploaded. Hint: Don't put a slash in the start or end. | my/custom/path (or leave it empty for root) |
| key | This is the access key you need to access to your bucket. | key-asdf |
| secret | This is the secret you need to access to your bucket. | secret-asdf |
Don't forget to save the configuration. :)
ClamAV
When S3 is used in conjunction with ClamAV, the file is first uploaded to the S3 bucket, then downloaded temporarily by the backend server, scanned by ClamAV then removed from the backend and actioned. This can lead to increased scanning times, especially for larger files, due to the additional upload and download steps. If you are experiencing slow scanning times, consider disabling S3 or ClamAV.
ZIP
Creating ZIP archives is not currently supported if you store your files in an S3 bucket.