What Is AWS Elemental? A Developer’s Guide to AWS Media Services

If you’ve researched cloud video infrastructure, you’ve run into AWS Elemental — the brand behind seven cloud media services, four on-premises appliances, and the video encoding stack that powers some of the largest streaming events on the planet, including the Super Bowl, the Olympics, and Prime Video. Amazon spent roughly $350 million acquiring Elemental Technologies in 2015, then folded its broadcast-grade encoders into AWS as a full portfolio of pay-as-you-go media services.

The catch for developers: AWS Elemental isn’t one product. It’s a suite of MediaLive, MediaConvert, MediaPackage, MediaConnect, MediaStore, MediaTailor, and (as of 2026) Elemental Inference — each priced separately, with different APIs and different roles in a video pipeline. Picking the right combination is half the work.

This guide breaks down every service in the AWS Elemental portfolio, how they fit together, what they cost per hour, and when a simpler live streaming API makes more sense than wiring up four AWS services yourself.

What Is AWS Elemental?

AWS Elemental is a portfolio of cloud-based media services and on-premises appliances from Amazon Web Services that handle live and file-based video encoding, packaging, transport, storage, ad insertion, and AI-powered processing for broadcasters, streamers, and OTT platforms. It evolved from Elemental Technologies, a Portland-based company founded in 2006 by three former Pixelworks engineers — Sam Blackman, Jesse Rosenzweig, and Brian Lewis — and was acquired by AWS in September 2015. The brand officially became “AWS Elemental” in April 2017.

The portfolio splits into two categories. Cloud media services (MediaLive, MediaConvert, MediaPackage, MediaConnect, MediaStore, MediaTailor, and Elemental Inference) run inside AWS regions on a pay-as-you-go model. On-premises appliances (Elemental Live, Conductor Live, Statmux, and Link) sit in your own data center, control room, or stadium and connect back to the cloud when needed.

The History Behind AWS Elemental

AWS Elemental’s roots matter because they explain why the portfolio looks the way it does. Elemental Technologies built broadcast-grade encoders that ran on GPU-accelerated commodity hardware — a contrarian bet in 2006, when most video processing required dedicated ASICs. By 2010, the company had shipped Elemental Live, an enterprise live-encoding appliance used by cable networks, sports leagues, and pay-TV operators.

After the 2015 acquisition, AWS rewrote much of that stack as managed cloud services. The first wave — MediaConvert, MediaLive, MediaPackage, MediaStore, and MediaTailor — launched at AWS re:Invent in November 2017. MediaConnect followed in 2018. The 2026 addition of Elemental Inference marked the portfolio’s pivot toward AI-driven video processing, with automatic vertical cropping and highlight detection for short-form distribution.

Today, the on-premises appliances still exist for customers who need on-site encoding — primarily satellite operators, in-venue production, and broadcasters with strict latency or sovereignty requirements — but the cloud services drive most new development.

AWS Elemental Media Services Explained

Each of the seven cloud media services handles one slice of the video workflow. They’re designed to compose: a typical live workflow stitches together MediaConnect → MediaLive → MediaPackage → CloudFront, with MediaTailor injecting ads. Here’s what each one does.

AWS Elemental MediaConnect

MediaConnect is a live video transport service that replaces satellite and fiber for contribution feeds. It moves broadcast-quality streams between locations, partners, and AWS regions over the public internet using protocols like Zixi, RTP-FEC, and SRT. The service supports up to 4K resolution at 100 Mbps per flow, point-to-multipoint distribution, and built-in encryption.

Use it when you need to pull a live feed from a stadium, a remote production truck, or a partner network into AWS for further processing. MediaConnect is billed per flow-hour plus data transfer.

AWS Elemental MediaLive

MediaLive is the live video encoder of the portfolio. It ingests live sources over RTMP, RTP, HLS, or MediaConnect flows and produces multiple adaptive bitrate renditions in real time. MediaLive supports H.264, H.265 (HEVC), and AV1, with resolutions up to 4K at 120fps and audio in AAC, Dolby Digital, and Dolby Atmos.

