As a cloud service provider, one of the keys to our success is broad integration with other leading cloud service providers. As a matter of fact, our platform depends on integrations with other cloud services providers. One of the most critical areas of integration is with secure cloud storage for both ingest of source content and delivery of processed outputs for enterprise companies. For this reason Encoding.com offers support for every leading cloud storage solutions on the market. Let’s take a look at what’s supported. For more details on implementation, visit our API documentation.
Since Encoding.com is built on Amazon’s cloud infrastructure, S3 storage is a natural fit. Using Amazon S3 storage has a key benefit. Users automating their media workflows with our API can use the < nocopy > command so source content does not have to be transferred to our servers and processing can begin immediately. In addition, delivering outputs to S3 is extremely efficient because the data never leaves the Amazon network. For more details on S3 integration, please visit our API documentation.
Support for both Swift V1 and Swift V2 are available through our API. Swift is a highly available, distributed, consistent object based blob storage, and a core component of the OpenStack platform. Organizations can use Swift to store lots of data efficiently, safely, and cheaply.
To use this as your source or destination, use the following URL structures:
For Swift V1:
For Swift V2:
Cloud Files brings a powerful and easy way to publish content over a world-class, industry leading CDN. Cloud Files users automatically gets access to this network. Users simply have to mark containers for publishing to CDN and they are readily accessible through the Limelight Networks CDN. The propagation of content to the edge locations is done automatically behind the scene. This workflow is a perfect compliment to Encoding.com as encoded videos can be sent directly to CDN enabled Cloud Files containers automatically producing a HTTP streaming URL to the video. In The Rackspace web control panel, it is a matter of creating a Container (the storage compartment for data), uploading Objects (the files to serve over CDN), and marking the Container as “public”. The Container is then assigned a unique URL which can be combined with Object names to embed in web pages, email messages, blog posts, etc. For example, you could encode a video with Encoding.com and have it sent directly to a Container called “video”. When this Container is published, it will be assigned a unique URL like http://c0000532.cdn.cloudfiles.rackspacecloud.com You could then publish a CDN enabled public link like “http://c0000532.cdn.cloudfiles.rackspacecloud.com/my_movie.flv.”. When that link is accessed, the video is automatically streamed using HTTP progressive from the CDN.
For customers using Microsoft Azure blob storage we offer integration support for both source and destination. To use Azure storage just follow a few steps. Specify Microsoft Azure as your source or destination, then specify the Share Key (aka Primary Access Key), then specify the path to your source or destination, including the container name and the full file name. The path should look something like this:
access_key should be urlencoded
For customers using Akamai as their CDN we offer support for Akamai NetStorage. This speeds up the global distribution of your assets through network distribution points worldwide to ensure delivery viewers everywhere. Configuring NetStorage as your destination is easy.
The primary benefit of using Akamai NetStorage is for customers already using Akamai as their CDN. Akamai NetStorage speeds up the global distribution of your content by first uploading to two global network distribution points. From there they are rapidly distributed to a network of global endpoints in preparation for delivery to the end-user.
Using Akamai NetStorage as your destination with our API is easy. Specify your destination as part of your API request.
We also support YouTube as an output destination. Encoded videos can be delivered directly to your YouTube account. In your API request just include your credentials and relevant information, as seen in the snippet below.