Change encoder without rewriting your code.
silken serves the MediaConvert API. Point the AWS SDK you already use at one endpoint, sign with your silken API key, and keep calling CreateJob, GetJob and ListJobs. A setting silken does not run comes back by field name, so you know before you move anything.
A free test on your own files · or book a meeting
const mc = new MediaConvertClient({
region: "us-east-1"
})
await mc.send(new CreateJobCommand({
Role, JobTemplate: "hls-ladder", Settings
}))const mc = new MediaConvertClient({
region: "us-east-1",
endpoint: "https://silken.io",
credentials: { accessKeyId: KEY, secretAccessKey: KEY }
})
// the same CreateJobCommand
// a setting silken does not run comes back by name:
400 BadRequestException
unsupported field CreateJob.settings…KEY is your silken API key, used for both credential fields; requests are SigV4-signed to /2017-08-29/.Your job settings, field by field.
What your MediaConvert client sends, and what silken does with it. The full list of supported settings is in the MediaConvert reference.
endpoint / endpoint_url / BaseEndpointhttps://silken.io, set as the endpoint override in the AWS SDK; requests go to /2017-08-29/ as they do at AWSAccessKeyId, SecretAccessKeyYour silken API key in both fields; SigV4 signing with service mediaconvert and region us-east-1CreateJob / GetJob / ListJobs / SearchJobs / CancelJobThe same operations, plus DescribeEndpoints, job templates and presets; anything else returns a named errorSettings.Inputs[].FileInputs3:// read through a read-only IAM role you grant with an external ID, or any presigned HTTPS URLOutputGroups[] (HLS, CMAF)A ladder with HLS playlists delivered to registered S3/R2/B2/Wasabi storage, or held for seven days by defaultOutputGroups[] (File)One MP4 written to the presigned HTTPS URL you give as DestinationOutputs[].VideoDescriptionH.264 rungs: height, width and the QVBR MaxBitrate as each rung’s capAny setting silken does not runRejected by field name with a 400 BadRequestException, never ignored or clampedFour steps, one workload at a time.
A migration is a project with our team, not a ticket. You keep running MediaConvert until each workload passes the checks you set.
MediaConvert is not ending. The end of support on 31 December 2026 in the AWS Elemental Server FAQ is for Elemental Server and Conductor File, the on-premises products. Running those? See Elemental Server migration.
- 01Send one job template and three sources
We run them and show you which settings run today, field by field, before anything else happens.
- 02Compare the outputs and the bill
Check renditions, playlists, picture and full silken job price against your acceptance criteria.
- 03Agree the acceptance checks
Manifests, renditions, captions and turnaround are checked against the list we agree, title by title.
- 04Change the endpoint
Point one workload’s SDK client at silken at a time. Job status comes from GetJob or a signed webhook instead of EventBridge.
Delivered output only. No input fee.
Each delivered version is billed per output minute at the published rate for its resolution. There is no input fee, and the published silken rate card applies. Three speeds: Fast runs solo on the node at top priority, Standard shares the node, and Economy packs jobs onto spare capacity at lowest priority. Economy is native API only: SDR H.264 + AAC, MP4/HLS through 1080p. HDR conversion, captions, DRM and progressive delivery require Standard or Fast. If your masters sit in another region or cloud, your provider may charge to read them, and the free test shows that too.
Questions
Do I have to rewrite my MediaConvert jobs?
No. Override the endpoint in the AWS SDK (endpoint_url in boto3, BaseEndpoint in Go) to https://silken.io, sign with your silken API key, and keep calling CreateJob with the same job template. A setting silken does not run is rejected with its field name, so nothing changes silently.
Do my files have to move?
Your masters stay where they are: silken reads s3:// inputs through a read-only IAM role you grant with an external ID, or any presigned HTTPS URL. Files and ladders can be written to your own registered storage; ladders without a destination are held for seven days by default.
Is MediaConvert being retired?
No. AWS Elemental MediaConvert is not ending. The 31 December 2026 end of support in the AWS Elemental Server FAQ applies to Elemental Server and Conductor File, the on-premises products. Check each job template against the documented compatibility subset before changing the endpoint.
Send us your hardest files.
Send one job setup plus three files. We agree the results date after engineering confirms capacity. You see which of your settings run today, the outputs, the turnaround, the failures and the full silken bill and any storage-provider transfer costs. Free within the standard scope.