We recently launched our ground-breaking Reserved Cloud for cloud media processing. This marks the first time a truly unmetered solution has been offered for media processing in the cloud. Customers can enjoy dedicated, single-tenant, unlimited encoding resources for a fixed monthly cost. They also have the option to seamlessly burst into our on-demand processing when Reserved Cloud reaches capacity. The solution is tightly integrated with Amazon Web Services, ensuring the highest levels of security, stability, and uptime. Most importantly, customers have complete visibility and control of their media processing workflow.
As with any of our solutions, Reserved Cloud combines robust media processing capabilities with a streamlined and mature API and UI. This allows teams to ramp up their workflows in minutes rather than hours or days. In this blog post we’ll provide a high level overview of managing Reserved Cloud.
This first two images show customer usage on a Reserved Cloud account. You’ll notice a straight horizontal orange line across the graph. This represents the capacity of a Reserved Cloud instance. Anything over that line is either jobs queuing (represented in grey in figure 1) or jobs being sent to our on-demand infrastructure (represented in red in figure 2).
Figure 1 – This shows jobs queuing when Reserved Cloud capacity is reached.
Figure 2 – This shows job bursting seamlessly into on-demand infrastructure when Reserved Cloud capacity is reached.
The next image shows a customer encoding queue that is using Reserved Cloud. This is exactly like our on demand queue, but jobs that are using Reserved Cloud are indicated in the job status column.
Figure 3 – This is shows jobs being processed by Reserved Instances
Enabling Reserved Cloud is just as easy. Reserved customers will have an extra tab in the Encoding.com UI for ‘Reserved Cloud Settings’. You have control over the following settings:
1) Enable Failover – This is a simple toggle to enable failover to on-demand infrastructure when capacity is reached on the Reserved Cloud.
2) Failover Timeout – This setting is the number of seconds jobs will sit in a Reserved Cloud queue before they are sent to our on-demand infrastructure.
3) Reserved Cloud – This is simply the number of Reserved Cloud instances available to the account and is not an editable field. To make more instances available, contact our sales team.
4) Simultaneous Tasks per Instance – This is the number of jobs a single instance can run at the same time. Each Reserved Cloud instance has 32 processing cores, and can accommodate up to 16 encoding tasks simultaneously.
Figure 4 – These are the Reserved Cloud settings