# Using s3 storage in an on prem deployment

**URL:** <https://openvidu.discourse.group/t/using-s3-storage-in-an-on-prem-deployment/2914>\
**Category:** Issues with deployment\
**Tags:** v2\
**Created:** [April 8, 2021, 7:00pm UTC](https://openvidu.discourse.group/t/using-s3-storage-in-an-on-prem-deployment/2914 "2021-04-08T19:00:33Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![bart](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@bart](https://openvidu.discourse.group/u/bart)\
**Post date:** [April 8, 2021, 7:00pm UTC](https://openvidu.discourse.group/t/using-s3-storage-in-an-on-prem-deployment/2914/1 "2021-04-08T19:00:33Z")

</div>

Hello,

I’ve recently deployed an openvidu cluster using the autoscaling webhook on top of [https://scaleway.com/](https://scaleway.com/) and since Scaleway has support for the s3 protocol how can I configure the media nodes to use s3 to write their recordings?

Thanks,  
Bart

---

<div class="post-metadata">

**Author:** ![pabloFuente](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/pablofuente/32/2536_2.png) [@pabloFuente](https://openvidu.discourse.group/u/pabloFuente)\
**Post date:** [April 9, 2021, 8:56am UTC](https://openvidu.discourse.group/t/using-s3-storage-in-an-on-prem-deployment/2914/2 "2021-04-09T08:56:45Z")

</div>

Hello,

Please read the first lines of S3 recording documentation: [OpenVidu Docs](https://docs.openvidu.io/en/2.17.0/advanced-features/recording/#uploading-recordings-to-aws-s3)

You can enable it in any OPenVidu Pro deployment, doesn’t matter if it is an AWS deployment or an On Premises deployment.

Best regards.

---

<div class="post-metadata">

**Author:** ![bart](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@bart](https://openvidu.discourse.group/u/bart)\
**Post date:** [April 9, 2021, 9:18am UTC](https://openvidu.discourse.group/t/using-s3-storage-in-an-on-prem-deployment/2914/3 "2021-04-09T09:18:49Z")

</div>

Thanks, And where do I put the s3 url? I don’t see that as part of the configuration params:  
[https://s3.nl-ams.scw.cloud](https://s3.nl-ams.scw.cloud)

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [April 9, 2021, 8:01pm UTC](https://openvidu.discourse.group/t/using-s3-storage-in-an-on-prem-deployment/2914/4 "2021-04-09T20:01:31Z")

</div>

S3 protocol? You’re not using AWS? I’m not sure this would work with other S3 providers. Is this your case?

If you’re using AWS, you just need to put the S3 bucket name, not the URL

---

<div class="post-metadata">

**Author:** ![bart](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@bart](https://openvidu.discourse.group/u/bart)\
**Post date:** [April 9, 2021, 8:17pm UTC](https://openvidu.discourse.group/t/using-s3-storage-in-an-on-prem-deployment/2914/5 "2021-04-09T20:17:49Z")

</div>

@cruizba

Well S3 is more of a spec, and multiple cloud providers have implemented that spec. (Including Scaleway).

So instead of defining the bucket I would expect something like this:

OPENVIDU\_PRO\_AWS\_S3\_URL=https://s3.nl-ams.scw.cloud

> **[How to use Object Storage with AWS-CLI](https://www.scaleway.com/en/docs/object-storage-with-aws-cli/)**
>
> AWS-CLI is an Object Storage client. Learn how to use it with Scaleway.

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [April 9, 2021, 8:24pm UTC](https://openvidu.discourse.group/t/using-s3-storage-in-an-on-prem-deployment/2914/6 "2021-04-09T20:24:53Z")

</div>

Try this:

```auto
OPENVIDU_PRO_RECORDING_STORAGE=s3
OPENVIDU_PRO_AWS_ACCESS_KEY=<YOUR_ACCESS_KEY>
OPENVIDU_PRO_AWS_SECRET_KEY=<YOUR_SECRET_KEY>

OPENVIDU_PRO_AWS_REGION=nl-ams <--- I suppose this is the region
OPENVIDU_PRO_AWS_S3_BUCKET=<BUCKET_NAME> <--- Only the name, without protocols

```

Edit: I think this would not work because we did not consider the use case of other endpoint urls, this is actually a possible feature. Sorry for the inconvenience.

Maybe is there a way to set this variable with an environment variable, but it seems like it is not possible: [Feature: Configure Services' Endpoint URLs via Environment Variables · Issue #1239 · aws/aws-sdk-php · GitHub](https://github.com/aws/aws-sdk-php/issues/1239)

---

<div class="post-metadata">

**Author:** ![bart](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@bart](https://openvidu.discourse.group/u/bart)\
**Post date:** [April 9, 2021, 8:38pm UTC](https://openvidu.discourse.group/t/using-s3-storage-in-an-on-prem-deployment/2914/7 "2021-04-09T20:38:58Z")

</div>

No problem!

Yes I didn’t think you guys have this feature. Would be great to have this in a next release as part of a config property, would this be possible?

---

<div class="post-metadata">

**Author:** ![micael.gallego](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/micael.gallego/32/2_2.png) [@micael.gallego](https://openvidu.discourse.group/u/micael.gallego)\
**Post date:** [April 10, 2021, 7:51am UTC](https://openvidu.discourse.group/t/using-s3-storage-in-an-on-prem-deployment/2914/8 "2021-04-10T07:51:40Z")

</div>

Thank you for the sugestion, we will evaluate the feasibility of the feature.

Best regards

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [April 5, 2022, 5:25pm UTC](https://openvidu.discourse.group/t/using-s3-storage-in-an-on-prem-deployment/2914/9 "2022-04-05T17:25:56Z")

</div>

@bart, this is available in OpenVidu PRO/Enterprise since version 2.21.0 by using:

```auto
OPENVIDU_PRO_AWS_S3_SERVICE_ENDPOINT

```

For more info check the properties [here](https://docs.openvidu.io/en/2.21.0/advanced-features/recording/#uploading-recordings-to-s3)
