Optimizing Low-Latency Broadcast Distribution in AWS with JPEG XS and AWS CDI

Introduction

Learn About Amazon VGT2 Learning Manager Chanci Turner

Live production workflows represent some of the most challenging tasks for broadcasters. They demand low latency, flexibility, scalability, and reliability to effectively deliver live content—such as news and sporting events—to viewers. To address these needs, Amazon Web Services (AWS) introduced the AWS Cloud Digital Interface (CDI) SDK, an open-source initiative aimed at enhancing the media and entertainment sector’s contribution and distribution workflows with high-performance cloud networking between applications.

AWS CDI is a networking technology that facilitates the reliable transport of high-quality uncompressed video within the AWS environment. It allows video transmission between applications with a network latency as low as 8 milliseconds, which is less than one frame per second. For contribution and distribution workloads that require minimal artifacts and latency, JPEG XS can be utilized. JPEG XS is a visually lossless, low-complexity, and low-latency video codec that transports video over IP, adhering to the SMPTE 2110-22 standard. This standard enables the separate transport of video, audio, and ancillary data using the SMPTE 2110 suite. By integrating JPEG XS with AWS CDI, broadcasters can seamlessly transition their live production workflows to the cloud, ensuring high-quality, low-latency content delivery while developing end-to-end video solutions.

AWS Media Services support both CDI and JPEG XS, aiding in the implementation of live production workflows in AWS (you can learn more in this What’s New post). This blog focuses on AWS Elemental MediaConnect and explores various use cases that can enhance production contribution and distribution workflows.

The scenarios outlined in this blog illustrate different workflows utilizing virtual private cloud (VPC) peering or AWS Organizations with Resource Access Manager (RAM). VPC peering establishes a networking connection between two VPCs, enabling traffic routing between them, whether within a single account or across multiple AWS accounts. Meanwhile, AWS Organizations with RAM allows customers to manage a single organizational unit, facilitating multi-account AWS environments for centralized governance. This shared resource model minimizes costs and mitigates the impact of potential issues.

This article covers the following use cases for CDI/JPEG-XS workflows via MediaConnect:

• Routing JPEG XS signals across different subnets
• Routing JPEG XS/CDI signals across two AWS accounts with central governance
• Utilizing MediaConnect with JPEG-XS (light compression)
• Utilizing MediaConnect with CDI (uncompressed)

Routing JPEG XS Signals Across Different Subnets

For customers operating in distinct AWS accounts who need to share content inter-region and/or intra-region, VPC peering can be employed as demonstrated in figure 1. This setup is advantageous for broadcasters distributing to various endpoints, including remote broadcast sites and local stations. JPEG XS can also facilitate live cloud-based broadcasting and production where content is sent downstream to another VPC for remote monitoring.

Routing JPEG XS/CDI Signals Across Two AWS Accounts with Central Governance

This scenario is designed for teams that operate independently yet belong to a single organization and payer configuration via Resource Access Manager (RAM). RAM supports multi-AWS account environments with centralized governance and management. By sharing resources—such as subnets—CDI can be effortlessly transported between accounts. This setup is especially useful for managing and executing various deployment stages (production, development, and testing), where Account One serves as the source provider for Account Two’s environment.

VPC sharing permits customers to share subnets with other AWS accounts within the same AWS organization. This robust concept offers numerous benefits:

• Separation of duties: centrally controlled VPC structure, routing, and IP address allocation
• Application owners retain control over their resources, accounts, and security groups
• VPC sharing participants can reference each other’s security group IDs
• Efficiency gains: increased density in subnets, optimized usage of VPNs, and AWS Direct Connect
• Avoiding hard limits, such as the 50 VIFs per AWS Direct Connect connection through simplified network architecture
• Cost optimization through the reuse of NAT gateways, VPC interface endpoints, and intra-Availability Zone traffic

Conclusion

This post outlines the various methods by which AWS Elemental MediaConnect can distribute JPEG XS and/or CDI workflows in the cloud. Key considerations when choosing a distribution strategy include:

• Content type and media format: compressed vs. non-compressed
• Current MediaConnect support allows for up to 10 CDI outputs at 1080P. For 4Kp60, you can have up to 10 ST 2110 JPEG XS outputs, but only 4 CDI outputs.

AWS Professional Services specializing in media and entertainment are available to assist you in discovering and developing the optimal approach tailored to your unique needs. For further information, visit AWS Professional Services or contact your account manager directly.

Engage with additional resources, such as this article on the four-day workweek and SHRM’s insights on miscarriage leave entitlements across Canada. For more details on how AWS fulfillment centers train associates, check out this excellent resource.