AWS Elemental MediaLive
A fully managed service that encodes broadcast-quality live video in real-time and simultaneously outputs to multiple destinations including television broadcast and internet streaming
Overview
AWS Elemental MediaLive is a fully managed service that encodes and transcodes live video streams in real-time, converting them into multiple formats for television broadcast and internet delivery. It encodes live video input via SDI or RTMP in H.264/H.265 and outputs in HLS or DASH format to MediaPackage or S3. A redundant configuration (Pipeline A/B) ensures automatic failover to maintain delivery continuity during hardware failures. Used as a real-time delivery infrastructure for sports broadcasts, news distribution, and live events at scales of millions of viewers, it significantly reduces upfront investment compared to traditional on-premises encoders.
Channel Design and Input/Output Configuration
A MediaLive channel is structured in three layers: Input, encoding settings, and Output Groups. Input sources support RTMP Push, RTP, HLS Pull, MediaConnect flows, and SDI input from Link devices, with the ability to switch between up to two inputs during delivery (Input Switching). Encoding settings define a bitrate ladder (ABR) - for example, simultaneously outputting three tiers at 1080p/5Mbps, 720p/3Mbps, and 480p/1.5Mbps enables adaptive bitrate delivery that adjusts to viewers' network conditions. Output Groups can combine MediaPackage (OTT delivery), Archive (S3 recording), Frame Capture (thumbnail generation), and RTMP (simultaneous social media streaming), outputting from a single channel to multiple destinations simultaneously. Audio Description and subtitle insertion (EBU-TT, WebVTT) are also managed declaratively in channel settings.
Redundancy and Fault Tolerance Design Patterns
For broadcast-quality delivery, eliminating single points of failure is the top priority. MediaLive provides pipeline redundancy (STANDARD channel) where two independent encoding pipelines operate simultaneously. When one pipeline fails, downstream MediaPackage automatically switches to input from the other pipeline. For input-side redundancy, MediaConnect is used to receive source video from two different AZs. Additionally, the Input Failover feature defines primary and secondary input sources, automatically switching to the secondary when the primary video feed is lost. Related books on video streaming (Amazon) provide systematic coverage of delivery infrastructure design. Fault detection is typically monitored via CloudWatch's InputVideoFrameRate metric, with alerts triggered on frame rate drops.
Cost Optimization and Operational Considerations
MediaLive pricing is determined by channel uptime (per minute), input resolution, number of outputs, and codec (H.264 vs H.265). For 24/7 linear channels, Reserved Pricing (1-year or 3-year commitments) can reduce costs by up to 50%. For intermittent event delivery, on-demand pricing is appropriate, and automating channel start/stop with EventBridge schedules prevents unnecessary uptime. H.265 (HEVC) encoding can reduce bitrate by approximately 30% at equivalent quality compared to H.264, but encoding costs are roughly double, so the decision should weigh CDN transfer cost tradeoffs. H.265 is advantageous when viewer counts are high and CDN costs dominate. Channel configuration changes can be pre-programmed using the Schedule Actions feature, enabling time-scheduled automatic execution of ad insertion and slate image switching.