Run your first job

Use a short, non-sensitive source file to prove that JetEncode can read input, report progress, write output, and expose useful diagnostics in your account.

Choose the smallest useful test

Use media you are authorized to process. Record its duration, size, container, video codec, and audio codec. Use an HTTP or S3 source and a dedicated S3 output prefix.

Supported formats

Video: MP4, WebM, MPEG-TS, and MOV. Audio: OGG, AAC, MP3, and WAV. Images: JPG, PNG, WebP, GIF, and animated WebP.

Prepare input and output

Attach an IAM instance role that can read only the test input and write only to the intended output prefix. Do not put AWS access keys in the job payload.

Input and output locations

Jobs read HTTP or Amazon S3 sources and write to Amazon S3 or another S3-compatible destination. Working media uses `/tmp` and is not durable.

AWS identity

Attach a least-privilege IAM instance role when a job uses Amazon S3. JetEncode must use the role through the AWS default credential provider chain.

Submit the job

You can create jobs in the UI, but use the HTTP API for production integrations. Save a valid request body as job.json, using the job payload reference for the exact schema.

curl --user "$JETENCODE_HTTP_USER:$JETENCODE_HTTP_PASSWORD" \
  -H 'Content-Type: application/json' \
  --data @job.json \
  http://<instance-address>/v1/jobs

Job creation API

Create jobs with POST /v1/jobs. The HTTP API also exposes job status, cancellation, configuration, workers, and queues.

Check progress

Capture the returned job identifier. Use the UI or API to distinguish queued, active, successful, cancelled, and failed states.

curl --user "$JETENCODE_HTTP_USER:$JETENCODE_HTTP_PASSWORD" \
  http://<instance-address>/v1/jobs/<job-id>

UI, API, and authentication

Complete first-run setup in the browser UI. Protect the UI and HTTP API with the HTTP credentials you set during setup; use the API for production job creation.

Verify success

Confirm the job reaches the documented success state.
Confirm the output exists at the expected path and is non-empty.
Inspect duration, container, streams, dimensions, and playback.
Locate the corresponding log record using the job identifier.

Job diagnostics

Use the browser UI and HTTP API to inspect job state and errors. JetEncode does not automatically export logs to an external service.

Clean up

Delete test media if no longer needed, remove temporary access grants, and stop or terminate disposable compute resources. Removing an image subscription does not automatically delete the resources you launched.