The service’s key differentiator versus simpler tools is reliability. Standard channels run two parallel encoding pipelines, so a hardware failure in one zone doesn’t drop your stream. Input failover lets you swap from a primary to a backup source mid-broadcast. That’s the architecture that powers 24/7 linear channels and tier-1 live sports.

AWS Elemental MediaConvert

MediaConvert is the file-based counterpart to MediaLive. It transcodes uploaded VOD files into multiple device-targeted renditions — H.264 for older browsers, HEVC for 4K mobile, AV1 for bandwidth-constrained delivery. Output formats include HLS, DASH, CMAF, and MP4. The service handles Dolby Vision, Dolby Atmos, accessibility captions, audio normalization, and DRM packaging.

Pricing is per output minute, with rates that vary by codec and resolution. A typical workflow: a user uploads a 1-hour 4K source, MediaConvert produces an HLS ladder with five renditions, and the resulting segments land in S3 or MediaStore for delivery.

AWS Elemental MediaPackage

MediaPackage is the origin server. It takes a single live encoded source (usually from MediaLive) and packages it on the fly into multiple delivery formats — HLS, DASH, CMAF, and Microsoft Smooth Streaming — so a single channel can feed iPhones, Android devices, smart TVs, and web players from one URL.

MediaPackage also handles time-shift features: cloud DVR, live-to-VOD asset creation, ad-conditioned playlists, and SCTE-35 marker manipulation. It supports four DRM systems (Widevine, FairPlay, PlayReady, and AES-128) and integrates with all major key servers. For OTT platforms, MediaPackage is what makes “one feed, every device” practical.

AWS Elemental MediaStore

MediaStore is object storage purpose-built for video. It looks like S3 but is tuned for the access patterns of live streaming — millions of HLS segment GETs per second per object, with consistent millisecond write latency and no eventual-consistency surprises. AWS positions it for live origin storage where MediaPackage isn’t enough on its own.

In practice, most workflows now route through MediaPackage, S3, or CloudFront caches rather than MediaStore. The service remains useful for very high-throughput live recording or DVR storage that needs predictable read performance.

AWS Elemental MediaTailor

MediaTailor is a server-side ad insertion (SSAI) service. Instead of dropping ad markers into the player and letting client-side code stitch ads in (which ad blockers can defeat), MediaTailor manipulates the manifest on the origin to splice personalized ads into each viewer’s HLS or DASH playlist. The result looks like the main content stream and is much harder to block.

MediaTailor handles linear ad replacement, on-the-fly ad pod construction, frequency capping, and integration with ad decision servers like Google Ad Manager, FreeWheel, and SpringServe. It’s the monetization piece for FAST channels and AVOD platforms.

AWS Elemental Inference (New in 2026)

The newest addition, announced in February 2026, is an AI service that processes live and on-demand video to generate vertical clips for mobile-first distribution. It performs automatic landscape-to-portrait cropping using subject tracking, and analyzes metadata to identify highlight-worthy moments in live broadcasts (a goal in football, a kill in esports, a peak moment in news coverage).

Elemental Inference is available in four AWS regions at launch — US East (N. Virginia), US West (Oregon), Asia Pacific (Mumbai), and Europe (Ireland). It’s targeted at broadcasters who need to spin live content into TikTok-ready short-form without dedicating editorial staff to every clip.

AWS Elemental Appliances & Software

On-premises hardware remains part of the portfolio for customers who need encoding at the source. The lineup is smaller than the cloud services but addresses workflows where round-trips to AWS aren’t acceptable.

AWS Elemental Live is the descendant of the original Elemental Live appliance from 2010 — a rackmount unit that does live H.264/H.265/AV1 encoding for cable, satellite, and IPTV operators.

Conductor Live orchestrates fleets of Elemental Live encoders, handling failover, scheduling, and stream provisioning across a control room or playout center.

Statmux is statistical multiplexing software for cable and satellite operators who pack multiple channels into a fixed transponder bandwidth. It dynamically reallocates bits between channels based on scene complexity.

