Infrastructure Design

Broadcast-Quality Live Streaming - Building a Large-Scale Delivery Platform with AWS Elemental MediaLive and MediaPackage

Explains how to build a broadcast-quality live streaming platform with AWS Elemental MediaLive and MediaPackage. Covers real-time transcoding, DRM, ad insertion, and multi-CDN delivery.

約 5 分で読めます

Requirements for Broadcast-Quality Live Streaming

Cloud migration of TV broadcasts, large-scale sports event delivery, and live streaming for paid video services have requirements that simple streaming services like IVS cannot meet. These include broadcast-quality transcoding (HEVC/H.265, HDR, 4K), DRM content protection, server-side ad insertion (SSAI), simultaneous generation of multiple delivery formats (HLS, DASH, CMAF), multi-CDN delivery, and high availability through redundant configurations. The AWS Elemental media services suite provides a broadcast-quality live streaming pipeline that meets these requirements. You combine MediaLive (transcoding), MediaPackage (packaging), MediaConnect (video transport), MediaStore (low-latency storage), and MediaTailor (ad insertion) to build an end-to-end delivery platform.

Real-Time Transcoding with MediaLive

MediaLive is a real-time transcoding service for live video. It receives video from input sources such as RTMP, RTP, HLS, and MediaConnect, and simultaneously converts it to multiple resolutions and bitrates. You define an ABR (Adaptive Bitrate) ladder; for example, you can simultaneously generate four output tiers: 1080p/5Mbps, 720p/3Mbps, 480p/1.5Mbps, and 360p/800kbps. Supported codecs include H.264 (AVC) and H.265 (HEVC); HEVC delivers equivalent quality at roughly half the bitrate of H.264, making it effective for reducing bandwidth costs. Two channel classes are available: SINGLE_PIPELINE and STANDARD (redundant pipeline). STANDARD processes through two independent pipelines, so streaming continues even if one fails. The STANDARD class is essential for broadcast-quality delivery.

MediaPackage with DRM and Ad Insertion

MediaPackage receives output from MediaLive and packages it into formats suitable for viewer devices. Just-in-Time packaging dynamically generates HLS (Apple devices), DASH (Android, Web), CMAF (low latency), and MSS (legacy Windows) from a single input. Since there is no need to pre-generate and store all formats, storage costs are reduced. DRM integration supports the three major DRM systems: Widevine (Google), FairPlay (Apple), and PlayReady (Microsoft), connecting to DRM key servers via the SPEKE (Secure Packager and Encoder Key Exchange) protocol. Integration with MediaTailor enables server-side ad insertion (SSAI). SSAI merges ads into the content stream on the server side, so it is unaffected by client-side ad blockers. For a systematic study of video delivery architecture, related books (Amazon) are also helpful.

MediaConnect and Delivery Architecture

MediaConnect is a highly reliable live video transport service used for video transmission between broadcast facilities and sites. It supports SRT (Secure Reliable Transport) and Zixi protocols, achieving broadcast-quality video transport even over the internet. Redundant flows ensure high availability, and real-time video quality monitoring metrics are provided. A typical delivery architecture flows from video source to MediaConnect (transport) to MediaLive (transcoding) to MediaPackage (packaging) to CloudFront (CDN delivery) to viewer devices. MediaLive input channel pricing is $0.354/hour for SD, $0.918/hour for HD, and $1.836/hour for Full HD. MediaPackage origin costs $0.034 per GB. Running a 24/7 live channel can cost several thousand dollars per month, so design according to your delivery scale and requirements.

Elemental Pricing

MediaLive pricing depends on input channel and output resolution/codec. HD (1080p) AVC output costs approximately $1.836 per hour. MediaPackage charges approximately $0.10 per GB received, with delivery billed through CloudFront pricing. MediaStore costs approximately $0.023 per GB/month for storage plus pay-per-use PUT/GET request charges. Monthly costs for a 24-hour broadcast channel can reach several thousand dollars, so manage costs by starting and stopping channels according to your broadcast schedule.

Summary - Guidelines for Using Elemental Media Services

