Overview
This Guidance demonstrates how to deploy a media lake, which addresses media management challenges for organizations of all sizes using AWS services and partner integrations. It shows how to create a centralized system for managing digital media assets throughout their lifecycle, featuring automated and manual media workflows, global namespace organization, and advanced metadata management. The Guidance helps implement human-in-the-loop review capabilities and a unified media, archive, and metadata data catalog that connects through API and user interface layers. By following this Guidance, organizations can optimize processing times, reduce costs, and enhance content monetization.
Benefits
How it works
Overview
This architecture diagram provides a functional overview of the capabilities of a media lake on AWS.

High-level application architecture
This architecture diagram shows the high-level API, storage, and back-end architecture of a media lake on AWS.

Pipeline execution and deployment
This architecture diagram shows the deployment and execution of pipelines used in a media lake to process media and produce metadata to aid search and render new versions for use with downstream systems.

Deploy with confidence
Ready to deploy? Review the sample code on GitHub for detailed deployment instructions to deploy as-is or customize to fit your needs.
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.
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages