Important: On December 31st 2024, AWS support for Media Services Application Mapper on AWS will end, and the GitHub repository will be archived. You will no longer be able to deploy Media Services Application Mapper on AWS via CloudFormation template within the AWS Console after this date. Existing deployments will continue to run. If you have deployed Media Services Application Mapper on AWS via cloning GitHub open-source code, you may continue to use the solution. If underlying service APIs change after solution support ends, deployments may error or may not be possible to stop / start.
The functionality provided by Media Services Application Mapper on AWS has been superseded with functionality in the new feature AWS Elemental workflow monitor a media-centric tool to simplify and elevate the monitoring of video workloads.
Overview
Media Services Application Mapper on AWS automatically provisions the services necessary to visualize media services, their relationships, and the real-time status of linear video services. This AWS solution features a browser application that includes both a tile view and a diagram view to help you identify the root cause of a problem when multiple media services are sending messages to Amazon CloudWatch.
Benefits
Aggregate resources into a single channel tile that represents a single streaming video channel. Each tile displays the aggregated media service configuration information for all resources included in the tile.
Visualize the relationships between your media services and the status of your resources and pipelines as workflow diagrams. You can also customize the solution to include custom node types or on-premises equipment.
You can customize or extend this solution for your specific needs. For example, add custom node types with the browser application, cache them into a database through a cloud-side task, and extend connection discovery and visualization overlay functionality to on-premises equipment.
Technical details
You can automatically deploy this architecture using the implementation guide.
Step 1
An Amazon CloudFront distribution to serve the Media Services Application Mapper on AWS web application.
Step 2
An Amazon Simple Storage Service (Amazon S3) bucket as an origin to serve the solution’s web application.
Step 3
Amazon API Gateway for inventory and monitoring queries to the solution’s backend.
Step 4
AWS Lambda functions to handle client REST API requests from API Gateway, periodically scan for media services resources, and receive notifications of changes in a resource’s status.
Two Lambda functions are custom resources for the browser application stack and one for the Amazon DynamoDB tables stack that are used during installation, update, and deletion.
Step 5
Amazon CloudWatch scheduled rules or event patterns to invoke the primary Lambda functions.
Step 6
DynamoDB tables to store the solution’s backend and front-end configuration and state.
Step 7
The AWS Cloud services and devices that this solution scans. The solution uses the AWS Elemental MediaLive API to discover AWS Elemental Link devices and the AWS Systems Manager API to discover AWS Elemental Live encoders.
Step 8
CloudWatch events to invoke the regional Lambda functions when there are operational changes in the sources of inventory or changes in state to subscribed CloudWatch alarms.
Step 9
Lambda functions to monitor source services for CloudWatch events in additional AWS Regions.
Step 1
An Amazon CloudFront distribution to serve the Media Services Application Mapper on AWS web application.
Step 2
An Amazon Simple Storage Service (Amazon S3) bucket as an origin to serve the solution’s web application.
Step 3
Amazon API Gateway for inventory and monitoring queries to the solution’s backend.
Step 4
AWS Lambda functions to handle client REST API requests from API Gateway, periodically scan for media services resources, and receive notifications of changes in a resource’s status.
Two Lambda functions are custom resources for the browser application stack and one for the Amazon DynamoDB tables stack that are used during installation, update, and deletion.
Step 5
Amazon CloudWatch scheduled rules or event patterns to invoke the primary Lambda functions.
Step 6
DynamoDB tables to store the solution’s backend and front-end configuration and state.
Step 7
The AWS Cloud services and devices that this solution scans. The solution uses the AWS Elemental MediaLive API to discover AWS Elemental Link devices and the AWS Systems Manager API to discover AWS Elemental Live encoders.
Step 8
CloudWatch events to invoke the regional Lambda functions when there are operational changes in the sources of inventory or changes in state to subscribed CloudWatch alarms.
Step 9
Lambda functions to monitor source services for CloudWatch events in additional AWS Regions.
Related content
Amazon CloudWatch is a monitoring service for AWS cloud resources and the applications you run on AWS. In this course you will learn about the capabilities and key terms of the service.
- Publish Date