Wowza Community

Storing streamfiles in S3 bucket for multiple EC2 instances

I want to use multiple AWS instances for wowza streaming engine. So I want to put my stream files in shared location among multiple instances like S3 bucket.

I didn’t find any way to store stream files in S3 bucket and one more option I tried is to mount S3 bucket on EC2 disk storage but due to change in permission by s3, I am unable to use it.

Would you please suggest a way to store streamFiles in shared location which can be used by multiple EC2 instances?

Do you have the permissions set to “public” for your S3 buckets and for the files when you upload them to the buckets? That’s the only way Wowza can access them if they are a publicly readable object.

I’m not sure what you mean by this? Can you explain? “…but due to change in permission by s3, I am unable to use it.”

Perhaps this article will help you?

Use Amazon S3 authorization with Wowza Streaming Engine EC2 instances

Wowza Media Systems™ provides Amazon Linux and Windows AMIs with preconfigured and tuned versions of the Wowza Streaming Engine™ media server software that are ready to start using the Amazon Web Services (AWS) Management Console. The Wowza Streaming Engine AMIs have three applications: live , vod , and vods3 .

By default, the vods3 application is configured with S3 authorization turned off. This means that all content must be publicly available. To stream non-publicly available content, modify the Media Cache configuration in Wowza Streaming Engine Manager.

  1. Enter the following URL in a web browser to connect to Wowza Streaming Engine Manager:http://[ public-domain-name ]:8088/enginemanagerReplace [ public-domain-name ] with the Public DNS value for the instance. For more information, see Get the instance public domain name and ID. (The steps are the same for Windows and Linux instances.)
  2. Sign with the user name wowza and a password. The password is the Instance ID .
  3. In Wowza Streaming Engine Manager, click the Server tab at the top of the page, and then click Media Cache in the contents pane.
  4. On the Media Cache page, on the Sources tab, and click the Edit (pencil) icon for amazons3 source.
  5. Enter your AWS Access Key ID and AWS Secret Access Key , and then click Save .

You can now re-stream protected content using the vods3 application.

Another suggestion from an engineer here at Wowza @Pankil_Thakkar is to use this- it’s 3rd party, but you can sync files locally that live on S3.