AWS solutions documentation change
Summary
Added new solution guide for Cloud-Native Fast-Turnaround Media Workflows using Time Addressable Media Store (TAMS) API, including architecture diagrams, workflow steps, implementation details, and Well-Architected Pillars analysis.
Security assessment
The documentation describes security features like Amazon S3 pre-signed URLs for time-limited access and Amazon Cognito for authentication, but doesn't indicate any security vulnerability being fixed. Security documentation is added in the 'Security' pillar section explaining access control mechanisms.
Diff
diff --git a/solutions/cloud-native-fast-turnaround-media-workflows-on-aws/index.md b/solutions/cloud-native-fast-turnaround-media-workflows-on-aws/index.md index 8b1378917..501e8e2f9 100644 --- a//solutions/cloud-native-fast-turnaround-media-workflows-on-aws/index.md +++ b//solutions/cloud-native-fast-turnaround-media-workflows-on-aws/index.md @@ -0,0 +1 @@ +# Guidance for Cloud-Native Fast-Turnaround Media Workflows on AWS @@ -1,0 +3,257 @@ +[ Open guide ](https://aws-solutions-library-samples.github.io/media-entertainment/cloud-native-fast-turnaround-media-workflows-on-aws/index.html)[ Go to sample code ](https://github.com/aws-solutions-library-samples/guidance-for-cloud-native-fast-turnaround-media-workflows-on-aws) + +## Overview + +This Guidance demonstrates new tools for media workflows in cloud environments as part of the Cloud-Native Agile Production (CNAP) program. This initiative builds upon the Time Addressable Media Store (TAMS) API specification, originally developed by the British Broadcasting Corporation's Research & Development team. The aim of the CNAP program is to drive industry adoption of TAMS as a cloud-native, open, and interoperable framework for fast-turnaround media workflows in the creation of News, Sports, and Entertainment content. TAMS stores media as discrete chunks in object storage, accessible through an open-source API. This approach eliminates common challenges found in traditional cloud-based media workflows. By using timing and identity as primary identifiers, TAMS enables content-centric workflows that reduce duplicate content and scale effectively, unlike traditional file-based systems. + +## How it works + +TAMS concept overview + +This architecture diagram shows the concept about how a Time Addressable Media Store (TAMS) sits at the core of a fast-turnaround workflow for processing live or near-live video and audio content. + +[ Download the architecture diagram. ](https://d1.awsstatic.com/solutions/guidance/architecture-diagrams/cloud-native-fast-turnaround-media-workflows-on-aws.pdf)  Step 1 + +All media is stored within a Time Addressable Media Store (TAMS). This holds chunked media on object storage with an API to provide the link between content and the media essence. + +Step 2 + +Live video feeds are uploaded as small chunks of media and registered with the TAMS to provide the effect of growing content. + +Step 3 + +File-based content can be uploaded natively or chunked prior to import as required. + +Step 4 + +Content can be processed in near real-time, generating additional versions, such as proxies, triggered through notifications from the storage system. + +Step 5 + +Content analysis can occur asynchronously and in near real-time, enabling rapid access to the outputs of machine learning and artificial intelligence (AI/ML) models. Examples include live subtitling, highlights generation, and content logging. + +Step 6 + +Simple clip-based editing can be performed, and the resulting edits can be published back to the TAMS, referencing the original content. + +Step 7 + +Craft editing can access content from the TAMS and publish back only new segments. + +Step 8 + +Content from the store can be played back as a real-time video stream into production galleries of linear channel playout facilities. + +Step 9 + +TAMS API can be easily converted into HTTP Live Streaming (HLS) manifests to enable live or on-demand content streaming from the TAMS. + +Step 10 + +Clips and files can be exported from the store for alternative purposes, such as the rapid distribution of content onto social media platforms. + +Step 11 + +The Media Asset Management (MAM) system maintains references to the content stored within the TAMS, along with the associated rich editorial and time-based metadata. + +TAMS data structure + +This architecture diagram shows the high-level data structure represented in the TAMS API specification. This diagram establishes the connection between the content that a user would be aware of and the actual media essence, which is stored in multiple formats and segments on the object storage system. + +[ Download the architecture diagram. ](https://d1.awsstatic.com/solutions/guidance/architecture-diagrams/cloud-native-fast-turnaround-media-workflows-on-aws.pdf)  Step 1 + +In the TAMS data structure, the parent source is equal to the actual content that a user interacts with. This parent source could be an editorial version of the content or a clip. + +Step 2 + +The secondary level source within the data structure allows for the aggregation of the various media types, such as video, audio, or data, into a cohesive collection. + +Step 3 + +The "flow" represents the technical manifestation of the content. This construct contains all the technical metadata necessary to describe the underlying media segments, such as bitrate, resolution, and frame rate. + +Step 4 + +Multiple flows can exist for a single piece of content, enabling the representation of different formats, such as HD and proxy, to coexist. + +Step 5 + +Flow types include video, audio, and data, allowing the different content types to be referenced in the store. + +Step 6 + +Segments are held on object storage and referenced in the TAMS API. The only interaction between the store and the segments occurs during deletion management. + +Step 7 + +The segments are linked to a flow and exist within the context of that flow's virtual timeline. A time range format, expressed as Epoch time plus nanoseconds, is used to represent the position of each segment along the timeline. + +Notes + +A segment can be referenced in one or more flows, allowing the reuse of segments between content without duplication at the storage layer. + +The TAMS maintains only the metadata required for the storage and referencing of the media content. The rich metadata should be managed within separate systems, such as the Media Asset Management system. + +AWS open source TAMS API + +This architecture diagram shows the components and data flows within the AWS open source implementation of the TAMS API. + +[ Download the architecture diagram. ](https://d1.awsstatic.com/solutions/guidance/architecture-diagrams/cloud-native-fast-turnaround-media-workflows-on-aws.pdf)  Step 1 + +Amazon Cognito provides user and system-to-system authentication. + +Step 2 + +The API is presented through Amazon API Gateway, including the validation of requests using the OpenAPI specification. + +Step 3 + +AWS Lambda functions process the API requests. Separate functions exist for the services, sources, flows, segments, and delete request endpoints. + +Step 4 + +Source and flow metadata is stored in an Amazon Neptune graph database. + +Step 5 + +Segment metadata is stored in Amazon DynamoDB for speed of retrieval. + +Step 6 + +Delete requests are forwarded to Amazon Simple Queue Service (Amazon SQS) for asynchronous deletion. + +Step 7 + +A Lambda function is responsible for processing delete operations by forwarding the requests to a secondary Amazon SQS queue, which then handles the deletion of the corresponding Amazon Simple Storage Service (Amazon S3) objects. + +Step 8 + +After the required wait period, a Lambda function evaluates delete requests and removes only unused objects from Amazon S3. + +Step 9 + +Events from core API functions are sent to Amazon EventBridge for subsequent reuse by other systems. + +Step 10 + +An optional Lambda function can process webhook requests to external systems according to the specification. + +AWS open source TAMS tools + +This architecture diagram demonstrates how the multiple components of the AWS TAMS Tools repository can be used alongside the core AWS open source TAMS implementation. + +[ Download the architecture diagram. ](https://d1.awsstatic.com/solutions/guidance/architecture-diagrams/cloud-native-fast-turnaround-media-workflows-on-aws.pdf)  Step 1 + +The TAMS Store capability is provided by the AWS open source implementation. + +Step 2 + +A React-based user interface application, deployed through AWS Amplify, enables users to navigate the store, view video content through the HLS endpoint, and control the live and file-based ingestion processes. + +Step 3 + +Live video ingestion is facilitated using AWS Elemental MediaLive, which creates segments on Amazon S3 that are subsequently uploaded to the TAMS. + +Step 4 + +File-based import is enabled using AWS Elemental MediaConvert, orchestrated by AWS Step Functions, to chunk up the media and upload into the TAMS. + +Step 5 + +An HLS endpoint is provided to convert the TAMS native API calls into a set of HLS manifests to allow content to be played back within a web-based HLS player. + +Step 6 + +The media processing workflow uses event notifications from the TAMS to trigger additional post-processing of the ingested content. This includes the extraction of images and the creation of proxy versions using Lambda, as well as the export of concatenated files for integration with other systems. + +## Deploy with confidence + +Everything you need to launch this Guidance in your account is right here. + +### We'll walk you through it + +Dive deep into the implementation guide for additional customization options and service configurations to tailor to your specific needs. + +[ Open guide ](https://aws-solutions-library-samples.github.io/media-entertainment/cloud-native-fast-turnaround-media-workflows-on-aws/index.html) + +### Let's make it happen + +Ready to deploy? Review the sample code on GitHub for detailed deployment instructions to deploy as-is or customize to fit your needs. + +[ Go to sample code ](https://github.com/aws-solutions-library-samples/guidance-for-cloud-native-fast-turnaround-media-workflows-on-aws) + +## Well-Architected Pillars + +Operational Excellence + +The AWS open source implementation of the TAMS API uses [AWS X-Ray ](https://aws.amazon.com/xray/) to trace requests through the serverless infrastructure, including **API Gateway** , **Lambda** , and **DynamoDB**. The **X-Ray** service aids developers and support teams in tracking and analyzing requests as they flow through the various components of the AWS open-source implementation of the TAMS API. + +In addition, all logs and metrics are collected within [Amazon CloudWatch ](https://aws.amazon.com/cloudwatch/) to facilitate monitoring and analysis. The metrics collected within CloudWatch support the creation of dashboards and the configuration of alarms. + +[Read the Operational Excellence whitepaper](https://docs.aws.amazon.com/wellarchitected/latest/operational-excellence-pillar/welcome.html) + +Security