Broadcast
Operations, Monitoring & Control
Broadcasters achieve flexibility, cost savings, and performance by running channel playout and distribution on AWS, but they also seek the same level of control and visibility into their broadcast workloads as they enjoy on-premises. This demonstration showcases an end-to-end monitoring and observability environment built using AWS services as well as open-source software and AWS Partner solutions. It allows operators with little or no cloud-specific skills to spin up playout channels and distribution pipelines, and provides an end-to-end view of their signal path, including real-time monitoring of video/audio quality, underlying infrastructure, and application-level performance and alerts. This enables customers to construct familiar MCR-style environments in the cloud for their channel playout and distribution workloads without compromising on the observability or automation they are accustomed to on-premises. (This demonstration won a NAB Show 2024 Product of the Year Award for Monitoring and Measuring Tools.)
Architecture
-
Architecture slide 1
-
Architecture slide 2
-
Architecture slide 3
-
Architecture slide 4
-
Architecture slide 1
-
Click image to zoom 🔍
-
Architecture slide 2
-
Click image to zoom 🔍
-
Architecture slide 3
-
Click image to zoom 🔍
-
Architecture slide 4
-
Click image to zoom 🔍
Featured Demo Partners
_______
Meet with an AWS M&E specialist
Disclaimer
References to third-party services or organizations on this page do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy them.
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.