This Guidance shows you how to transition your linear playout origination and master control operations to the cloud. By harnessing computing capacity, storage options, and the extensive Media Services offerings of AWS, you can achieve efficient resource allocation, scalability, cost effectiveness, and resiliency. This Guidance provides best practices, helping you modernize your content delivery and viewer engagement while optimizing operational efficiency.

Please note: [Disclaimer]

Architecture Diagram

[Architecture diagram description]

Download the architecture diagram PDF 

Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

  • This Guidance uses CloudWatch and Amazon Managed Grafana to let you visualize and analyze operating system states, helping you quickly identify and remediate noncompliant components. You can then use Lambda to invoke actions based on events or alarms created by these monitoring components. Lambda lets you implement complex incident recovery logic for multiple systems, supporting operators by removing complex manual tasks. Additionally, this Guidance simplifies resource management by using AWS Systems Manager Patch Manager to automatically scan and patch Amazon EC2 instances.

    Read the Operational Excellence whitepaper 

  • This Guidance lets you scope down AWS Identity and Access Management (IAM) policies to the minimum permissions required for your Guidance to function properly, helping you limit unauthorized access to resources. Additionally, Secrets Manager stores all passwords required to access the bastion servers and application interfaces and helps you protect access to resources.

    Read the Security whitepaper 

  • This Guidance uses two AZs, reducing the risk of AZ-level events impacting the output of your system. Additionally, AWS media services like MediaLive and MediaConnect support redundant primary and backup inputs, helping you build resilient video workflows. Lambda adds resiliency and reliability to your workflows through automatic scaling, retries, and high availability.

    Read the Reliability whitepaper 

  • This Guidance uses CloudWatch to collect and visualize near real-time logs, metrics, and event data in automated dashboards, helping you streamline infrastructure and application maintenance. You can easily monitor various metrics that indicate optimal instance sizing for applications running on Amazon EC2. Additionally, you can use MediaConnect in conjunction with protocols, such as Real-time Transport Protocol (RTP) with forward error correction or Secure Reliable Transport (SRT), to deliver video at a high rate without packet loss.

    Read the Performance Efficiency whitepaper 

  • This Guidance lets you take advantage of highly predictable baseline usage requirements and reduce your data transfer costs by making a long-term commitment through MediaConnect reserved output bandwidth. MediaConnect and MediaLive pricing is based on the output bitrate of the video feeds being processed, so you can optimize costs by tuning the video and encoding quality. MediaLive also supports reserved pricing for inputs, outputs, and add-on features. Additionally, AWS ISV products, such as broadcast routers and playout engines, run on Amazon EC2 instances and have stable 24/7 workloads. Savings Plans can help reduce the cost of 24/7 operations.

    Read the Cost Optimization whitepaper 

  • This Guidance uses managed services such as MediaConnect, Lambda, Amazon Managed Grafana, and Amazon Simple Storage Service (Amazon S3), minimizing workload requirements. MediaConnect scales based on demand so you don’t have to manage the underlying infrastructure. This reduces waste and energy consumption, ultimately helping you reduce your carbon footprint.

    Read the Sustainability whitepaper 

Disclaimer

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.

References to third-party services or organizations in this Guidance 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 the architecture.

Was this page helpful?

 Feedback