Skip to main content

AWS Solutions Library

Guidance for Event-Driven Media Workflow Automation on AWS

Overview

This Guidance illustrates how media and entertainment (M&E) customers can leverage AWS services to automate and optimize their end-to-end media supply chain workflows. By implementing an event-driven, serverless architecture, M&E companies can streamline processes across various domains like asset management, metadata handling, rights management, editing, packaging, delivery, quality control, and distribution. This solution integrates with multiple AWS independent software vendor (ISV) offerings, enabling a seamless and efficient content management lifecycle. Key benefits include reduced operational costs, fewer manual tasks and errors, improved time-to-market, and unlocked monetization opportunities through innovative content delivery models. This Guidance empowers M&E businesses to build a scalable, cost-effective media supply chain that delivers high-quality content experiences to audiences worldwide while staying competitive in the dynamic media landscape.

How it works

Overview

This diagram gives an overview of how to integrate event-driven third-party partner services and applications into your AWS account. The subsequent tabs show how to integrate this Guidance with various third-party events.

Download the architecture diagram PDF
Missing alt text value

Amazon SNS FIFO event to Amazon SQS FIFO

This diagram shows how to integrate third-party events that are produced from an Amazon EventBridge third-party event source and delivered to an EventBridge Event Bus in your AWS account.

Download the architecture diagram PDF
Architecture diagram showing AWS event-driven integration and routing workflows using Amazon SNS, SQS, Lambda, EventBridge, Step Functions, and DynamoDB for handling events from multiple sources to various destinations including partner SaaS, applications, and AWS services.

Amazon EventBridge Event Bus SaaS Integration

This diagram shows how to integrate third-party events that are produced from an Amazon EventBridge third-party event source and delivered to an EventBridge Event Bus in your AWS account.

Download the architecture diagram PDF
Missing alt text value

How it works (continued)

Amazon EventBridge Custom Event Bus Integration

This diagram shows how to integrate partner events that are produced from a partner’s Software as a Service (SaaS) or your application. The events are delivered to an Amazon EventBridge custom event bus in your AWS account.

Download the architecture diagram PDF
Missing alt text value

Amazon SQS to AWS Lambda Integration

This diagram shows how to integrate partner events that are produced by an Amazon SQS queue with an AWS Lambda function in your AWS account.

Download the architecture diagram PDF
Missing alt text value

Partner Webhook Integration

This diagram shows how to integrate partner events produced by a partner webhook with an Amazon API Gateway endpoint.

Download the architecture diagram PDF
Missing alt text value

Well-Architected Pillars

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 services managed by AWS like Amazon SQS , Lambda , API Gateway , EventBridge , Step Functions , and DynamoDB to enhance operational excellence. These services operate at the Regional level, utilizing multiple Availability Zones for high availability and fault tolerance. Built-in error handling and dead-letter queues provide visibility into failures, enabling timely detection and mitigation. The serverless nature of these services simplifies operations and reduces operational overhead.

Read the Operational Excellence whitepaper 

AWS Identity and Access Management (IAM), Lambda , API Gateway , Amazon SQS , and DynamoDB contribute to a secure architecture. IAM enables granular access control and least-privilege access to resources. API Gateway authorizes inbound API requests, while Amazon SQS queue policies manage queue access. DynamoDB encrypts data at rest using keys managed by AWS.

Read the Security whitepaper 

EventBridge automatically retries failed event deliveries and sends unprocessed events to a dead-letter queue. Lambda functions can be configured to send failed events to an Amazon SQS dead-letter queue for further analysis and processing. This fault tolerance and error handling ensure reliable event processing and prevent data loss.

Read the Reliability whitepaper 

The event-driven microservices architecture, built with serverless services like Lambda , Amazon SQS , and EventBridge , automatically scales based on demand, ensuring optimal resource utilization. Furthermore, DynamoDB allows for decoupled storage, scaling throughput and capacity independently to meet performance requirements.

Read the Performance Efficiency whitepaper 

This Guidance optimizes costs through the effective use of AWS services that follow a pay-as-you-go pricing model, charging only for the resources consumed during event processing. For example, the serverless nature of Lambda enables right-sizing compute resources to match workload demands, preventing over-provisioning. Amazon SQS and Amazon SNS minimize data transfer costs by efficiently routing and delivering events. DynamoDB offers cost-effective storage and granular capacity provisioning, allowing independent scaling of throughput and storage based on requirements.

Read the Cost Optimization whitepaper 

EventBridge , Lambda , API Gateway , Amazon SQS , and Amazon SNS contribute to sustainability by minimizing inactive resource usage. These serverless services are active only when processing events, reducing energy consumption and your infrastructure footprint. The event-driven microservices architecture with Lambda further optimizes resource utilization by running only the necessary code, minimizing the overall environmental impact.

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.