These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.
Step 1
Everything you need to launch this Guidance in your account is right here.
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.
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 pushes metrics to CloudWatch at various stages to provide observability into the infrastructure, such as AWS Lambda functions, AI services, and Amazon S3 buckets.
We highly recommend that you encrypt sensitive data in transit and at rest. This Guidance automatically encrypts media files and metadata at rest with Amazon S3 server-side encryption (SSE-S3). The Guidance's Amazon SNS topics and DynamoDB tables are also encrypted at rest using SSE-S3. Furthermore, documents indexed to the OpenSearch Service cluster are encrypted at rest, and node-to-node communication within the cluster is also encrypted.
This Guidance deploys a static website hosted in an Amazon S3 bucket. To help reduce latency and improve security, this Guidance includes a CloudFront distribution with an origin access identity, which is a special CloudFront user that helps restrict access to website bucket contents. For more information, refer to Restricting access to an Amazon S3 origin.
Guidance for Media2Cloud on AWS uses AWS serverless services wherever possible (for example, Lambda, API Gateway, Amazon S3, and DynamoDB) to ensure high availability and quick recovery from service failure.
You can create workflows with the pre-built AWS CloudFormation template. Because this Guidance is an open source project published on GitHub, you can customize this and build from the source code. The README provides a step-by-step guide to build and customize this Guidance, along with a mini-tutorial, and an in-depth explanation of each component and the overall design.
Because this Guidance uses a serverless and event-driven architecture, you are only charged for what you use. Its design allows you to configure and tailor your own media workflows, and use only the AWS services that you need. Furthermore, it allows your assets to be stored cost effectively using Amazon S3 with Lifecycle policies to store and archive ingested contents, proxies, and metadata.
A critical component for sustainability is maximizing the usage of the AWS AI services so you minimize the environmental impact of the backend services. And, the serverless design of this Guidance is designed to reduce your carbon footprint compared to the footprint of continually operating on-premises servers.
This blog post announces AWS Media Intelligence (AWS MI) solutions and covers four important use cases: content search and discovery, captioning and localization, compliance and brand safety, and content monetization.
This blog post describes how ESSENCE Magazine, with the help of Starchive.io and AWS, celebrated their landmark anniversary with a major virtual event to mark the occasion.
Learn how AWS created a long-term remedy to F1’s media asset management needs using the Media2Cloud (M2C) reference implementation by AWS Solutions.
Learn how UKTV uses this AWS Solution to achieve their goals of increased observability, better resilience, and greater possibilities for more advanced media functionality.