AWS Elemental Link is the appliance most relevant to smaller production setups. It’s a small box you plug an SDI or HDMI source into; it auto-discovers a configured MediaLive channel and pushes the feed without any encoder configuration. The 1080p model is the standard; the Link UHD model handles 4K HDR.

How AWS Elemental Works: A Typical Live Workflow

For a developer building live streaming, the canonical AWS Elemental pipeline looks like this:

1. Capture and contribute. An encoder at the venue (or an Elemental Link device) pushes RTMP or SRT to a MediaConnect flow or directly to a MediaLive input.
2. Live encode. MediaLive transcodes the contribution feed into an adaptive bitrate ladder — typically 1080p, 720p, 480p, and 360p — using adaptive bitrate streaming techniques.
3. Origin and package. MediaLive outputs to MediaPackage, which produces HLS and DASH manifests, applies DRM, and exposes time-shifted endpoints.
4. Monetize. MediaTailor sits between MediaPackage and the player, splicing ads into the manifest based on SCTE-35 markers.
5. Deliver. Amazon CloudFront delivers the streams globally with caching at the edge.
6. Record and repurpose. MediaPackage automatically creates live-to-VOD assets in S3; MediaConvert or Elemental Inference can re-encode them for clips.

For VOD-only workflows, the path collapses to: upload to S3 → trigger MediaConvert → output to S3 or MediaStore → CloudFront delivery. No MediaLive or MediaPackage required.

AWS Elemental Pricing

AWS Elemental is pay-as-you-go but the math gets complex because each service prices differently. Here’s a rough developer’s guide.

MediaLive is the line item that usually dominates a live workflow’s bill. It uses per-minute billing with a 10-minute minimum. Costs vary by:

• Input type (codec, bitrate, resolution)
• Number of output renditions
• Whether you run a STANDARD channel (two pipelines) or SINGLE_PIPELINE
• Advanced features (statmux, frame capture, Dolby audio)

A single 1080p channel with three outputs runs roughly $1.50-$3.00 per hour on demand. A Standard channel with two HD inputs and five AVC outputs costs around $3.94 per hour. If you commit to a 12-month reservation and run more than 180 hours per month, you can shave up to 70% off the on-demand rate.

MediaConvert charges per output minute. Basic tier runs around $0.0075 per minute for SD H.264; professional tier (HEVC, 4K, HDR) is several times higher. A 1-hour 4K HDR transcode with a five-rendition ABR ladder can land between $1 and $5.

MediaPackage charges per GB of content packaged plus per GB of egress. Live channels add a small per-hour rate.

MediaConnect charges per flow-hour plus outbound data transfer.

MediaTailor charges per ad-supported viewer hour.

MediaStore charges per GB of storage and per request, at rates higher than S3 in exchange for media-optimized performance.

The hidden cost: data transfer. Egress to the internet via CloudFront is billed separately, and at scale it often dwarfs the encoding line items. Run the numbers across a representative month before committing.

Advantages of AWS Elemental

AWS Elemental earned its position as the de facto choice for tier-1 broadcasters for a few reasons.

Broadcast-grade quality. The encoders are derived from a decade of work on professional video processing. H.264 quality at a given bitrate is competitive with or better than most alternatives, and the codec coverage (H.264, HEVC, AV1, Dolby Atmos, Dolby Vision) is broader than most cloud services.

Reliability for 24/7 channels. Standard MediaLive channels run two parallel encoding pipelines across availability zones, and input failover lets you swap sources mid-stream. That’s what 24/7 linear channels need.

Scale. AWS Elemental routinely handles tier-1 events — the Super Bowl, the Olympics, the Premier League. The infrastructure is built for tens of millions of concurrent viewers without preprovisioning.

Deep AWS integration. If your application already runs on AWS, the services compose with IAM, CloudWatch, Lambda, S3, and CloudFront without bolt-on glue.

