AWS Media Services: A Developer’s Guide to the Full Suite

If you’re building a streaming app on AWS, you’ve probably opened the console, searched “media,” and seen a wall of services with similar names — MediaConnect, MediaConvert, MediaLive, MediaPackage, MediaStore, MediaTailor, IVS, Elastic Transcoder, Kinesis Video Streams. Each one solves a slice of the video workflow. None of them does the whole job alone.

This guide breaks down the AWS Media Services suite the way a developer actually uses it: what each service does, how they chain together for live and on-demand workflows, what they cost, and where the rough edges are. By the end you’ll know which services you actually need, which ones you can skip, and when stitching together 6-10 AWS services is overkill for a video streaming app that ships next month.

What Are AWS Media Services?

AWS Media Services is Amazon’s collection of managed services for moving, encoding, packaging, protecting, monetizing, and delivering video in the cloud. The suite covers every stage of a broadcast-grade video workflow — from live ingest through transcoding, packaging, ad insertion, and origin delivery — so you don’t have to run your own encoders, packagers, or transport servers.

The services are grouped under the AWS Elemental brand, a nod to Elemental Technologies, the broadcast video specialist AWS acquired in 2015. According to the AWS overview whitepaper, AWS positions the suite as “the most purpose-built media services, software, and appliances of any cloud.”

Each service is independent, pay-as-you-go, and wired to integrate with the rest of AWS — S3 for storage, CloudFront for CDN, IAM for permissions, CloudWatch for monitoring. That modularity is the suite’s biggest strength and its biggest source of complexity.

AWS Media Services List: The Full Suite

Below is every service that falls under the AWS Media Services umbrella, what it does, and where it sits in a typical video workflow.

AWS Elemental MediaConnect

MediaConnect is the “fiber and satellite replacement” service. It’s a high-quality live video transport service that moves contribution-grade streams from a remote site (a stadium, a studio, a production truck) into AWS, or from AWS out to broadcast partners.

It supports the Zixi, SRT, RTP-FEC, and RIST protocols, and pricing is based on flow hours plus data transfer. If you’re sending a 1080p60 feed from a venue into AWS for encoding, MediaConnect is the front door. For a deeper look at SRT specifically, see the SRT protocol guide.

AWS Elemental MediaLive

MediaLive is the broadcast-grade live encoder. You give it a live input — an RTMP push, an RTP stream, a MediaConnect flow, an HLS pull — and it outputs adaptive bitrate renditions (typically HLS, MPEG-DASH, or UDP/RTP) for downstream packaging or distribution.

It handles transcoding to multiple resolutions and bitrates, audio normalization, ad signaling (SCTE-35), closed captions (608/708/WebVTT), and statmux. Channels can run 24/7 or be spun up for live events. Pricing is per-channel-hour, scaled by input resolution and codec.

AWS Elemental MediaConvert

MediaConvert is the file-based VOD transcoder. Upload an MP4, MOV, MXF, or ProRes source to S3, submit a job, and MediaConvert outputs renditions in H.264, H.265/HEVC, AV1, VP9, or audio-only formats. It handles HLS and DASH packaging, DRM hooks, captions, image overlays, and SCTE-35 markers.

MediaConvert replaced Amazon Elastic Transcoder for most new workloads. Pricing is per output minute, tiered by codec and resolution. A 1-hour 1080p H.264 encode runs roughly $1–$2 per output rendition.

AWS Elemental MediaPackage

MediaPackage is the just-in-time packager and origin. It takes a single input — usually an HLS feed from MediaLive or an MP4 from S3 — and outputs streams in HLS, DASH, CMAF, and Microsoft Smooth Streaming on demand. It also handles DRM (Widevine, PlayReady, FairPlay), DVR-style time-shifting, and ad marker conditioning.

The big win is format-agnostic delivery: one input, every output, generated on the fly. MediaPackage v2 (released 2023) added low-latency HLS and a simpler pricing model based on ingest and egress.

AWS Elemental MediaStore (Deprecated)

MediaStore was a low-latency, S3-compatible origin store purpose-built for video. AWS announced its deprecation in 2024, with full shutdown scheduled for November 13, 2025. The migration path is S3 + CloudFront, or MediaPackage v2 as a managed origin.

If you’re starting a new project today, skip MediaStore. If you’re on it, plan a migration.

AWS Elemental MediaTailor

MediaTailor handles server-side ad insertion (SSAI). Instead of letting client players stitch ads — which gets blocked by ad blockers and breaks on TV apps — MediaTailor splices ads into the manifest on the server, so every viewer sees one continuous stream of content and ads.

It integrates with VAST/VMAP ad decision servers, supports both live and VOD, and emits ad reporting beacons. Pricing is per ad request and per personalized manifest. See our guide to OTT video monetization for the full SSAI vs. CSAI tradeoff.

