media server logo
API docsLaunch in AWS

Akamai Cdn

Mar 06, 2026

Introduction

This is a practical guide to using akamai-cdn for low-latency live streaming where contribution uses SRT. It’s written for streaming engineers and operations teams who need concrete decisions, configuration values, and a checklist to run a reliable 2–5 second live stream using SRT to an encoder or Akamai Media Services Live, then packaging via CMAF/LL-HLS or LL-DASH and delivery via Akamai Adaptive Media Delivery. For this workflow, teams usually combine Player & embed, Ingest & route, and Paywall & access. Before full production rollout, run a Test and QA pass with Generate test videos and streaming quality check and video preview. Before full production rollout, run a Test and QA pass with a test app for end-to-end validation.

Keywords: Low latency live video streaming via SRT

Decisions you must make before implementation

  • Latency target: pick a clear target. Sub-second requires WebRTC; 2–5s is realistic globally with chunked CMAF + CDN; 10–30s is standard HLS.
  • Ingest protocol: use SRT for reliable contribution (encoder → edge or encoder → Media Services Live). SRT is for contribution only—not a player delivery protocol.
  • Packaging & distribution: choose chunked CMAF with LL-HLS or LL-DASH for CDN distribution. Use WebRTC only if you need sub-second interactivity.
  • Where to package: prefer Akamai Media Services Live for SRT ingest + packaging (less operational overhead). Self-managed packager (Shaka Packager / Bento4) is OK for custom needs.
  • Origin and caching: origin can be NetStorage, S3, or Media Services Live. Use Akamai Adaptive Media Delivery (AMD) with Origin Shield for cache consistency and lower origin load.
  • Security and auth: use SRT encryption (passphrase/AES) for contribution and token-based URL signing or EdgeWorkers for distribution authentication and anti-leeching.
  • Player support: confirm target players support LL-HLS/LL-DASH (Safari, HLS.js low-latency builds, Shaka with CMAF). Have fallbacks to standard HLS for unsupported clients.

Practical configurations (what to set and why)

SRT ingest — recommended settings

SRT is resilient to jitter and packet loss when configured correctly. Key parameters you will set on the encoder or SRT client:

  • URL pattern: srt://[SRT_INGEST_HOST]:[PORT]?streamid=publish/[STREAM_KEY]&latency=2000&pkt_size=1316
  • latency: 1500–5000 ms. Start at 2000 ms (2s) in real networks, increase if packet retransmits are visible. Lowering latency increases packet loss risk.
  • pkt_size: 1316 (typical for live); tune for MTU on path.
  • encryption: enable AES (SRT supports passphrase); use a strong passphrase and rotate periodically.
  • streamid: pass stream identifier/publish key so edge or Media Services Live can route the feed.

Example ffmpeg push (encoder → Akamai SRT ingest endpoint placeholder):

ffmpeg -re -i input -c:v libx264 -preset veryfast -g 48 -keyint_min 48 -sc_threshold 0 \
-b:v 4000k -maxrate 4500k -bufsize 9000k -c:a aac -b:a 128k \
-f mpegts "srt://srt-ingest.example.akamaized.net:10000?streamid=publish/stream123&pkt_size=1316&latency=2000"

Encoder and packaging (CMAF chunking) — key parameters

To achieve low end-to-end latency you must align encoder keyframes with packaging segments and produce small CMAF chunks:

  • Keyframe / GOP: set a fixed keyframe interval aligned to segment duration. Example: segment duration = 2s → GOP/keyframe = 2s (for 25 fps, keyframe every 50 frames).
  • Segment duration: 2s segments are a good balance for 2–5s latency.
  • Chunk (fragment) duration: 200–500 ms per chunk inside each segment (CMAF fMP4 chunking). Smaller chunk gives lower latency but more HTTP requests and CPU overhead.
  • Codec & profiles: H.264 High profile (or HEVC if supported) with CBR or constrained VBR for stable delivery; AAC-LC audio 48 kHz.
  • ABR ladder: provide 4–6 renditions. Example ladder: 6 Mbps (1080p60), 4 Mbps (1080p30/720p60), 3 Mbps (720p30), 1.5 Mbps (480p), 800 kbps (360p), 300 kbps (audio+small video).
  • Packager: prefer Media Services Live for automatic SRT ingest → packaging to CMAF + HLS/DASH manifests. If self-hosting use Shaka Packager or Bento4 with fragment_duration=200–250 ms and segment_duration=2s.

Akamai CDN configuration — Adaptive Media Delivery & edge settings

Set these rules in Akamai Control Center or provide them to your Akamai contact:

Use the bitrate calculator to size the workload, or build your own licence with Callaba Self-Hosted if the workflow needs more flexibility and infrastructure control. Managed launch is also available through AWS Marketplace.