# Amazon S3 Media Cache Source Connectivity Issue

**URL:** <https://community.wowza.com/t/amazon-s3-media-cache-source-connectivity-issue/47119>\
**Category:** Wowza Streaming Engine\
**Created:** [June 3, 2016, 7:47am UTC](https://community.wowza.com/t/amazon-s3-media-cache-source-connectivity-issue/47119 "2016-06-03T07:47:49Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Phillip\_Moon](https://avatars.discourse-cdn.com/v4/letter/p/a8b319/32.png) [@Phillip\_Moon](https://community.wowza.com/u/Phillip_Moon)\
**Post date:** [June 3, 2016, 7:47am UTC](https://community.wowza.com/t/amazon-s3-media-cache-source-connectivity-issue/47119/1 "2016-06-03T07:47:49Z")

</div>

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/](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/](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/](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/](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](https://our.domain.com/vod2/_definst_/mp4:amazons3/bucket-name/test.mp4/playlist.m3u8).

Any help would be much appreciated!

Cheers

---

<div class="post-metadata">

**Author:** ![Anand\_Selvadurai](https://avatars.discourse-cdn.com/v4/letter/a/839c29/32.png) [@Anand\_Selvadurai](https://community.wowza.com/u/Anand_Selvadurai)\
**Post date:** [June 15, 2016, 1:30pm UTC](https://community.wowza.com/t/amazon-s3-media-cache-source-connectivity-issue/47119/2 "2016-06-15T13:30:38Z")

</div>

+1

Same problem here…

Can anyone help us please?

---

<div class="post-metadata">

**Author:** ![Michelle\_B](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/michelle_b/32/394_2.png) [@Michelle\_B](https://community.wowza.com/u/Michelle_B)\
**Post date:** [June 23, 2016, 12:50pm UTC](https://community.wowza.com/t/amazon-s3-media-cache-source-connectivity-issue/47119/3 "2016-06-23T12:50:32Z")

</div>

Hi,

This would require us to review your configuration and logs files. Do send a [support request](https://www.wowza.com/support/open-ticket) with a zip copy of the following files from your Wowza installation.

- conf/

- logs/

Michelle

---

<div class="post-metadata">

**Author:** ![Mike\_Jennings](https://avatars.discourse-cdn.com/v4/letter/m/a9adbd/32.png) [@Mike\_Jennings](https://community.wowza.com/u/Mike_Jennings)\
**Post date:** [July 11, 2018, 7:40am UTC](https://community.wowza.com/t/amazon-s3-media-cache-source-connectivity-issue/47119/4 "2018-07-11T07:40:19Z")

</div>

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](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?

---

<div class="post-metadata">

**Author:** ![Phillip\_Moon](https://avatars.discourse-cdn.com/v4/letter/p/a8b319/32.png) [@Phillip\_Moon](https://community.wowza.com/u/Phillip_Moon)\
**Post date:** [July 11, 2018, 7:01pm UTC](https://community.wowza.com/t/amazon-s3-media-cache-source-connectivity-issue/47119/5 "2018-07-11T19:01:43Z")

</div>

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,

```auto
(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

```

---

<div class="post-metadata">

**Author:** ![Phillip\_Moon](https://avatars.discourse-cdn.com/v4/letter/p/a8b319/32.png) [@Phillip\_Moon](https://community.wowza.com/u/Phillip_Moon)\
**Post date:** [July 11, 2018, 7:04pm UTC](https://community.wowza.com/t/amazon-s3-media-cache-source-connectivity-issue/47119/6 "2018-07-11T19:04:40Z")

</div>

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,

```auto
<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](https://docs.aws.amazon.com/general/latest/gr/rande.html).

Hope this all helps.
