Setting up for streaming from CloudFront with Encoding.com is easy. Once you've enabled your clips for access by authenticated users or public use, follow these steps in the AWS console under CloudFront:

1 - Create a new Distribution. Set the delivery method to 'Download' - Selecting 'streaming' will not work for this workflow 

2 - Customize the next screen, or just click 'Continue' / 'Create Distribution'

3 - Deliver as normally to the bucket specified for CloudFront and you're ready to go.

For more information on CloudFront streaming, please see AWS's documentation here: http://aws.amazon.com/cloudfront/

Save some time with your encodes with this simple step, if you are sourcing from S3, try this URL formatting:

http://[AWS_KEY:AWS_SECRET@][bucket].s3.amazonaws.com/[filename]?nocopy

if 'nocopy' is specified at the end of your URL, the source file will be downloaded directly from your bucket, thus saving time. Please use this only if your buckets are located in the US. If ?nocopy is not specified at the end of your URL, the source will be copied to Encoding.com bucket first. This workflow saves you traffic in the case of non-US buckets and more than one encoding task per source.

Want to only process certain files in your watchfolders?  Use our masking controls in the watchfolder UI. Good stuff!

+ Select 'Watchfolder' --> 'Add New' in the UI

+ Under the 'File Name Control' field, add in the type of content you WANT to process. For example, if you want to process only .mp4 content, then the masking field would contain, '*.mp4.' Add in multiple files types if you like!

+ Please note this functionality is only for file types, and not file names.

Have a lot of files that you need encoded quickly? No worries. Rather than upload the 400 terabytes of content, ship your drives directly to Amazon and place them on your S3 account. Don't have an S3 account? Sign up for one here. It's quick and painless, I promise. 

---

Prerequisites:

+ Make sure you have our secret key and access key ID in hand.  The website lays out the directions pretty good from here on out. You'll be asked to create SIGNATURE file & MYMANIFEST.txt

+ Make sure device conforms to S3 Standards. View 'Shipping Your Storage Device':

http://docs.amazonwebservices.com/AWSImportExport/latest/DG/index.html?CHAP_GettingSetUp.html

+ Please note that the Getting Started guide contains lots of other information in there, such as how to exclude directories, so make sure to read through the entire guide '

--

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

Yes! Give this a try if you're wanting to incorporate these into your integration method.
 

This policy will allow CloudFront to gain access to private content. 

{ 
"Version":"2008-10-17", 
"Id":"PolicyForCloudFrontPrivateContent", 
"Statement":[{ 
"Sid":" Grant CloudFront Origin Identity access to private content", 
"Effect":"Allow", 
"Principal":{ 
"AWS":"arn:aws:iam::cloudfront:user/CloudFront Origin Access Identity PRIVATE" // This is the origin ID specific to our account. 
}, 
"Action":"s3:GetObject", 
"Resource":"arn:aws:s3:::bucketname/*" 
} ]
}

You've read all the help articles, you've done your homework, and S3 is still giving you grief.  

Check this one simple thing, and it should help you with your final issues.

Does your source or destination URL look like this:

http://[your_accesskey_code]:[your_secretkey_code]@CLIVETHEGOAT.s3.amazonaws.com/path

Amazon AWS does not recognize capital letters of bucketnames (the part after the @). Change that puppy to this:

http://[your_accesskey_code]:[your_secretkey_code]@clivethegoat.s3.amazonaws.com/path

If all is still not well, drop us a line at helpdesk@encoding.com and we'll help you solve your issue with this.

Encoding.com offers proven S3 video integration solutions. Amazon Web Services (AWS) comprises a series of remote computing/web services that make your life easier. Infinitely scalable and use AWS with Encoding.com to create a workflow with storage locations and services accessed via HTTP.

Use Encoding.com for all of your cloudfront streaming needs. Amazon’s S3 Interface can be used seamlessly with Encoding.com’s compression platform for usage as either as source or destination.

Using Amazon S3 is a snap. Follow these directions to get you started

1) Manually set the Amazon S3 object to have READ permission for the AWS user fastencoding: 1a85ad8fea02b4d948b962948f69972a72da6bed800a7e9ca7d0b43dc61d5869 This is a requirement for encoding.com to read the file(s).  
To do this, log into your AWS console, right click on the bucket and select 'Properties' Add the string and wait for a moment, as it resolves to 'fastencoding'. Give this user upload/delete permissions.

