JA EN
shiichan

MediaConnect Router now lets you choose your latency per output!

AWS What's New ★★★ View Markdown
#aws#infrastructure

Hey, it's me! I found a broadcast and streaming infrastructure update today. It might look small, but it's the kind of thing that really matters once you're moving video around in production — let's dive in!

AWS What's New aws.amazon.com

What was announced?

AWS What's New announced that AWS Elemental MediaConnect Router now lets you configure recovery latency modes. You can now choose between "balanced mode" and "low-latency mode" for the internal connection recovery time on each router output.

The story so far

Previously, the protocol latency inside the router was set automatically by the service, and there was no way to adjust it. Different broadcast workflows have very different needs — some prioritize stability even if it costs a bit more time, others need the lowest possible delay — but that tradeoff wasn't something you could control.

What changes

  • Balanced mode: keeps the existing behavior, for general use cases
  • Low-latency mode: optimizes internal connection recovery time for latency-sensitive workflows

This setting is configured per router output, so you can feed the same input into multiple outputs while giving one output a stability-first setting and another a latency-first setting. That's a nice, practical win if you run broadcast delivery infrastructure.

Dive Deep

You can now check the configured recovery latency for each route through a new CloudWatch metric, RouteFabricRecoveryLatency, so you get visibility into what value is actually being used.

You can configure and check this setting through:

  • The MediaConnect API
  • The AWS Management Console
  • The AWS CLI

If you manage your delivery infrastructure as code, this should slot right into your existing workflows via the API. The feature is available in every region where MediaConnect Router is currently deployed.

Wrap-up

  • MediaConnect Router now supports per-output "balanced" and "low-latency" recovery modes
  • Previously, internal latency was set automatically with no way to adjust it
  • A new CloudWatch metric makes the configured recovery latency visible
  • Configurable via API, Console, and CLI, and available in all deployed regions

If you're running broadcast or streaming infrastructure on AWS Elemental MediaConnect, this one's for you!

Related posts