How to configure an external S3 bucket for recordings instead of the default MinIO#
By default, OpenVidu uses MinIO to store recordings. However, you can configure OpenVidu to use an external S3 bucket to store recordings.
In this example we will use AWS S3 with an S3 bucket named openvidu-recordings
in region us-east-1
.
Single Node deployment#
-
SSH into your Server and edit the file
/opt/openvidu/config/egress.yml
to add the following configuration: -
Restart OpenVidu Server:
Elastic and High Availability deployment#
-
SSH into all your Media Nodes and edit the file
/opt/openvidu/config/egress.yaml
to add the following configuration: -
Restart your Media Nodes:
If you are using v2compatibility
module, you also need to configure the openvidu-v2compatibility
service in your Master Node/s:
-
SSH into your Master Node/s and edit the file
/opt/openvidu/.env
to add the following configuration:V2COMPAT_OPENVIDU_PRO_RECORDING_STORAGE=s3 V2COMPAT_OPENVIDU_PRO_AWS_S3_BUCKET=openvidu-recordings V2COMPAT_OPENVIDU_PRO_AWS_S3_SERVICE_ENDPOINT=https://s3.amazonaws.com V2COMPAT_OPENVIDU_PRO_AWS_ACCESS_KEY=<YOUR_AWS_ACCESS_KEY> V2COMPAT_OPENVIDU_PRO_AWS_SECRET_KEY=<YOUR_AWS_ACCESS_SECRET> V2COMPAT_OPENVIDU_PRO_AWS_REGION=us-east-1
-
Restart your Master Node/s:
Info
If you are using v2compatibility
and you want to use a path in the bucket configuration, you need to set the V2COMPAT_OPENVIDU_PRO_AWS_S3_BUCKET
with the path included. It is not necessary to add the path in the egress.yaml
configuration.
For example: