Submit an AWS Elemental MediaConvert job using a job template, choosing on-demand vs reserved queue

Steps

1. Decide whether to use a system job template (pre-built, settings fixed by AWS) or a custom job template (created from scratch or duplicated/adjusted from a system template) — job templates configure an entire job, while output presets only configure a single output.
2. In the console, open a template on the Job templates page and choose 'Create job'; via API/SDK/CLI, submit a CreateJob request referencing the template rather than re-specifying all output settings.
3. Because inputs and the IAM service role are not stored in templates, supply Inputs (video/audio/caption selectors matching what the template's outputs expect) and the IAM role at job-submission time.
4. Pick a queue for the job by setting the `Queue` property to a queue ARN in the job JSON; if omitted, MediaConvert uses your default on-demand queue.
5. On-demand queues require no advance setup, scale automatically, support all MediaConvert features, and bill per-feature-used rates — this is the default queue type for most customers.
6. Reserved queues require a 12-month commitment and you pay for a fixed number of Reserved Transcode Slots (RTS) regardless of usage; they don't autoscale and have documented feature limitations (e.g. cannot run accelerated transcoding directly, though jobs set to 'Preferred' acceleration can hop to an on-demand queue to get it).