MediaCache AWS S3 not working

Wowza Streaming Engine
1

I had to set the amazons3 mediacache.

I typed both the Aws key and secret correctly, but the vod did not work properly.

So I changed both the bucket and the file to public and tested it, but it did not work either.

Is there anything I’m missing?

The s3 path on the log was normally accessible.

log:

WARN server comment 2017-07-04 02:09:02 - - - - - 48.465 - - - - - - - - MediaCacheItemHTTPImpl.getItemInfo[S3_LOCATION]: HTTP response: 400 WARN server comment 2017-07-04 02:09:02 - - - - - 48.465 - - - - - - - - MediaCacheItemBase.init: Item does not exist: MEDIA_FILE_NAME

2

I Have the exact same problem. Been trying to solve it for 3 days without any result. I’ve tried with both root keys and IAM users, no result. I set permissions to public, and can open the file on the browser, but not with Wowza. The sample URL is correct according to my S3 links, so there must be an error somewhere in Wowza.

3

Hi there,

I have exactly the same problem as Raehyeok and Jan.

Is there already a solution for this from Wowza side?

Version 4.7.1 does not fix the issue.

4

Hi,

I am facing the same issue in wowza 4.7.3. On the same wowza, it is able to play video that is stored in Amazon Singapore region, but is not able to play video stored in the mumbai region.

I have checked multiple times that accessKey and secret are correct. Also base path is also correct as per https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region

5

Hi,

I found a solution with the help of Wowza support.

You need to add two parameters in the MediaCache.xml configuration.

awsSigningVersion

4

Integer

awsDefaultRegion

eu-west-3

String

And for BasePath, I put “https://s3.amazonaws.com/”.

6

I have the same problem with 4.7.5.01. Your solution does not help. Actually nothing helps. Also tried to change base URL, bucket location, etc. Can open URLs in a browser, but media cache reports 400.

7

I had the same issue, send a ticket to wowza and they said “it is a known issue, you need to make your bucket public” with the bucket public, the streaming engine could retrieve the file and cached it.

8

Hi @Jon Remo,

The Support Team may have asked to make an S3 bucket publicly available as a quick test but using the proper AWS credentials your instance should be able to retrieve these files without having the content publicly available.

To help troubleshoot these issues, another thing we suggest to users is enabling the following property on your MediaCacheSource:

    <Property>
        <Name>debugHTTPRequests</Name>
        <Value>true</Value>
        <Type>Boolean</Type>
    </Property> 

Along with enabling the MediaCache / DebugLog as shown here:

<DebugLog>true</DebugLog>

Then after restarting WowzaStreamingEngine retry the playback and include a compressed copy of the latest /logs/wowzastreamingengine_access.log with your ticket information. This should help us narrow down the issues.

Best regards,
Andrew