A customer can export a reviewed video as one MP4 with the judge's tooltips, the score and the branding burned in, and a two second pause at each tooltip.
Clicking Export Video inserts a pending row and returns at once. WordPress then renders the overlay images and a manifest and uploads them to S3. The encoding itself runs on AWS Lambda with ffmpeg, because the host has no ffmpeg and MediaConvert cannot hold a frame.
The click starts the Lambda with an asynchronous invoke, so rendering begins within seconds. The worker claims the job, renders, uploads the MP4 to a presigned URL and reports back. It holds no AWS credentials: WordPress hands it presigned URLs. A WP cron job and a once-a-minute EventBridge poll are the safety nets if the invoke fails.
A double click or an overlapping cron run must not render the same reel twice. A row moves from pending to processing with a single conditional UPDATE, and only the run that changes the row proceeds. Rows stuck in processing return to pending after ten minutes.