Amazon Interactive Video Service (IVS)

Amazon IVS is the simpler, all-in-one live streaming service. You push an RTMPS stream to an IVS channel and IVS handles encoding, packaging, CDN delivery, and a player SDK — no MediaLive, no MediaPackage, no CloudFront config required.

IVS has two products: IVS Low-Latency (sub-5-second glass-to-glass, ideal for interactive use cases like live shopping or auctions) and IVS Real-Time (sub-300ms, WebRTC-based, for stage-style group video). It’s billed per ingest hour and per delivery hour.

IVS is much easier to integrate than the Elemental stack, but it gives up the granular control broadcasters need (no statmux, no SCTE-35 ad markers in the same flexible way, no custom packaging).

Amazon Elastic Transcoder (Legacy)

Elastic Transcoder is the original AWS video transcoding service from 2013. AWS still operates it, but recommends MediaConvert for new workloads — Elastic Transcoder lacks support for HEVC, AV1, and many of MediaConvert’s broadcast features.

Amazon Kinesis Video Streams

Kinesis Video Streams isn’t really a media production service — it’s an IoT/analytics ingest pipeline. It captures real-time video from cameras and devices, indexes it by timestamp, and feeds it into ML services like Rekognition or SageMaker. Use it for security cameras, drones, autonomous vehicles, or video analytics, not for streaming entertainment.

AWS Elemental Appliances & Software

For on-prem or hybrid workflows, AWS sells physical and virtual encoders that mirror the cloud services:

• AWS Elemental Live — On-prem live encoder
• AWS Elemental Server — On-prem file encoder
• AWS Elemental Conductor — Cluster manager for the above
• AWS Elemental Link — Small hardware device that captures a venue feed and sends it to MediaLive or MediaConnect

These are aimed at broadcasters with fixed infrastructure or strict latency/bandwidth needs.

How AWS Media Services Work Together

The services are LEGO bricks. Most real-world deployments wire several of them together. Here’s how a typical live and VOD workflow looks.

Live Streaming Workflow

Camera/Encoder
    │ RTMP / SRT / Zixi
    ▼
AWS Elemental MediaConnect       (transport)
    │
    ▼
AWS Elemental MediaLive          (live encoding to ABR)
    │ HLS push
    ▼
AWS Elemental MediaPackage       (packaging, DRM, DVR)
    │ HLS / DASH / CMAF
    ▼
Amazon CloudFront                (CDN)
    │
    ▼
Player (web / mobile / TV)

Optional: MediaTailor sits between MediaPackage and CloudFront for ad insertion. If you don’t need broadcast-grade encoding, Amazon IVS replaces MediaConnect + MediaLive + MediaPackage + CloudFront as a single service. For a deeper comparison, see HLS vs DASH.

Video-on-Demand Workflow

Source upload (MP4/MOV/MXF)
    │
    ▼
Amazon S3                        (mezzanine storage)
    │
    ▼
AWS Elemental MediaConvert       (file transcoding to ABR)
    │
    ▼
Amazon S3                        (packaged output)
    │
    ▼
Amazon CloudFront                (CDN)
    │
    ▼
Player

For DRM, DVR features, or just-in-time packaging on VOD, route the MediaConvert output through MediaPackage’s VOD endpoint instead of straight to S3.

A Hybrid Live-to-VOD Pipeline

Many publishers run both flows from the same source. MediaLive can archive live channels to S3 in MP4 or HLS form, then a Lambda function triggers MediaConvert to repackage the recording as VOD. This is the cloud equivalent of the live to VOD workflow most OTT services need.

AWS Media Services Pricing

There’s no single AWS Media Services price. Every service bills independently, usually by some combination of input minutes, output minutes, channel hours, or data transfer. Here’s a realistic snapshot for a developer running modest workloads (US East regions, mid-2026 pricing, always verify current rates on AWS pricing pages).

On top of these, you’ll pay for S3 storage (~$0.023/GB-month), CloudFront delivery ($0.085/GB to start, tiered down), and any Lambda or Step Functions glue code. A modest 24/7 single-channel live stream with one HD MediaLive channel, MediaPackage, and CloudFront delivery to ~1,000 concurrent viewers can easily run $3,000–$8,000/month. For more on what video infrastructure typically costs, see our breakdown of video hosting costs.

Advantages of AWS Media Services

Broadcast-grade quality

The Elemental codebase came from a 10+ year broadcast video specialist. MediaLive and MediaConvert support pristine 4K HEVC encoding, statmux, SCTE-35, CEA-608/708 captions, Dolby audio — features that matter if you’re delivering to traditional TV alongside OTT.

Modular and composable

Because each service does one thing, you can mix and match. Use MediaConvert without MediaLive. Use MediaPackage with your own encoder. Drop MediaTailor in front of any HLS stream. That flexibility is rare in turnkey video platforms.

