What does a cloud playout channel cost on AWS?

Article · Gatis Gailis ·

All figures are estimates from AWS public list prices (eu-west-1, USD, November 2026) for the reference model described below. They are not a quote.

If you run playout for a broadcast, FAST or OTT channel on AWS, most of your bill comes from four things: the virtual machine that plays out 24/7, the storage for your library, the data you send out to the internet, and any second copy you run for redundancy. This article puts numbers on each.

Short answer. In our reference model, one channel running 24/7 costs roughly $800 to $1,100 a month in AWS, depending on channel type. A hot backup brings a linear HD channel to about $1,900. A cloud disaster-recovery channel that sits idle costs about $100 a month, and a three-day pop-up event about $150. These numbers cover AWS only, not any playout software licence.

Estimated AWS cost per month, by channel type

Channel type Estimated AWS cost / month Biggest line
FAST / OTT channel ~$800 Compute (about 70%)
24/7 linear HD channel ~$1,050 Compute (about half), then storage and egress
Linear HD, warm standby ~$1,100 As above, plus second set of storage
Linear HD, 1+1 hot backup ~$1,900 Compute and egress doubled
Cloud DR, idle month ~$100 Storage
Cloud DR, one active day ~$100 Storage
3-day pop-up event ~$150 Storage and compute

With an instance one size smaller or larger and an outbound bitrate between 4 and 25 Mbit/s, the linear HD channel lands between about $650 and $2,100 a month. Your own figure depends on the choices in the “What moves your bill” section.

The reference model

The numbers come from how Veset’s Nimbus platform runs a channel in a customer’s own AWS account: one playout per channel, each on its own virtual machine. Other designs will cost differently. A platform that shares machines between channels, or bills per media-processing hour, has a different cost shape, and these figures do not describe it.

One channel in your own AWS account

Each playout is a small stack: an EC2 virtual machine running the playout software, EBS volumes for cache, data, logs and HLS segments, a public IP with DNS, and an S3 bucket for the media library.

The five things that make up the bill

  1. Compute (EC2). The playout runs around the clock: 730 hours a month. The cost is fixed whether the channel plays a live show or a loop. It is the largest line, and the one where instance size matters most.
  2. Storage. The media library in S3 (about $24 per TB per month) plus EBS volumes on the playout machine.
  3. Internet egress. Everything the channel sends out to the internet. AWS gives 100 GB a month free, then charges per GB. This is the line that depends most on your own choices.
  4. Fixed network items. A public IPv4 address, DNS, and a little monitoring. Small, but never zero.
  5. Optional services. For example AWS Elemental MediaConnect if you want Zixi or RIST delivery, and a CDN for viewer delivery on FAST and OTT. These are not in the numbers above.

Egress: the number to check first

A channel sending 10 Mbit/s all day, every day, moves about 3.2 TB a month. At list price that is roughly $280 on its own. Double the bitrate and the egress cost roughly doubles: 5 Mbit/s is about $140 a month, 8 Mbit/s about $225, 25 Mbit/s about $720.

For FAST and OTT the playout usually sends one stream to your CDN, and the CDN delivers to viewers. Viewer delivery is billed separately and grows with audience size (CDN list prices start around $85 per TB). We model only the origin stream here.

Redundancy: the second playout is a second bill

1+1 hot backup and warm standby

  • 1+1 hot backup. Two synchronised playouts with identical outputs, in one region or two. You pay for two sets of compute and egress. Your receiver or master control chooses which feed goes on air.
  • Warm standby. The second playout starts automatically within a few minutes of a failure. In the reference model it sits stopped until then and costs storage and a fixed IP, not compute. That makes it about $800 a month cheaper than a hot backup, in exchange for a few minutes’ delay when it takes over.
  • Multi-region. Traffic between regions adds a per-GB charge (about $0.02 per GB). We have not modelled this.

The right choice depends on how long you can be off air. A hot backup has no gap. A warm standby accepts a short one.

Cloud DR for an on-prem playout

If your primary playout is on-premises, a cloud DR channel can sit idle and cost little.

Cloud DR for an on-prem playout

Idle, you pay for the synchronised library and a reserved IP, about $100 a month in the reference model. An operator starts the DR playout within minutes when needed, and a full active day adds roughly $20 of compute. Outbound traffic for one day at 8 Mbit/s fits inside the free 100 GB.

Pop-up channels

An event channel running for 72 hours costs about $150 in the reference model, split between compute and storage, because compute is billed only while it runs.

What moves your bill

Lever Effect
Outbound bitrate Largest swing. 4 to 25 Mbit/s moves a linear HD channel by about $600 a month
Instance size One size up doubles compute (about $550 a month more from the reference size); one size down saves about $280
Library size Each extra TB in S3 adds about $24 a month
Number of playouts Costs scale almost linearly per playout
Hours running Pop-up and DR channels pay for compute only while running
Region Prices differ by region; ours are for Ireland (eu-west-1)
Your AWS agreement Enterprise discounts, savings plans and credits can lower your actual bill below list price

Assumptions

Item Assumption
Prices AWS on-demand list prices, eu-west-1, USD, November 2026
Hours 730 per month; egress on 30-day months
Instance A 16-vCPU class instance for every channel type, about $0.77 per hour. Smaller sizes may suit light channels
EBS 382 GB gp3 per playout (log 40, data 2, cache 300, HLS 40)
Library FAST/OTT 2 TB; linear HD 10 TB; DR 2 TB; pop-up 1 TB, in one S3 bucket
Outbound FAST/OTT 5 Mbit/s to CDN; linear HD 8 Mbit/s; both 24/7
Standby and DR Stopped playouts cost storage and an IP only (modelled assumption)
Fixed items $3.65 public IPv4, $0.50 DNS zone, $10 monitoring and other, per playout
Not included Playout software licence, CDN viewer delivery, MediaConnect, support plan, tax, data transfer between regions, backup of your own content

Your own numbers will differ. To price your exact setup, use the AWS Pricing Calculator. If you run, or are considering, Nimbus, talk to us and we will help you size it.

AWS changes its prices from time to time. Check current prices before you decide.

How Veset works with Amazon Web Services

Veset Nimbus runs on AWS: buy through AWS Marketplace, run playouts in your own AWS account or Veset's, with MediaConnect and MediaTailor.