Custom S3 Endpoint.

[Daz Owens]

HI all,

I am trying to link AMS with a Digital Ocean space which is S3 Compatible.

Having a look through the source - I cant seem to see anywhere to set it.

There is a way to set a region and an endpoint by setting the region to the full endpoint. But this only works with AWS bucket urls like http://bucket.eu1-west.etc...

Any help would be very much appreciated.

Thanks,

Daz

[Mark Sergienko]

AntMedia supports HTTP forwarding to DigitalOcean:

Add this to settings:

settings.httpforwarding.baseURL=https\://****.sfo2.cdn.digitaloceanspaces.com

For upload simply use s3cmd v2. Configure it as described in DigitalOcean docs

then in your end muxing script:   

s3cmd sync $1 s3://**** --acl-public --add-header=Cache-Control:max-age=31536000

On Tuesday, 12 May 2020 09:57:22 UTC-4, Daz Owens wrote:

HI all,

I am trying to link AMS with a Digital Ocean space which is S3 Compatible.

Having a look through the source - I cant seem to see anywhere to set it.

There is a way to set a region and an endpoint by setting the region to the full endpoint. But this only works with AWS bucket urls like http://bucket.eu1-west.etc...

Any help would be very much appreciated.

Thanks,

Daz

[Daz Owens]

Absolutely spot on - got it uploading to a bucket now.

Curious - I need to send back the recording name. Do you know if there is a way i can get the recording name or set it via the REST API?

On Tuesday, 12 May 2020 15:16:57 UTC+1, Mark Sergienko wrote:

AntMedia supports HTTP forwarding to DigitalOcean:

Add this to settings:

settings.httpforwarding.baseURL=https\://****.sfo2.cdn.digitaloceanspaces.com

For upload simply use s3cmd v2. Configure it as described in DigitalOcean docs

then in your end muxing script:   

s3cmd sync $1 s3://**** --acl-public --add-header=Cache-Control:max-age=31536000

On Tuesday, 12 May 2020 09:57:22 UTC-4, Daz Owens wrote:

HI all,

I am trying to link AMS with a Digital Ocean space which is S3 Compatible.

Having a look through the source - I cant seem to see anywhere to set it.

There is a way to set a region and an endpoint by setting the region to the full endpoint. But this only works with AWS bucket urls like http://bucket.eu1-west.etc...

Any help would be very much appreciated.

Thanks,

Daz

[Benjamin Lowry]

I have a similar issue. I tried to follow the guidance here to add some XML configuration to red5-web.xml 

https://github.com/ant-media/Ant-Media-Server/wiki/Amazon-(AWS)-S3-Integration  

Since DigitalOcean is S3 compatible, I tried just adding the following, but no luck 

<property name="endpoint" value="{BUCKET}.{REGION}.digitaloceanspaces.com" />

It looks like support was added recently (21 May 2020)

https://github.com/ant-media/Ant-Media-Server-Common/commit/60c2ac09aad4cc3596c8085f7d9c5b422bb99eab#diff-af2cd3146936cd39c14422b63d289f75  

 

This integration looks simpler than using a user-defined muxerFinishScript, so I'd prefer being able to use that, if possible.

Do you know if it's possible to upgrade to a nightly version, or when a newer version will be released?

I'm currently using Ant Media Server Enterprise 2.0.0 (installed through one-click into Digital Ocean)