AWS Well-Architected design considerations

This solution uses the 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 benefit this solution.

Operational excellence

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

This solution pushes metrics to CloudWatch at various stages to provide observability into the infrastructure, Lambda functions, MediaConvert, 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.

This solution uses AWS Identity and Access Management (IAM) roles to allow customers to assign granular access policies and permissions to services and users in the AWS Cloud.

Reliability

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

This solution uses AWS serverless services wherever possible (for example, Lambda and Amazon S3) 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.

This solution uses serverless architecture. It can be launched in any AWS Region that supports the AWS services used in the solution, such as Lambda, Amazon S3, and 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.

You can measure the efficiency of the workloads, and the costs associated with delivery, by using Application Manager.

Sustainability

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

This solution uses managed and serverless services to minimize the environmental impact of the backend services. If desired, you can run this solution only during specific events and then delete the stack after the program ends. This approach helps reduce the carbon footprint compared to the footprint of continually operating on-premises servers.