Architecture overview
This section provides a reference implementation architecture diagram for the components deployed with this solution.
Architecture diagram
Deploying this solution with the default parameters builds the following configuration of resources in the AWS Cloud.
Media Services Application Mapper architecture on AWS
The AWS CloudFormation template deploys the following serverless infrastructure and web content for Media Services Application Mapper (MSAM) on AWS:
-
An Amazon CloudFront
distribution to serve the Media Services Application Mapper on AWS web application. -
An Amazon Simple Storage Service
(Amazon S3) bucket as an origin to serve the solution’s web application. -
Amazon API Gateway
for inventory and monitoring queries to the solution’s backend. -
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 DynamoDB tables stack that are used during installation, update, and deletion. -
Amazon CloudWatch
scheduled rules or event patterns to invoke the primary Lambda functions. -
Amazon DynamoDB
tables to store the solution’s backend and front-end configuration and state. -
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 Elemental Live encoders.
-
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.
-
Lambda functions to monitor source services for CloudWatch events in additional AWS Regions.
Note
Requests to and responses from the APIs are logged in Amazon CloudWatch. Lambda functions invoked by scheduled events or notification events also send log data to Amazon CloudWatch.