Deep AWS integration

Everything plugs into S3, IAM, CloudWatch, EventBridge, Lambda, and Step Functions. If your stack is already AWS-heavy, the operational story is familiar — same console, same monitoring, same billing.

Global reach via CloudFront

MediaPackage and IVS connect natively to CloudFront, AWS’s CDN with 600+ edge locations. Latency to viewers is rarely the bottleneck. For broader CDN options, see our take on the best CDN for video streaming.

Pay-per-use, no upfront commit

Channel hours, output minutes, and ad requests bill by the second or by the unit. You can spin up a MediaLive channel for a one-night event and pay $20–$50.

Mature, battle-tested

Customers like Discovery, Sling TV, Sky, Fox Sports, and Pac-12 Networks run major live events on the suite. The reliability story is real.

Disadvantages of AWS Media Services

Steep learning curve

There’s no “AWS Media Services button.” You have to learn 4–8 different services, their input/output formats, their IAM roles, and how to wire them with S3 events, EventBridge rules, or Step Functions. Most teams burn 2–6 weeks just standing up a working pipeline.

Pricing complexity

Every service has its own pricing dimensions — input minutes, output minutes, channel hours, manifest requests, egress GB. A simple 1-channel setup can have 6+ line items on the bill. Forecasting cost is hard, and small misconfigurations (forgetting to stop an idle channel) can produce surprise charges.

No built-in player

AWS gives you the IVS player SDK for IVS, but for MediaLive/MediaPackage pipelines you supply your own player (Video.js, Shaka, HLS.js, JW Player, Bitmovin). For options, see our video player API guide.

No multistreaming

AWS doesn’t have a native multistream-to-Facebook/YouTube/Twitch service. You’d build that yourself using MediaConnect outputs or a third-party tool.

Some services are being deprecated or renamed

MediaStore is shutting down November 2025. MediaPackage v1 is being superseded by v2. Elastic Transcoder is on life support. Migrations are part of the operational tax.

Limited free tier

The AWS free tier covers Elastic Transcoder (20 free SD minutes/month) and not much else. Most media services hit your credit card on minute one.

The Elemental suite is the right pick when you’re a broadcaster with broadcast requirements, or when your team is deep in AWS and willing to absorb the integration work. If you just need to add live streaming or VOD to a product in days, the calculus shifts.

When to Use a Video API Instead

For most product teams adding video to an app — a fitness platform, a SaaS dashboard, a creator marketplace, a live shopping site, a church streaming service — wiring together MediaConnect, MediaLive, MediaPackage, MediaTailor, CloudFront, and a player SDK is overkill. You spend more time on infrastructure than on the actual product.

A managed live streaming API bundles ingest, encoding, ABR, multi-CDN delivery, and a player into a single API call. LiveAPI is built for exactly this case: developers who want to ship video features fast, without architecting a 6-service pipeline.

Where LiveAPI maps to AWS Media Services:

You also skip the IAM policy juggling, the channel-stop-when-idle Lambda functions, and the multi-line pricing model. LiveAPI is pay-as-you-grow based on video and livestream minutes — one billing dimension instead of six.

For a closer look at how a developer-first API differs from cloud building blocks, see our video API developer guide. If you’re comparing managed video platforms, the best live streaming APIs roundup is a useful starting point.

How to Get Started with AWS Media Services

If the Elemental suite is the right call for your project, here’s the shortest path to a working live pipeline.

1. Map the workflow

Decide which services you actually need. A simple “RTMP in, HLS out, web player” pipeline only requires MediaLive + MediaPackage + CloudFront. Skip MediaConnect unless you’re contributing from a remote site over a managed network. Skip MediaTailor unless you’re inserting ads.

2. Set up IAM roles

Each service needs roles to write to S3, read from S3, and pass roles to other services. Create dedicated service roles up front — they’re the most common source of “it works in the console but fails from CloudFormation” bugs.

3. Create the MediaPackage channel first

Counter-intuitively, build downstream-to-upstream. Create the MediaPackage channel and copy its ingest URL — you’ll need it when configuring MediaLive’s output. Define your HLS/DASH endpoints, DRM config, and DVR window here.

4. Configure the MediaLive input and channel

Pick an input type (RTMP push, RTMP pull, HLS, MediaConnect). Define your output group pointing at MediaPackage. Set your ABR ladder — common ladders are 5 renditions from 360p/600kbps up to 1080p/5Mbps.

5. Wire up CloudFront

Create a CloudFront distribution with the MediaPackage endpoint as the origin. Configure the right cache behaviors — HLS manifests need short TTLs (1–2s), segments can cache longer (10s+). Enable origin shield if you’re high-scale.

6. Test with a software encoder

