Create a reusable AWS Elemental MediaConvert job template with CreateJobTemplate
domain: docs.aws.amazon.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Define transcoding settings (outputs, encoding parameters) once, following the same settings schema used for ad hoc jobs
Call CreateJobTemplate (or the AWS CLI create-job-template command with a JSON settings file) to save the template with a name, category, description, and queue
Reference the saved job template's name when submitting new transcoding jobs instead of repeating the full settings payload each time
Use ListJobTemplates/GetJobTemplate to confirm the template exists and inspect its settings before relying on it in production
Update the template centrally when encoding requirements change so all jobs referencing it pick up the new settings
Known gotchas
Job templates are a way to avoid repeating a large settings payload, but a job submitted from a template can still override specific settings at invocation time - verify whether your integration expects strict template settings or allows overrides
Template name, category, description, and queue can be set either in the JSON settings file or as separate CLI/API parameters - conflicting values between the two need to be reconciled
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?