Guidance for Media2Cloud on AWS
Overview
How it works
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.
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.
Operational Excellence
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.
Security
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.
Reliability
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.
Performance Efficiency
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.
Cost Optimization
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.
Sustainability
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.
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
Disclaimer
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages