Using Amazon S3 with the Watch Folder

AWS watch folders are a beautiful thing. Let's lay out a couple ground rules before we begin, shall we?

+ Make sure your destination is NOT a source location subfolder. You should NOT use /some_path/videos as a source and /some_path/videos/encoded as a destination unless you want an infinite loop.

+ The destination should be in a separate bucket or folder, ideally.

+ Do not use capital letters in your bucket names.

1) Specify the URL

You source and destination URLs would be: Ensure to add on your secret keys to the URL for the watchfolder, unless your buckets are public. In that case, it would look like this:

2) Set the bucket ACLs

To let read bucket contents and save the results, add UPLOAD and DELETE permission for the AWS user fastencoding (1a85ad8fea02b4d948b962948f69972a72da6bed800a7e9ca7d0b43dc61d5869). Please no not use 'fastencoding' as is, use the long string, as it will resolve to the user fastencoding. 
If you use separate buckets for source and destination, note that you destination bucket MUST have READ permission as well as WRITE (upload/delete), in order for to verify the results of the file delivery.

3) Specify output file permissions

By default, results saved by have READ permission for all authenticated AWS users. What if we need to share results with the other users, or make the file visible to the web? To make set READ permission for ALL users, just add ?acl=public-read to the end of your destination URL:

Now your files are accessible though HTTP for browser viewing. You can now use the URL of the file to view the video and share with other users. 

4) Specifying your AWS credentials.

Sometimes you may need the result files saved to your bucket by to have permissions for a specific user, such as yourself. In this case you can specify your AWS Access Key and Secret Access Key in the URL. You won't need to add any permissions to the bucket in this scenario:

Say the Access Key and the Secret Access Key are:
lQT5MsQLirc8owb:SxX/9EhU4MQarasFelQ0v2M. First, we must percent-encode the Secret Access Key, as it contains the special URL characters: ':' and '/'. The percent-encoded Secret Access Key is:

Once the Secret Access Key is properly percent-encoded, it can be added to the address string, the destination URL would look like this:

Please contact Support if you are experiencing any issues building your S3 workflow.

1 Star2 Stars3 Stars4 Stars5 Stars (63 votes, average: 4.37 out of 5)