2) Use the following format for the source url: http://[bucket].s3.amazonaws.com/[filename] Amazon provides some excellent documentation about ACL permissions, visit this link for details:

http://docs.amazonwebservices.com/AmazonS3/latest/dev/

Important notes: 

**We do not currently support Amazon EU/AP/Toyko buckets 

**Do not use capitalization in your bucket names. You will receive a 403 error. Please only use lowercase letters.

The “Content-Type” of a video is an important and in most cases required MIME type for streaming video. Amazon S3 simply echos back whatever MIME type you send when you upload the file. You can set the content-type parameter of a video before sending it to Amazon by appending &content_type= to your S3 destination, for example: http://dbucketname.destination.s3.amazonaws.com/no_ext_file_with_cont_type?acl=public-read&content_type=video/mp4 Note: For .3gp files: Use content_type=video/3gpp For .flv files: Use content_type=video/x-flv We are still looking into a way to set this as a batch server side, such as you would configuring an FTP directory. For now, the Amazon S3 web user interface does allow you to individually modify the properties of each file. Select the file, view Properties, then click the Metadata tab at the bottom. Type in the new value, then click the Save button to apply the new MIME type to the file.

We use both Amazon EC2 and Rackspace Cloud for our video processing.
Notification HTTP posts are coming from 67.192.242.205 or 67.192.242.206
API requests are sent to manage.encoding.com at 67.192.243.9

Port Assignments

FTP on port 21
SFTP on port 22
HTTP on port 80
HTTPS on port 443

Amazon EC2 (updated May 2011)

Please refer to AWS forum post https://forums.aws.amazon.com/ann.jspa?annID=1030 for more details.

US East (Northern Virginia)

216.182.224.0/20 (216.182.224.0 - 216.182.239.255)
72.44.32.0/19 (72.44.32.0 - 72.44.63.255)
67.202.0.0/18 (67.202.0.0 - 67.202.63.255)
75.101.128.0/17 (75.101.128.0 - 75.101.255.255)
174.129.0.0/16 (174.129.0.0 - 174.129.255.255)
204.236.192.0/18 (204.236.192.0 - 204.236.255.255)
184.73.0.0/16 (184.73.0.0 – 184.73.255.255)
184.72.128.0/17 (184.72.128.0 - 184.72.255.255)
184.72.64.0/18 (184.72.64.0 - 184.72.127.255)
50.16.0.0/15 (50.16.0.0 - 50.17.255.255)
50.19.0.0/16 (50.19.0.0 - 50.19.255.255)
107.20.0.0/15 (107.20.0.0 - 107.21.255.255) NEW

US West (Northern California)

204.236.128.0/18 (216.236.128.0 - 216.236.191.255)
184.72.0.0/18 (184.72.0.0 – 184.72.63.255)
50.18.0.0/16 (50.18.0.0 - 50.18.255.255) NEW

EU (Ireland)

79.125.0.0/17 (79.125.0.0 - 79.125.127.255)
46.51.128.0/18 (46.51.128.0 - 46.51.191.255)
46.51.192.0/20 (46.51.192.0 - 46.51.207.255)
46.137.0.0/17 (46.137.0.0 - 46.137.127.255)
46.137.128.0/18 (46.137.128.0 - 46.137.191.255) NEW

Asia Pacific (Singapore)

175.41.128.0/18 (175.41.128.0 - 175.41.191.255)
122.248.192.0/18 (122.248.192.0 - 122.248.255.255)
46.137.224.0/19 (46.137.224.0 - 46.137.255.255) NEW

Asia Pacific (Tokyo)

175.41.192.0/18 (175.41.192.0 - 175.41.255.255)
46.51.224.0/19 (46.51.224.0 - 46.51.255.255)

Rackspace Cloud Servers

204.232.192.* - 204.232.207.*
173.203.194.* - 173.203.223.*
174.143.152.* - 174.143.173.*

S3 Storage Access

Almost every corporate firewall will allow outgoing access to the web at ports 80 and/or 443, or via an HTTP/HTTPS proxy. Can you access https://s3.amazonaws.com from behind the firewall? If so, you can access S3 storage.

Localization

For specific access at a corporate location behind a firewall needing an IP range, please try these steps.

1. From a command prompt use dig or nslookup to lookup an IP for s3.amazonaws.com

