Case study

Pilot Reels. From a schedule to a published video.

Pilot Reels turns a series brief into recurring short videos: script, voice, visuals, captions and publication. We built the AWS pipeline that runs that journey in Arabic and English, with each episode tracked against its posting window.

Practice AWS Cloud · DevOps Engagement Platform build · automated video · generative AI
Designed capacity
15K+
Videos per month in the platform sizing model; not a published volume.
Publishing platforms
3
YouTube Shorts, TikTok and Instagram Reels.
Languages
2
Arabic and English, including right-to-left captions.
Proof of concept
6 weeks
Test series covered languages, visual styles and all three publishing paths.
The brief

A posting schedule has dependencies all the way back to the script.

A scheduled video depends on several kinds of work finishing in order: generation, voice, rendering and the external publishing platform. Bursts of simultaneous jobs or a failed platform request could otherwise leave an episode late or posted twice.

Pilot Reels also needed predictable cost per video and protection for customers' channel credentials. The production system had to make failures visible and recoverable without manual editing of every episode.

What we did

Treat every episode as a trackable workflow.

Start production ahead of the posting slot

EventBridge Scheduler queues work after checking the customer's credits. Each stage records progress so the team can follow an episode from scheduled job to published result.

Scale the render workload independently

SQS queues separate generation, rendering and publishing. ECS Fargate workers expand with queue depth, keeping posting-time bursts from forcing every service to carry the same capacity.

Match the AI model to the work

Amazon Bedrock supports scripts, scene prompts, captions and keyframe generation. Different model tiers handle different tasks, with content checks and per-video usage metering.

Make publication safe to retry

Publisher workers use each customer's authorisation and protect against duplicate posts. Failed jobs remain visible for recovery, and Arabic captions are tested alongside the English path.

The outcome

An operational pipeline with a cost per episode.

The delivered platform covers scheduling, generation, rendering and publishing to all three services. The proof of concept produced and posted test series across both languages and the supported visual styles before production build-out.

The platform is sized for more than 15,000 videos a month. Publishing within the scheduled window for at least 99% of episodes, and at least 99.5% success after retries, are service targets rather than reported production results.

The brief

The person you brief is the person who solves it.

One conversation · 30 minutes · no monologue