Amongst our full list of integration methods for your transcoding workflow, Amazon’s cloud storage solution, S3, is one of our most popular. We’ve put together these tips, based on customer feedback, to get you integrated, transcoding, and on your way.
1) In order for S3 input/output to work, you will need your AWS keys. You can get these from the Account -> Security Credentials section of the AWS Console.
2) We have enabled secure SSL for S3, using the same syntax with a https:// path. Please note all SSL transfers take twice as long, due to processing overhead.
3) Please make sure your destination is NOT a source location subfolder. Our watch folder UI prevents this, since it would be an infinite loop of encoding jobs.
4) Please do not use capital letters, spaces, periods/dots [.] or underscores in your S3 bucket names. Please keep it simple to minimize DNS CNAME errors.
5) If you have special characters in your AWS keys (like a plus symbol [+] or slash [/]) you will need to percent-encode them. For example, a plus symbol would be %2B and a slash is %2F
6) Please start your testing with just a few files. Don’t put a hundred videos in your source folder until you know you are happy with the settings you are using!
Amazon S3 Source Path (Private Option):
(“nocopy" flag allows instant read by EC2 encoders, reducing encoding time)
Amazon S3 Output Path (Private Owner):
(view permissions defined as public at file level with “public-read" flag)
Example from our Support Team (changed the keys, just so you know what it should look like):
Above, we have examples of a URL that supports delivery to a private bucket through the usage of the security credentials. It also supports public viewing of the file, sans credentials, due to the use of the public-read flag. This is a well-used workflow to deliver content to a protected bucket, yet still make it available to adoring fans. Please let us know how it goes! Our support team is available 9-5/PST.