2. Take the IP you get (I get 207.171.187.117) and run a whois query on it. If you aren't on a system that has whois installed there are several websites that provide it, including Network Solutions at http://www.networksolutions.com/whois/index.jsp

3. On there you will see the range of IP addresses Amazon owns around the IP that you found. So for me, when I whois the above IP the following result comes back:

"Amazon.com, Inc. AMAZON-01 (NET-207-171-160-0-1) 207.171.160.0 - 207.171.191.255"

NOTE: s3.amazonaws.com is a CNAME for s3-1.amazonaws.com and s3-2.amazonaws.com

The two ranges of IPs I see assigned for these are:
72.21.192.0 - 72.21.223.255
207.171.160.0 - 207.171.191.255

You might get completely different IP ranges based on where you are in the world. Just follow these steps to localize.

Amazon access permissions are set by the user who creates the object. By default, when Encoding.com sends a encoded file to a user's Amazon S3 bucket it sets the permissions of this file to authenticated-read. 

If you want your file to be public readable, add ?acl=public-read to your destination URL, like this:

http://your.bucket.s3.amazonaws.com/folder/file.ext?acl=public-read

This will allow you to share your file with all web users - the file is accessible via this URL:

http://your.bucket.s3.amazonaws.com/folder/file.ext.

 If otherwise, you don't want to share your file with anybody, you can make encoding.com to save your file using specific Amazon credentials. In this case you have to specify your AWS Access Key and Secret Access Key in your destination URL:

http://AWS_KEY:AWS_SECRET@your.bucket.s3.amazonaws.com/fooder/file.ext

The file is now accessible only by that user.  If the user wants to own the destination file and grant permissions for it, specify both AWS credentials and the ACL:

http://AWS_KEY:AWS_SECRET@your.bucket.s3.amazonaws.com/fooder/file.ext?acl=authenticated-read

Also note, we must percent-encode (URL escaping - see the full help article here) the Secret Access Key, as it contains the special URL characters: ':' and '/'. The percent-encoded Secret Access Key is:

lQT5MsQLirc8owb%3ASxX%2F9EhU4MQarasFelQ0v2M

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

http://1ZG3YAKJ8W0VOA9L7WT6:lQT5MsQLirc8owb%3ASxX%2F9EhU4MQarasFelQ0v2M@encode.video.s3.amazonaws.com/v/encoded/

Encoding.com was developed to work seamlessly with the Amazon S3 storage service as either the source location of your video library or the destination location where we send videos after encoding is complete. A basic understanding of Amazons ACL permissions is recommended and we would highly recommend reading through our articles on integrating Amazon S3 with encoding.com **Please note we do not currently support all of the Amazon EU buckets.

As a source media you must specify an URL that could be of three types:
1) http://[user]:[password]@[server]/[path]/[filename] or
2) ftp://[user]:[password]@[server]/[path]/[filename] or
3) http://[your_bucket].s3.amazonaws.com/[path]/[filename]
You can omit [user]:[password]@ in case of public (not password protected) resources. In last case, the bucket must have READ permission for AWS user 1a85ad8fea02b4d948b962948f69972a72da6bed800a7e9ca7d0b43dc61d5869.

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.

--> We do not currently support EU buckets.

Let's proceed with using the bucket name 'encode.video bucket' & /v/source and /v/encoded as source and destination prefixes accordingly.


1) Specify the URL

You source and destination URLs would be:
http://encode.video.s3.amazonaws.com/v/source/
http://encode.video.s3.amazonaws.com/v/encoded. 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:

http://your_accesskey_code:your_secretkey_code@encode.video.s3.amazonaws.com/v/source/


2) Set the bucket ACLs

To let Encoding.com 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 Encoding.com to verify the results of the file delivery.

3) Specify output file permissions

By default, results saved by Encoding.com 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 Encoding.com set READ permission for ALL users, just add ?acl=public-read to the end of your destination URL:


http://encode.video.s3.amazonaws.com/v/encoded/?acl=public-read


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 Encoding.com 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:
1ZG3YAKJ8W0VOA9L7WT6
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:


lQT5MsQLirc8owb%3ASxX%2F9EhU4MQarasFelQ0v2M


Once the Secret Access Key is properly percent-encoded, it can be added to the address string, the destination URL would look like this:
http://1ZG3YAKJ8W0VOA9L7WT6:lQT5MsQLirc8owb%3ASxX%2F9EhU4MQarasFelQ0v2M@encode.video.s3.amazonaws.com/v/encoded/

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