Wowza Community

Amazon S3 Media Cache Source Connectivity Issue

Hi there,

We’re having issues with connecting our Media Cache Source to our Amazon S3 Bucket in Seoul. We’ve previously had a bucket in Tokyo and that seemed to work fine, but are having issues with the new Seoul bucket.

These are my Media Cache Source settings:

Prefix: amazons3/

Base Path: https://s3.ap-northeast-2.amazonaws.com/

Use Amazon S3 bucket name in domain: false

Minimum Time To Live: 30 mins

Maximum Time To Live: 2 hours

We have also tried these alternative settings:

Prefix: amazons3/

Base Path: http://s3.amazonaws.com/

Use Amazon S3 bucket name in domain: true

Minimum Time To Live: 30 mins

Maximum Time To Live: 2 hours

Prefix: amazons3/

Base Path: https://s3.amazonaws.com/

Use Amazon S3 bucket name in domain: true

Minimum Time To Live: 30 mins

Maximum Time To Live: 2 hours

Prefix: amazons3/

Base Path: https://s3.amazonaws.com/

Use Amazon S3 bucket name in domain: false

Minimum Time To Live: 30 mins

Maximum Time To Live: 2 hours

We have confirmed the credentials work as I have used them with another application called Cyber Duck to connect to the Amazon S3 Bucket.

We connect the Media Cache Source to vod2 and access it via this URL https://our.domain.com/vod2/definst/mp4:amazons3/bucket-name/test.mp4/playlist.m3u8.

Any help would be much appreciated!

Cheers

+1

Same problem here…

Can anyone help us please?

Hi,

This would require us to review your configuration and logs files. Do send a support request with a zip copy of the following files from your Wowza installation.

  • conf/

  • logs/

Michelle

I’ve got the same problem.

I’m running in an EC2 instance so I’m not sure how to get those files to you. However: I tested my media source setup, and the test URL works in VLC.

Details for the “S3 Testmedia” source:

Given a bucket name of avstestmedia, and the Big Buck Bunny movie in a subfolder called media-player-testmedia, I went into the Media Source editor and entered the test path:

amazons3/avstestmedia/media-player-testmedia/sample.mp4

which generated the URL
http://avstestmedia.s3.amazonaws.com/media-player-testmedia/sample.mp4

This works in VLC.

In my VOD Edge application (called “vodedge”), I have set All Media Sources Are Available and “S3 Testmedia” appears below. Only dvrorigin is there besides.

In the Test Players view I went to Apple HLS tab. For the Application, I have “vodedge/definst”, and for the Media File Name I have “mp4:avstestmedia/media-player-testmedia/sample.mp4” .
when I click Start it just says:

The video could not be loaded, either because the server or network failed or because the format is not supported.

Suffixing playlist.m3u8 made no difference, and neither did omitting “definst

What am I missing here?

You’ll need to suffix the URL with /playlist.m3u8 (HLS) or /manifest.mpd (DASH). I forget, but VLC can only do one type and not the other. Overall your URL should look like the below,

(HLS: iOS/MacOS)
https://yourdomain.com/{VOD_APP_NAME}/_definst_/mp4:{MEDIA_CACHE_PREFIX}/{PATH_TO_VIDEO_IN_BUCKET}/{MP4_VIDEO_NAME}.mp4/playlist.m3u8

(MPD: Android/Chrome)
https://yourdomain.com/{VOD_APP_NAME}/_definst_/mp4:{MEDIA_CACHE_PREFIX}/{PATH_TO_VIDEO_IN_BUCKET}/{MP4_VIDEO_NAME}.mp4/manifest.mp

It’s also worth checking your /conf/MediaCache.xml file in the Wowza Streaming Engine folder.

For your node that is your S3 config, make sure you have the two settings set,

<Property>
   <Name>awsDefaultRegion</Name>
   <Value>ap-northeast-2</Value>
   <Type>String</Type>
</Property>
<Property>
   <Name>awsSigningVersion</Name>
   <Value>4</Value>
   <Type>Integer</Type>
</Property>

Replace ap-northeast-2 with the region your S3 bucket is located. Here is a list here, https://docs.aws.amazon.com/general/latest/gr/rande.html.

Hope this all helps.