AWS MediaLive + MediaPackage + MediaTailor Pipeline for Indian Broadcasters

AWS MediaLive, MediaPackage and MediaTailor are the three AWS Elemental services that together handle live video encoding, packaging and ad insertion for IP-delivered broadcast channels. This reference architecture shows how they fit together and how to size them for Indian broadcast and OTT traffic patterns.

Indian broadcasters moving a linear or 24x7 news channel to IP delivery consistently land on the same three services. Below is how they fit together, what each one is actually responsible for, and the design decisions that matter for Indian traffic patterns — high mobile viewership, price-sensitive CDN egress, and CTV apps as a growing share of audience.

The Three Layers of the Pipeline

AWS Elemental MediaLive — Encoding

Ingests your live feed (RTMP, SRT or an existing contribution feed) and encodes it into an adaptive bitrate ladder, embedding SCTE-35 ad markers from your playout system or manually configured break points.

AWS Elemental MediaPackage — Packaging & Origin

Takes MediaLive's output and packages it into HLS, DASH and CMAF simultaneously, handles time-shifted/DVR viewing windows, and serves as the origin your CDN pulls from.

AWS Elemental MediaTailor — Ad Insertion

Reads the SCTE-35 cues surfaced through MediaPackage, calls your ad decision server, and stitches the returned ad creative into the manifest before it reaches CloudFront and the viewer.

Reference Architecture

1. Contribution feed arrives via RTMP/SRT from your studio or OB van into MediaLive in ap-south-1 (Mumbai).
2. MediaLive encodes an ABR ladder (typically 240p–1080p for mixed mobile/desktop/CTV audiences common in India) and embeds SCTE-35 cues.
3. MediaPackage packages HLS + DASH output and exposes both a direct endpoint and a MediaTailor-wrapped endpoint.
4. MediaTailor sits in front of the MediaPackage endpoint, stitching ads at each SCTE-35 cue using your ad decision server.
5. CloudFront caches and delivers the MediaTailor-stitched manifest to viewers, with edge locations across India for low-latency delivery to mobile-first audiences.
6. Player clients (web, iOS, Android, CTV apps) request the single stitched stream — no client-side ad logic required.

Sizing for Indian Traffic Patterns

Two things shape the sizing conversation for Indian broadcasters differently than a typical US/EU deployment:

• Mobile-first, bandwidth-constrained viewers. The ABR ladder needs a genuinely usable low-bitrate rung (240p–360p) rather than assuming broadband-class connections — this affects both encoding cost and viewer retention during network congestion.
• CDN egress dominates cost at scale. MediaLive/MediaPackage running costs are largely fixed per channel; CloudFront data transfer is the cost that scales with audience, so ABR ladder discipline (not over-provisioning high bitrates) has a direct, compounding cost impact once you're serving millions of concurrent mobile viewers during a major news event.

Where Corporate Training Fits

Because this pipeline spans encoding, packaging, ad tech and CDN configuration, teams inheriting it often need hands-on training rather than just documentation — walking through MediaLive channel configuration, MediaPackage endpoint setup and MediaTailor session initialization with the actual team that will operate it day to day.

Frequently Asked Questions