Find your answers here.
AWS authentication access is currently not implemented for thumb_destination. Alternatively you can create a separate task with output=thumbnail to use this feature: To quote our API documentation: Instead of using thumb_ parameters within <format>, you can specify separate encoding task with output = thumbnail: <format> <!– Format fields –> Read more
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.
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 Read more
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 Read more