Results 1 to 3 of 3

Thread: VODS3 Authorization recorded files

  1. #1

    Default VODS3 Authorization recorded files

    Hi,

    I'm trying to use VODS3 to view streams which are recorded in an S3 bucket. The bucket does not have any permissions. I have also not set the AWSAccessKey and AWSSecretAccessKey values in Server.xml. However, when I try to play the recorded flvs, the streams play. They should not be playing if i have not set the secret access keys in server.xml.
    I'm not sure why these recorded files are playing, but this is not the required behaviour as these should play only when I've set the server.xml.
    I presume this is what they mean when they say "By default the vods3 feature is configured with S3 authorization turned off".
    Also, this happens for recorded files only. If I try to play files which have not been recorded, it correctly says "Stream not found."

    Is there something I've missed with vods3 authorization or could this be an issue for recorded files?

  2. #2
    Join Date
    Dec 2007
    Posts
    25,641

    Default

    Double check the ACL permissions of the bucket and the items.

    From the EC2 guide:

    By default the vods3.zip startup package is configured with S3 authorization turned off. This
    means that all content must be publicly available. To stream non-publicly available content, unzip
    the vod3s.zip startup package and modify the two system properties “awsAccessKeyId” and
    “awsSecretAccessKey” in “wowza/conf/Server.xml”. Set these two values to the “Access Key
    ID” and “Secret Access Key” for the user in which you would like to authorize access and zip up
    the vods3 folder. Use this new zip archive as your startup package. For example:
    <Property>
    <Name>awsAccessKeyId</Name>
    <Value>11DV8PNKTHN1234732</Value>
    </Property>
    <Property>
    <Name>awsSecretAccessKey</Name>
    <Value>p0fsdFIE1Nofyx5Sfe+CmuQi0uXt7ygrD8Xxz+</Value>
    </Property>
    The default setup is such that any content in S3 that is publicly available can be re-streamed
    through your instance. To limit the content to specific buckets you can use the stream alias
    system to add aliases for the buckets from which you would like to stream. The stream alias
    package has been included with the vods3.zip startup package. To modify the default
    configuration edit the file “wowza/conf/StreamNameAliasMap.txt” that is included in the
    vods3.zip startup package and create a new startup package with the modifications.
    Richard

  3. #3

    Default

    Hi Richard,

    We figured out the reason this was happening was because the s3 bucket was mounted. It does not restream the recording if the bucket is unmounted and the s3 access key is not specified.

    Thanks for your help.

    Regards.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •