Want to use S3 as a source location for your material, but you don't want to hand out secret or access keys? Give this a try! Use your canonical ID at the end of the URL string to pass the ownership from Encoding.com to yourself. Alternately, give your source location access via Encoding.com's canonical ID so that we have access to your files. 

Here's a few scenarios of where canonical IDs come into play with our platform.

+ To send us source videos, without passing keys, ensure that you are giving Encoding.com's canonical ID full access on the destination bucket through the S3 interface. Here's how to accomplish that:

1) Select the bucket you wish to source from in the S3 console. Right click on it and select 'Properties'

2) Under the Permissions tab at the bottom, select the plus button and grant upload/delete access to Encoding.com. Our ID is: 1a85ad8fea02b4d948b962948f69972a72da6bed800a7e9ca7d0b43dc61d5869.  Once you have entered this ID, it will resolve to fastencoding in a few seconds. Just hang in there. This allows Encoding.com to use its credentials to pull your source files on that particular bucket.

+ To deliver files from Encoding.com to your bucket and make ownership solely yours, please use the following syntax for your destination URLS:

http://your_bucket.s3.amazonaws.com/path/file.ext?acl=private-read&canonical_id

Sample of what an actual canonical S3 output path looks like:

http://mybucket.s3.amazonaws.com/video/output/clive_waterski.mp4?acl=private-read&canonical_id=5ecaabaxaf9da27db13630cedde7f7a652d00a63f3407aa4c21c318d6bdf2dc0

Once this passes into the system, the canonical ID will be restricted from view. Neat, huh? 

Here's an example of what we see on our end:

http://ksc.target.s3.amazonaws.com/test.flv?acl=private-read

(6 votes, average: 3.00 out of 5)

Loading...