Codec breadth. Few cloud services support AV1 encoding, HEVC with HDR, Dolby Vision, and Dolby Atmos in the same product. AWS Elemental does.

Drawbacks of AWS Elemental

The portfolio’s strengths come with real friction for smaller teams.

Complexity. A working live pipeline needs MediaConnect, MediaLive, MediaPackage, MediaTailor, S3, and CloudFront — each with its own console, API, IAM permissions, and pricing model. Wiring them together in CloudFormation or Terraform is its own engineering project.

Pricing opacity. Per-minute billing across six services makes it hard to predict a monthly bill before you’ve actually run a workload. Most teams spend a couple of weeks running test channels just to understand their cost shape.

Latency. MediaLive’s lowest practical glass-to-glass latency is around 30 seconds with HLS. If you need sub-second latency, you’re looking at Amazon IVS, WebRTC, or a different stack entirely. See our guide on ultra-low-latency video streaming for context.

Time to launch. A first working pipeline takes most teams 1-3 weeks. Production-hardening (failover testing, monitoring, cost alarms, automated channel lifecycle) is a multi-month project.

Operational overhead. MediaLive channels charge you for every minute the channel is running, whether or not anyone is watching. Forgetting to stop an idle channel is a common source of unexpected bills.

If you’re a broadcaster pushing tens of thousands of channel-hours per month with tier-1 reliability requirements, the operational overhead is worth it. If you’re a developer trying to ship a live streaming feature in a SaaS app or a creator platform, the configuration tax often outweighs the benefits. That’s the trade-off most teams weigh before they pick a stack.

How to Get Started With AWS Elemental

If you’ve decided AWS Elemental fits, here’s the minimum-viable path to a working live channel.

Step 1: Set up MediaPackage. Create a channel and an HLS endpoint. Record the ingest URLs MediaPackage returns — you’ll feed these to MediaLive.

aws mediapackage create-channel --id my-live-channel
aws mediapackage create-origin-endpoint \
  --channel-id my-live-channel \
  --id my-hls-endpoint \
  --hls-package "SegmentDurationSeconds=6"

Step 2: Create a MediaLive input security group and input. The security group restricts which IPs can push to your RTMP endpoint.

aws medialive create-input-security-group \
  --whitelist-rules Cidr=203.0.113.0/24
aws medialive create-input \
  --name my-rtmp-input \
  --type RTMP_PUSH \
  --input-security-groups <security-group-id>

Step 3: Create a MediaLive channel that pulls from the input and pushes to MediaPackage. You’ll define the ABR ladder, audio settings, and output group in the channel configuration. The console wizard is easier than the CLI for this step.

Step 4: Start the channel and push your source from an RTMP encoder like OBS, Wirecast, or vMix. After ~30 seconds the HLS endpoint from step 1 will start serving segments.

Step 5: Set up CloudFront in front of the MediaPackage endpoint for global delivery. CloudFront’s caching is what turns a single-region origin into a global stream.

Step 6: Stop the channel when you’re done. Idle running channels still bill at the standard hourly rate.

For VOD-only workflows, swap MediaLive and MediaPackage for MediaConvert: upload to S3, trigger a MediaConvert job, deliver from S3 via CloudFront. Read more on video transcoding APIs if you want to compare approaches.

AWS Elemental Alternatives

If the complexity-to-feature ratio of AWS Elemental doesn’t fit your team, alternatives compress the pipeline.

Amazon IVS is AWS’s own simplified live streaming service. It’s a managed end-to-end pipeline with sub-3-second latency, native chat, and no MediaLive/MediaPackage configuration. The trade-off: maximum 1080p at 60fps, no AV1, no Dolby, no 24/7 channel optimizations.

Mux, Cloudflare Stream, and api.video are managed video APIs that abstract away MediaConvert + MediaPackage + CDN into a single API call. See our Mux alternatives writeup for a comparison.

Wowza Streaming Cloud is a classic managed streaming option for hybrid (on-prem + cloud) workflows. See our breakdown of Wowza alternatives.