The AWS Elemental media services suite provides the building blocks for broadcast-quality live streaming platforms in the cloud. Combine MediaLive's real-time transcoding, MediaPackage's Just-in-Time packaging and DRM, MediaConnect's reliable video transport, and MediaTailor's ad insertion to build an end-to-end delivery pipeline. It is suited for large-scale delivery that requires DRM, ad insertion, and broadcast-quality transcoding. If you only need interactive low-latency streaming, consider IVS instead.

Related Services

AWS Elemental MediaLiveA service that encodes broadcast-quality live video in real timeAWS Elemental MediaPackageA service that packages and delivers live and on-demand video for multiple devicesAmazon CloudFrontA CDN service that delivers content at high speed from edge locations around the world

Related Articles

Live Streaming Infrastructure - Building Low-Latency Live Streams with Amazon IVSLearn how to build low-latency live streaming with Amazon Interactive Video Service (IVS). This article covers managed infrastructure, chat integration, real-time stage features, and when to choose MediaLive instead.Video Transcoding - Building a Scalable Media Conversion Pipeline with AWS Elemental MediaConvertLearn how to build a video transcoding pipeline using AWS Elemental MediaConvert and S3. This article covers multi-format output, HDR support, and cost-efficient serverless media processing techniques.Automating SSL/TLS Certificate Management with AWS Certificate Manager - From Issuance to RotationLearn how ACM handles free public certificate issuance, DNS validation, automatic renewal, and deployment to ALB and CloudFront.

More on This Topic

Why Auto Scaling Scales Out Fast but Scales In Cautiously - The Design Intent Behind Asymmetric Decision LogicThis article explains why EC2 Auto Scaling executes scale-out immediately while applying a cooldown period for scale-in, the flapping prevention mechanism, and the internal logic of target tracking scaling.Demand-Driven Infrastructure with AWS Auto Scaling - Designing and Optimizing Scaling PoliciesLearn how to use target tracking, predictive, and scheduled scaling policies effectively, and optimize costs with mixed instances policies that leverage Spot Instances.AWS Fault Domain Design - How the Three-Layer Structure of AZs, Regions, and Partitions Protects AvailabilityLearn why AWS infrastructure is designed with three layers of fault domains - AZs (fault isolation), Regions (geographic separation), and Partitions (political separation) - and how far failures propagate at each layer, with real-world examples.Distributed Systems Principles Learned from AWS Outages - How Past Major Incidents Reshaped ArchitectureUsing AWS's published incident reports as case studies - including the S3 outage (2017), Kinesis outage (2020), and the unique nature of us-east-1 - this article explains design principles such as Shuffle Sharding, Static Stability, and Cell-based Architecture.Why AWS Builds Regions Where It Does - The Hidden Criteria Behind Data Center Site SelectionWe explain the criteria AWS considers when deciding region locations, including power supply, geopolitical risk, data sovereignty legislation, network connectivity, and natural disaster risk, with concrete examples from specific regions.Why AWS Availability Zone IDs Differ Per Account - The Design Intent Behind AZ MappingExplains how us-east-1a maps to different physical AZs per account, why AZ IDs (use1-az1) were introduced, the design intent of even capacity distribution, and considerations for cross-account AZ specification.Batch Computing Infrastructure - Large-Scale Parallel Processing with AWS BatchLearn how to build large-scale batch processing with AWS Batch. Covers job queue design, auto-scaling compute environments, cost optimization with Spot Instances, and building batch infrastructure ideal for scientific computing and large-scale data processing.Automating Batch Computing with AWS Batch - Designing Job Queues and Compute EnvironmentsLearn about job scheduling with AWS Batch, choosing between Fargate and EC2 compute environments, and leveraging Spot Instances for cost optimization.

Similar Articles and Services

Live Streaming Infrastructure - Building Low-Latency Live Streams with Amazon IVSLearn how to build low-latency live streaming with Amazon Interactive Video Service (IVS). This article covers managed infrastructure, chat integration, real-time stage features, and when to choose MediaLive instead.Serverless Video Transcoding with AWS Elemental MediaConvert - HLS Delivery and Thumbnail GenerationTranscode file-based video at broadcast quality and generate multiple formats including HLS, DASH, and MP4 in a single job. Learn how to build large-scale video processing pipelines with job templates and queue priority control.Building Low-Latency Live Streaming with Amazon IVS - Streaming Channels and Chat IntegrationBuild low-latency live streaming channels and integrate player SDKs and chat functionality into your application. This article also covers recording and clip features.