Working with reserved queues in AWS Elemental MediaConvert
With reserved queues, you can purchase transcoding capacity for a 12-month period. The following topics provide information about working with reserved queues, such as creating and deleting queues, and allocating resources.
Topics
About reserved queues
Reserved queues differ from on-demand queues in how AWS Elemental MediaConvert allocates transcoding resources for jobs and in how you pay for your transcoding.
Note
There are a few features that you can't use with jobs that you send to a reserved queue. For more information, see Feature limitations with reserved queues.
Resource allocation and job prioritization with reserved queues
When you set up your reserved queue, you choose how many jobs it can run at once by specifying the number of reserved transcode slots (RTS) in the queue. For example, if you send five jobs to a reserved queue with two RTS, MediaConvert immediately begins processing the first two jobs that you submit, and it holds the other three in the queue. When one of the jobs that MediaConvert is processing finishes, the service begins processing the next job.
Each RTS has its own dedicated computing resources. Therefore, when MediaConvert processes a job that you send to a reserved queue, it takes the same amount of time to process whether the queue has one RTS or multiple RTS.
When a job in a reserved queue finishes, MediaConvert selects the next job to process based on the job's priority. You set the priority of a job when you create it. If more than one job has the highest priority, MediaConvert begins the one that you submitted first. For more information, see Job priority.
How you pay for transcoding with reserved queues
With reserved queues, you pay for the capacity in the queue regardless of
whether you use it. When you set up a reserved queue, you make a 12-month
commitment to a pricing plan. The pricing plan specifies a fixed number of
reserved transcode slots (RTS). For more information, see MediaConvert
Pricing
Important
After you purchase your RTS, you can't cancel your 12-month commitment.
You can purchase additional capacity for a reserved queue that already has RTS. To purchase additional capacity, you extend your existing commitment with a new 12-month commitment for a larger number of RTS. The new commitment begins when you purchase the additional capacity. You can't decrease the number of RTS in your reserved queue.
When your pricing plan term expires, your reserved queue persists. You can still send jobs to it, but AWS Elemental MediaConvert doesn't run them.
About Auto Renew
You can set your pricing plan to auto renew. When your pricing plan term ends, AWS Elemental MediaConvert checks the auto renew status. If auto renew is enabled at that time, you automatically commit to another 12-month term for the same number of RTS at the same price. You can change the auto renew status at any time.
You can choose auto renew when you set up your queue. Anytime after that, you can change the auto renew status on the Edit page for the queue. For more information, see Create a reserved queue and Edit reserved queues.
About billing when jobs hop queues
When you set up queue hopping between a reserved queue and an on-demand queue, MediaConvert bills you according to the queue that it runs your job from. That is, if the job runs from your reserved queue, MediaConvert doesn't bill you for the job. If the job runs from your on-demand queue, MediaConvert bills you for the job at the on-demand rate.
Feature limitations with reserved queues
The following features are available only in jobs that you send to an on-demand queue. For jobs that you send to a reserved queue, you must disable the following features:
-
Note
Reserved queues cannot run accelerated jobs. However, you can submit a job to a reserved queue with Accelerated transcoding set as Preferred. When you do, if the job hops to an on-demand queue, it will run with acceleration. For more information, see Specify accelerated transcoding for hopped jobs.
Create a reserved queue
If you decide to purchase additional capacity for your reserved queue, you can. For more information, see Purchase additional capacity for a reserved queue. The following tabs show different options for creating a reserved queue.
Purchase additional capacity for a reserved queue
To increase the number of jobs that your reserved queue can process at once, you can purchase additional capacity for it. To purchase additional capacity, you extend your existing commitment with a new 12-month commitment for a larger number of reserved transcode slots (RTS). The new commitment begins when you purchase the additional capacity. You can't decrease the number of RTS in your reserved queue. You can't cancel your commitment or revert to your original commitment after you increase the capacity.
The following tabs show how to purchase additional capacity for a reserved queue.
Edit reserved queues
When you edit a queue, you can change the following:
-
The description, which helps you identify it in the queue dashboard.
-
The auto renew status of the queue's pricing plan for reserved transcode slots (RTS). For more information, see How you pay for transcoding with reserved queues.
-
The paused or active status of the queue. Pausing the queue prevents the service from starting any more jobs until you reactivate the queue.
The following tabs show two options for editing a reserved queue.
Listing reserved queues
You can list the AWS Elemental MediaConvert queues that are associated with your Amazon Web Services account and get details about those queues. The following tabs show two options for listing your queues.
Purchase transcoding capacity for an expired reserved queue
After your initial pricing plan term for reserved transcode slots (RTS) expires, your reserved queue persists without the capacity to run transcoding jobs. You can send jobs to the queue, but MediaConvert doesn't process them. To begin processing jobs through the queue again, you can set up a new pricing plan, which requires a new 12-month commitment.
The following tabs show two options for purchasing transcoding capacity for an expired reserved queue.
Delete a reserved queue
You can delete any queue other than the default queue. You can't delete a reserved queue that has an active pricing plan or that contains unprocessed jobs. The following tabs show two options for deleting a reserved queue.
Simulate a reserved queue
You can run a job in a simulated reserved queue to test its performance. When you do, MediaConvert runs your job from an on-demand queue with similar performance to what you will see with one RTS in a reserved queue. Take note of how long you job takes to complete and use this job completion time when calculating how many RTS you need.