[SEO Subhead]
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.
Please note: [Disclaimer]
Architecture Diagram
-
Overview
-
Amazon SNS FIFO event to Amazon SQS FIFO
-
Amazon EventBridge Event Bus SaaS Integration
-
Amazon EventBridge Custom Event Bus Integration
-
Amazon SQS to AWS Lambda Integration
-
Partner Webhook Integration
-
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.
Click to enlarge
Step 1
Partner Software as a Service (SaaS) applications, partner applications, your application, or an AWS service send events to your AWS account.Step 2
Amazon Simple Queue Service (Amazon SQS), AWS Lambda, Amazon API Gateway, or Amazon EventBridge receive events produced from step one.
Step 3
EventBridge rules route events to Lambda to be enriched and transformed. Skip this step if there is no need for enrichment or transformation.Step 4
EventBridge rules route events to a destination. Rules use event pattern matching to route events based on their contents.Step 5
Lambda sends event data to downstream services. If multiple steps are required, AWS Step Functions starts a multi-step workflow using the event. Skip this step if there is no need for additional processing.
Step 6
Downstream services, such as a partner SaaS, a locally deployed partner application, your application, a third-party application, an AWS service, or your data lake, receive the event data.Step 7
Amazon SQS dead-letter queue (DLQ) receives events not successfully processed from previous steps. Amazon SQS will re-drive and process the events. If re-driven events are unsuccessful, Lambda writes the event to an Amazon DynamoDB table for manual review.Step 1
Partner Software as a Service (SaaS) applications, partner applications, your application, or an AWS service send events to your AWS account.Step 2
Amazon Simple Queue Service (Amazon SQS), AWS Lambda, Amazon API Gateway, or Amazon EventBridge receive events produced from step one.
Step 3
EventBridge rules route events to Lambda to be enriched and transformed. Skip this step if there is no need for enrichment or transformation.Step 4
EventBridge rules route events to a destination. Rules use event pattern matching to route events based on their contents.Step 5
Lambda sends event data to downstream services. If multiple steps are required, AWS Step Functions starts a multi-step workflow using the event. Skip this step if there is no need for additional processing.
Step 6
Downstream services, such as a partner SaaS, a locally deployed partner application, your application, a third-party application, an AWS service, or your data lake, receive the event data.Step 7
Amazon SQS dead-letter queue (DLQ) receives events not successfully processed from previous steps. Amazon SQS will re-drive and process the events. If re-driven events are unsuccessful, Lambda writes the event to an Amazon DynamoDB table for manual review. -
Amazon SNS FIFO event to Amazon SQS FIFO
-
This diagram shows how to integrate third-party events into your AWS account that are produced from an Amazon SNS FIFO (first in, first out) topic. These topics are delivered to a subscribed Amazon SQS FIFO queue.
Click to enlarge
Step 1
Partner SaaS applications, partner applications, or your application send events to your AWS account.Step 2
An Amazon SQS queue or Amazon Simple Notification Service (Amazon SNS) topic receives events from a third-party service. Use FIFO (first in, first out) queues with FIFO topics for ordered processing. Ensure the queue and topic types match—either FIFO or standard.Step 3
EventBridge rules route events to Lambda to be enriched and transformed. Skip this step if there is no need for enrichment or transformation.Step 4
EventBridge rules route events to a destination. Rules use event pattern matching to route events based on their contents.Step 5
Lambda sends event data to downstream services. If multiple steps are required, Step Functions starts a multi-step workflow using the event. Skip this step if there is no need for additional processing.Step 6
Downstream services, such as partner SaaS, a locally deployed partner application, your application, a third-party application, an AWS service, or your data lake, receive the event data.Step 7
Amazon SQS DLQ receives events not successfully processed from previous steps. Amazon SQS will re-drive and process the events. If re-driven events are unsuccessful, Lambda writes the event to a DynamoDB table for manual review.Step 1
Partner SaaS applications, partner applications, or your application send events to your AWS account.Step 2
An Amazon SQS queue or Amazon Simple Notification Service (Amazon SNS) topic receives events from a third-party service. Use FIFO (first in, first out) queues with FIFO topics for ordered processing. Ensure the queue and topic types match—either FIFO or standard.Step 3
EventBridge rules route events to Lambda to be enriched and transformed. Skip this step if there is no need for enrichment or transformation.Step 4
EventBridge rules route events to a destination. Rules use event pattern matching to route events based on their contents.Step 5
Lambda sends event data to downstream services. If multiple steps are required, Step Functions starts a multi-step workflow using the event. Skip this step if there is no need for additional processing.Step 6
Downstream services, such as partner SaaS, a locally deployed partner application, your application, a third-party application, an AWS service, or your data lake, receive the event data.Step 7
Amazon SQS DLQ receives events not successfully processed from previous steps. Amazon SQS will re-drive and process the events. If re-driven events are unsuccessful, Lambda writes the event to a DynamoDB table for manual review. -
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.
Click to enlarge
Step 1
Partner SaaS applications send events to your AWS account.Step 2
The EventBridge partner event source provisions a SaaS partner event bus into your account. The event bus receives partner events, and if necessary, an EventBridge rule routes the events to Lambda for transformation.Step 3
EventBridge rules route events to Lambda to be enriched and transformed. Skip this step if there is no need for enrichment or transformation.Step 4
EventBridge rules route events to a destination. Rules use event pattern matching to route events based on their contents.Step 5
Lambda sends event data to downstream services. If multiple steps are required, Step Functions starts a multi-step workflow using the event. Skip this step if there is no need for additional processing.Step 6
Downstream services, such as partner SaaS, a locally deployed partner application, your application, a third-party application, an AWS service, or your data lake, receive the event data.Step 7
Amazon SQS DLQ receives events not successfully processed from previous steps. Amazon SQS will re-drive and process the events. If re-driven events are unsuccessful, Lambda writes the event to a DynamoDB table for manual review.Step 1
Partner SaaS applications send events to your AWS account.Step 2
The EventBridge partner event source provisions a SaaS partner event bus into your account. The event bus receives partner events, and if necessary, an EventBridge rule routes the events to Lambda for transformation.Step 3
EventBridge rules route events to Lambda to be enriched and transformed. Skip this step if there is no need for enrichment or transformation.Step 4
EventBridge rules route events to a destination. Rules use event pattern matching to route events based on their contents.Step 5
Lambda sends event data to downstream services. If multiple steps are required, Step Functions starts a multi-step workflow using the event. Skip this step if there is no need for additional processing.Step 6
Downstream services, such as partner SaaS, a locally deployed partner application, your application, a third-party application, an AWS service, or your data lake, receive the event data.Step 7
Amazon SQS DLQ receives events not successfully processed from previous steps. Amazon SQS will re-drive and process the events. If re-driven events are unsuccessful, Lambda writes the event to a DynamoDB table for manual review. -
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.
Click to enlarge
Step 1
Partner SaaS applications, partner applications, or your application send events to your AWS account.Step 2
An AWS Partner SaaS platform or AWS Partner custom app writes events to the EventBridge custom event bus. The event bus receives partner events, and if necessary, an EventBridge rule routes the events to Lambda for transformation.Step 3
EventBridge rules route events to Lambda to be enriched and transformed. Skip this step if there is no need for enrichment or transformation.Step 4
EventBridge rules route events to a destination. Rules use event pattern matching to route events based on their contents.Step 5
Lambda sends event data to downstream services. If multiple steps are required, Step Functions starts a multi-step workflow using the event. Skip this step if there is no need for additional processing.Step 6
Downstream services, such as partner SaaS, a locally deployed partner application, your application, a third-party application, an AWS service, or your data lake, receive the event data.Step 7
Amazon SQS DLQ receives events not successfully processed from previous steps. Amazon SQS will re-drive and process the events. If re-driven events are unsuccessful, Lambda writes the event to a DynamoDB table for manual review.Step 1
Partner SaaS applications, partner applications, or your application send events to your AWS account.Step 2
An AWS Partner SaaS platform or AWS Partner custom app writes events to the EventBridge custom event bus. The event bus receives partner events, and if necessary, an EventBridge rule routes the events to Lambda for transformation.Step 3
EventBridge rules route events to Lambda to be enriched and transformed. Skip this step if there is no need for enrichment or transformation.Step 4
EventBridge rules route events to a destination. Rules use event pattern matching to route events based on their contents.Step 5
Lambda sends event data to downstream services. If multiple steps are required, Step Functions starts a multi-step workflow using the event. Skip this step if there is no need for additional processing.Step 6
Downstream services, such as partner SaaS, a locally deployed partner application, your application, a third-party application, an AWS service, or your data lake, receive the event data.Step 7
Amazon SQS DLQ receives events not successfully processed from previous steps. Amazon SQS will re-drive and process the events. If re-driven events are unsuccessful, Lambda writes the event to a DynamoDB table for manual review. -
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.
Click to enlarge
Step 1
Partner SaaS applications, partner applications, or your application send events to your AWS account.Step 2
Lambda polls an AWS Partner SaaS or an AWS customer application’s Amazon SQS queue. Lambda receives events from the Amazon SQS subscription and performs any needed transformation.Step 3
EventBridge rules route events to Lambda to be enriched and transformed. Skip this step if there is no need for enrichment or transformation.Step 4
EventBridge rules route events to a destination. Rules use event pattern matching to route events based on their contents.Step 5
Lambda sends event data to downstream services. If multiple steps are required, Step Functions starts a multi-step workflow using the event. Skip this step if there is no need for additional processing.Step 6
Downstream services, such as partner SaaS, a locally deployed partner application, your application, a third-party application, an AWS service, or your data lake, receive the event data.Step 7
Amazon SQS DLQ receives events not successfully processed from previous steps. Amazon SQS will re-driven and process the events. If re-drive events are unsuccessful, Lambda writes the event to a DynamoDB table for manual review.Step 1
Partner SaaS applications, partner applications, or your application send events to your AWS account.Step 2
Lambda polls an AWS Partner SaaS or an AWS customer application’s Amazon SQS queue. Lambda receives events from the Amazon SQS subscription and performs any needed transformation.Step 3
EventBridge rules route events to Lambda to be enriched and transformed. Skip this step if there is no need for enrichment or transformation.Step 4
EventBridge rules route events to a destination. Rules use event pattern matching to route events based on their contents.Step 5
Lambda sends event data to downstream services. If multiple steps are required, Step Functions starts a multi-step workflow using the event. Skip this step if there is no need for additional processing.Step 6
Downstream services, such as partner SaaS, a locally deployed partner application, your application, a third-party application, an AWS service, or your data lake, receive the event data.Step 7
Amazon SQS DLQ receives events not successfully processed from previous steps. Amazon SQS will re-drive and process the events. If re-driven events are unsuccessful, Lambda writes the event to a DynamoDB table for manual review. -
Partner Webhook Integration
-
This diagram shows how to integrate partner events produced by a partner webhook with an Amazon API Gateway endpoint.
Click to enlarge
Step 1
Partner SaaS applications send events to your AWS account.Step 2
API Gateway receives HTTP API calls from third-party applications. Lambda receives the HTTP API call, processes the request, and responds to the third-party application.Step 3
EventBridge rules route events to Lambda to be enriched and transformed. Skip this step if there is no need for enrichment or transformation.Step 4
EventBridge rules route events to a destination. Rules use event pattern matching to route events based on their contents.Step 5
Lambda sends event data to downstream services. If multiple steps are required, Step Functions starts a multi-step workflow using the event. Skip this step if there is no need for additional processing.Step 6
Downstream services, such as partner SaaS, a locally deployed partner application, your application, a third-party application, an AWS service, or your data lake, receive the event data.Step 7
Amazon SQS DLQ receives events not successfully processed from previous steps. Amazon SQS will re-drive and process the events. If re-driven events are unsuccessful, Lambda writes the event to a DynamoDB table for manual review.Step 1
Partner SaaS applications send events to your AWS account.Step 2
API Gateway receives HTTP API calls from third-party applications. Lambda receives the HTTP API call, processes the request, and responds to the third-party application.Step 3
EventBridge rules route events to Lambda to be enriched and transformed. Skip this step if there is no need for enrichment or transformation.Step 4
EventBridge rules route events to a destination. Rules use event pattern matching to route events based on their contents.Step 5
Lambda sends event data to downstream services. If multiple steps are required, Step Functions starts a multi-step workflow using the event. Skip this step if there is no need for additional processing.Step 6
Downstream services, such as partner SaaS, a locally deployed partner application, your application, a third-party application, an AWS service, or your data lake, receive the event data.Step 7
Amazon SQS DLQ receives events not successfully processed from previous steps. Amazon SQS will re-drive and process the events. If re-driven events are unsuccessful, Lambda writes the event to a DynamoDB table for manual review.
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.
-
Operational ExcellenceRead the Operational Excellence whitepaper
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.
-
SecurityRead the Security 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.
-
ReliabilityRead the Reliability 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.
-
Performance EfficiencyRead the Performance Efficiency 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.
-
Cost OptimizationRead the Cost Optimization 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.
-
SustainabilityRead the Sustainability 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.
Implementation Resources
A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.
The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.
Related Content
[Title]
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.