AWS Well-Architected design considerations

We designed this solution with best practices from the AWS Well-Architected Framework, which helps customers design and operate reliable, secure, efficient, and cost-effective workloads in the cloud.

This section describes how the design principles and best practices of the Well-Architected Framework were applied when building this solution.

Operational excellence

This section describes how we architected this solution using the principles and best practices of the operational excellence pillar.

The Content Localization on AWS solution pushes metrics to Amazon CloudWatch at various stages to provide observability into the infrastructure, Lambda functions, AI services, Amazon Simple Storage Service (Amazon S3) buckets, and the rest of the solution components.

Security

This section describes how we architected this solution using the principles and best practices of the security pillar.

AWS highly recommends that customers encrypt sensitive data in transit and at rest. This solution automatically encrypts media files and metadata at rest with Amazon S3 Server-Side Encryption (SSE). The Media Insights on AWS solution's Amazon Simple Notification Service (Amazon SNS) topics and Amazon DynamoDB tables are also encrypted at rest using SSE.

This solution deploys a static website hosted in an Amazon S3 bucket. To help reduce latency and improve security, this solution includes an Amazon CloudFront distribution with an origin access identity, which is a CloudFront user that provides public access to the solution’s website bucket contents.

Reliability

This section describes how we architected this solution using the principles and best practices of the reliability pillar.

Content Localization 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

This section describes how we architected this solution using the principles and best practices of the performance efficiency pillar.

Content Localization on AWS uses serverless architecture and along with Media Insights on AWS, can be launched in any AWS Region that supports the AWS services used in the solution such as: AWS Lambda, Amazon API Gateway, Amazon S3, Amazon Rekognition, Amazon Translate, Amazon Transcribe, Amazon Comprehend, Amazon Polly, and AWS Elemental MediaConvert.

This solution is automatically tested and reviewed by solutions architects and subject matter experts for areas to experiment and improve.

Cost optimization

This section describes how we architected this solution using the principles and best practices of the cost optimization pillar.

Content Localization on AWS uses serverless architecture; therefore, customers only get charged for what they use.

The solution is a modular framework that allows users to configure and tailor their own media workflows and use only the AWS services that they need.

Sustainability

This section describes how we architected this solution using the principles and best practices of the sustainability pillar.

Content Localization on AWS uses managed and serverless services to minimize the environmental impact of the backend services. A critical component for sustainability provided by the solution is maximizing the usage of the AWS AI services. The serverless design of this solution (using Lambda, API Gateway, Amazon S3, and DynamoDB) are aimed at reducing carbon footprint compared to the footprint of continually operating on-premises servers.