LiveAPI is the developer-first option. It rolls live ingest (RTMP and SRT), video encoding, HLS packaging, multi-CDN delivery (Akamai, Fastly, Cloudflare), and an embeddable player into a single API with pay-as-you-grow pricing. Where AWS Elemental needs six services and a couple of weeks of plumbing, LiveAPI gets a working live or VOD pipeline running in a few lines of code. Check the best live streaming APIs for the broader landscape.

AWS Elemental FAQ

What is AWS Elemental used for?

AWS Elemental is used to encode, package, transport, store, monetize, and deliver live and on-demand video at broadcast quality. Common use cases include 24/7 OTT channels, live sports streaming, news broadcasts, FAST channels, and large-scale VOD libraries that need device-targeted ABR delivery.

Is AWS Elemental free?

No. Every AWS Elemental service is pay-as-you-go with no free tier. MediaLive bills per channel-minute (around $1.50-$4 per hour for a typical 1080p channel), MediaConvert bills per output minute, MediaPackage bills per GB packaged, and so on. Costs add up quickly if you run channels 24/7.

What is the difference between AWS Elemental MediaLive and MediaConvert?

MediaLive encodes live video streams in real time and runs continuously while a live event is happening. MediaConvert encodes file-based video on demand as a one-off job that produces an output file. Use MediaLive for live channels and events; use MediaConvert for VOD libraries, archives, and post-event re-encoding.

What is the difference between MediaPackage and MediaStore?

MediaPackage is an origin server that produces HLS, DASH, and CMAF manifests with DRM and time-shift features from a single input. MediaStore is purpose-built object storage for video segments with millisecond-consistent write latency. MediaPackage handles packaging logic; MediaStore handles storage. Most workflows use MediaPackage with S3 or CloudFront rather than MediaStore directly.

Does AWS Elemental support 4K?

Yes. MediaLive supports 4K live encoding up to 120fps with H.264, H.265, and AV1. MediaConvert supports 4K HDR file-based encoding with Dolby Vision and HDR10. AWS Elemental Live (the on-premises appliance) supports 4K UHD encoding for broadcast workflows. See our 4K live streaming encoder guide for context.

What is AWS Elemental Link?

AWS Elemental Link is a small plug-and-play hardware device that captures SDI or HDMI video and pushes it directly to a configured MediaLive channel with no encoder setup. It’s targeted at simpler live production setups — houses of worship, lecture halls, small sports venues — where a full broadcast encoder is overkill.

Was AWS Elemental originally Amazon?

No. AWS Elemental started as Elemental Technologies, an independent company founded in Portland, Oregon in 2006 by Sam Blackman, Jesse Rosenzweig, and Brian Lewis. Amazon Web Services acquired the company in September 2015 for approximately $350 million and rebranded it as AWS Elemental in April 2017.

How do I learn AWS Elemental MediaLive?

Start with the AWS Elemental MediaLive workshop on the AWS Workshops site, which walks through a complete RTMP-to-HLS pipeline with MediaPackage. From there, read the MediaLive user guide for channel configuration and pricing details. Skill Builder also offers free MediaLive training courses with hands-on labs.

Choosing AWS Elemental for Your Project

AWS Elemental is the right pick when you’re running tier-1 broadcast workflows, need codec breadth (AV1, HEVC, Dolby Atmos), require 24/7 channel reliability with input failover, or already have a deep AWS footprint. The services compose into pipelines that handle the world’s largest live events.

If you’re a developer or product team trying to ship a live streaming feature without becoming a video encoding specialist, the configuration overhead is real. LiveAPI gives you live RTMP and SRT ingest, instant encoding, HLS delivery across Akamai, Cloudflare, and Fastly, embeddable players, and live-to-VOD recordings in a single API — without juggling six AWS services and a CloudFormation template.

Get started with LiveAPI and ship a live streaming feature in days instead of weeks.

For deeper reading, the official AWS Elemental product page lists the current portfolio, and the AWS Elemental Wikipedia entry covers the company’s history. MediaLive’s full per-region rate card is on the MediaLive pricing page.