Amazon Web Services (AWS) offers several media services that make it fast and easy to prepare, process, and deliver broadcast and over-the-top video from the AWS Cloud. These pay-as-you-go services replace costly, hardware-based video infrastructure to deliver great viewing experiences on multiple screens.

It can be a challenge to understand the workflow relationships between different media services and identify the root cause of a problem when multiple media services are sending messages to Amazon CloudWatch, a monitoring and management service.

This webpage introduces an AWS solution that automatically provisions the services necessary to visualize media services, their relationships, and the real-time status of linear video services.

The following sections assume basic knowledge of architecting on the AWS Cloud and media service workflows.

AWS offers a solution that displays the logical connections between media services, visualizes error messages and counts, and produces a list of confidence-ranked root causes for problematic workflows. The diagram below presents the architecture you can deploy in minutes using the solution's implementation guide and accompanying AWS CloudFormation template.

  1. An AWS CloudFormation template configures the solution's core AWS services, which includes a suite of AWS Lambda microservices (functions) that manage the inventory, connections, alarms, and events of your media services.
  2. Amazon API Gateway hosts the solution’s RESTful APIs.
  3. Amazon CloudWatch invokes the solution's microservices which monitor your media service resources and stores information about them in Amazon DynamoDB tables.
  4. The solution also deploys a browser application that visualizes the relationships between your media services, and the status of your resources and pipelines as a workflow diagram using the information in DynamoDB.
  5. Currently, the solution monitors AWS Elemental MediaLive, AWS Elemental MediaPackage, Amazon Simple Storage Service, and Amazon CloudFront.
Deploy Solution
Implementation Guide

What you'll accomplish:

Deploy Media Services Application Mapper using AWS CloudFormation. The AWS CloudFormation template will automatically launch and configure the components necessary to visualize media services, their relationships, and the real-time status of linear video services.

Automatically monitor your media service resources using Amazon CloudWatch, AWS Lambda, and Amazon DynamoDB.

What you'll need before starting:

An AWS account: You will need an AWS account to begin provisioning resources. Sign up for AWS.

Skill level: This solution is intended for IT infrastructure architects, administrators, and DevOps professionals who have experience with media workflows, and practical experience architecting on the AWS Cloud.

Workflow Diagrams

The Media Services Application Mapper enables you to track your media services in real-time. You can visualize the relationships between your media services and the status of your resources and pipelines as workflow diagrams. Workflow diagrams show your media service resources, their connections, and their status.

You can also customize the solution to include custom node types or on-premise equipment in workflow diagrams.


Channel Tiles

Channel tiles aggregate resources into a single item that represents a single streaming video channel. Each tile displays the aggregated media service configuration information for all resources included in the file. You can select the tile to see the tile’s resources on a workflow diagram.  


Q: Can I customize or extend this solution for my specific needs?

Yes. The Media Services Application Mapper is designed to be customized or extended. For example, you can add custom node types with the browser application, or by caching them into a database through a cloud-side task. You can also extend connection discovery and visualization overlay functionality to on-premise equipment.  

Q: Does this solution support Amazon DynamoDB auto scaling?

Yes. By default, each DynamoDB table is set to scale when recent operations exceed 50% of read/write capacity. The maximum provisioned capacity is set to 5,000 units. We recommend setting alarms and notifications for throttling errors, if utilization exceeds 75%, or if any table exceeds read/write capacity units.  

Q: Where can I find the source code for this solution?

You can visit the GitHub repository to download the templates and scripts for this solution and share your customizations with others.   

Need more resources to get started with AWS? Visit the Getting Started Resource Center to find tutorials, projects and videos to get started with AWS.

Tell us what you think