Use OBS or FFmpeg to push to your MediaLive RTMP ingest. Verify the channel goes “Running,” check the MediaPackage endpoint URL in VLC or hls.js, then plug it into your player.

7. Add monitoring

Wire CloudWatch alarms on MediaLive’s InputVideoFrameRate, ActiveAlerts, and MediaPackage’s EgressBytes. Channels failing silently mid-event is the #1 ops issue.

8. Plan teardown

Idle MediaLive channels still bill. Use EventBridge + Lambda to auto-stop channels when an input has been dark for >30 minutes.

For a worked end-to-end pipeline build, AWS publishes a practical guide to AWS Media Services that walks through several reference architectures.

AWS Media Services vs. Alternatives

The Elemental suite isn’t the only cloud video stack. Here’s how it compares.

Azure’s exit is worth a note — Microsoft retired Azure Media Services in June 2024, which means cross-cloud teams need to pick a non-Microsoft path. AWS’s Elemental suite is the closest like-for-like replacement, and for teams wanting something simpler, see our Mux alternatives and Wowza alternatives breakdowns.

AWS Media Services FAQ

What is the difference between AWS Media Services and AWS Elemental?

AWS Elemental is the brand name for the broadcast-grade services AWS acquired from Elemental Technologies in 2015. AWS Media Services is the broader umbrella covering Elemental services (MediaConnect, MediaConvert, MediaLive, MediaPackage, MediaStore, MediaTailor) plus other media offerings like Amazon IVS, Elastic Transcoder, and Kinesis Video Streams. In practice the terms are used interchangeably. Our AWS Elemental deep dive covers the Elemental-branded services in more detail.

Is AWS Media Services free?

No. There’s no free tier for MediaLive, MediaConvert, MediaPackage, MediaConnect, or MediaTailor. Elastic Transcoder includes 20 free SD output minutes per month. Most workloads hit billable usage from the first stream.

Which AWS media service should I use for live streaming?

For broadcast-grade live, use MediaLive + MediaPackage + CloudFront. For lightweight or interactive live (chat, live shopping, auctions), use Amazon IVS. For just transporting a feed without encoding, use MediaConnect alone.

Which AWS media service should I use for VOD?

MediaConvert is the modern choice. Elastic Transcoder still works but lacks HEVC, AV1, and most of MediaConvert’s broadcast features.

Is MediaStore being shut down?

Yes. AWS announced MediaStore deprecation in 2024, with full service end on November 13, 2025. Migrate to S3 + CloudFront or MediaPackage v2.

Can I use AWS Media Services without other AWS services?

Technically yes — MediaConvert can read from any HTTP source and write to any S3-compatible bucket. In practice, you’ll end up using S3, IAM, CloudFront, CloudWatch, and probably Lambda. The services are designed for the AWS ecosystem.

What protocols does AWS MediaLive support for ingest?

RTMP push, RTMP pull, RTP, HLS pull, MediaConnect flows, and AWS Elemental Link devices. There’s no native SRT or WebRTC ingest in MediaLive itself — for SRT, you route through MediaConnect first. To compare protocols, see SRT vs RTMP.

What output formats does AWS MediaPackage support?

HLS, MPEG-DASH, CMAF, and Microsoft Smooth Streaming. MediaPackage v2 added support for low-latency HLS (LL-HLS).

How does AWS Media Services pricing compare to a managed video API?

AWS bills by service-specific dimensions (channel hours, output minutes, egress GB, manifest requests). A managed video API like LiveAPI bundles everything into video and livestream minutes — usually simpler to forecast for small-to-mid workloads.

Does AWS Media Services support DRM?

Yes. MediaPackage natively integrates with SPEKE (Secure Packager and Encoder Key Exchange) for Widevine, PlayReady, and FairPlay DRM. You bring your own DRM key provider (Axinom, EZDRM, BuyDRM, etc.).

Can I run AWS Media Services on-premises?

Partially. AWS Elemental Appliances & Software (Elemental Live, Elemental Server, Elemental Conductor) run on-prem. The cloud-only services (MediaLive, MediaConvert, MediaPackage) don’t run outside AWS.

Building Streaming Without the Six-Service Pipeline

AWS Media Services is the right pick when you need broadcast-grade control, deep AWS integration, and you’ve got the engineering bandwidth to wire 6+ services together. For everyone else — product teams shipping a feature, founders launching an MVP, developers who’d rather not write IAM policies all afternoon — a single video API is the faster path.

Try LiveAPI free to ship live streaming, VOD, multi-CDN delivery, and an embeddable player in a single API call. RTMP, SRT, and RTSP ingest, instant encoding with ABR, HLS output to Akamai/Fastly/Cloudflare, automatic live-to-VOD, and multistream to 30+ destinations — without the channel-hour math.