Find your answers here.
If you are used to setting permissions in Amazon buckets, you're probably familiar with S3's style of ACL usage appended to the source URLs. In Rackspace, no URL defined permissions exist. The way to set public versus private permissions is via containers. Public: Select 'Publish to CDN' in the container properties. This creates a link Read more
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 Read more
The error message ECOM00221 translates to “S3 download error: The specified key does not exist” It appears that your Amazon key is not being recognized as valid. Please check the content of the string you entered and see if it is valid. Also, please make sure that the key that you are using Read more
The error message ECOM00208 translates to “Error accessing S3 file” It appears that the correct permissions were not exacted upon the destination folder. Please also check to see if the specified destination bucket exists. You can read all about S3 Amazon permissions for destinations at this Knowledge Base article: http://edchelp.wpengine.com/idx.php/9/032/Amazon-S3-Integration/article/Setting-permissions-for-Amazon-S3-bucket-delivery-from-encodingcom.html
The error message ECOM00207 translates to “Error putting file to S3” It appears that the correct permissions were not exacted upon the destination folder. Please also check to see if the specified destination bucket exists. You can read all about S3 Amazon permissions for destinations at this Knowledge Base article: http://edchelp.wpengine.com/idx.php/9/032/Amazon-S3-Integration/article/Setting-permissions-for-Amazon-S3-bucket-delivery-from-encodingcom.html
The error message ECOM00204 translates to “S3 Upload Error: Access denied” When you encounter this error, the first step that you must take it to verify that the S3 destination bucket has granted write permission for AWS user fastencoding. Please view the knowledge base article on S3 delivery for further explanation: http://edchelp.wpengine.com/idx.php/9/032/Amazon-S3-Integration/article/Setting-permissions-for-Amazon-S3-bucket-delivery-from-encodingcom.html
With TAR output is set to OFF, and should see .m3u8 pointers and .ts segment files populate your output directory. The trick is correctly formatting the output filepath. You have to make sure your output filepath has a filename WITHOUT a 3-character file extension. I had this same problem because I either defined only the Read more
Please send your API requests to manage.encoding.com at 52.200.5.10 Notification posts are coming from 34.193.0.100 Port Assignments FTP on port 21 SFTP on port 22 HTTP on port 80 HTTPS on port 443 AWS Amazon has a very sophisticated system in place for managing IP ranges across their infrastructure. Everything you need to know about 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.