Guidance for Automated Language Translations 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
AWS managed services emit their own set of metrics into Amazon CloudWatch, where you can monitor services for errors and set up CloudWatch alarm notifications.
Security
This solution uses Amazon Cognito to authenticate translators prior to providing them with access to the translation management application. For data ingress from the PIM and CMS, this architecture will provide flexible authentication options including API keys, AWS Identity and Access Management (IAM) if the source system supports it, and customer authentication against a different identity provider using Lambda authorizers.
Reliability
This Guidance is based on an event-driven, distributed architecture. It uses a Step Functions workflow that provides built-in retry capabilities. Additionally, it uses EventBridge to support built-in retry capability for up to 24 hours with exponential back-off, a pattern where the wait time is increased exponentially after every retry attempt, and jitter, which adds some amount of randomness to the backoff to spread the retries around in time.
Performance Efficiency
Serverless technologies feature automatic scaling. If there is an influx of changes in the translation content, the architecture will scale accordingly and make changes in near real time.
Cost Optimization
This architecture follows a serverless-first approach. Where possible, serverless services scale based on the number of content changes, which means costs will scale based on service usage.
Sustainability
AWS managed services scale up and down according to business requirements and traffic, making them more sustainable than on-premises architectures that do not offer on-demand scalability. Additionally, serverless components of this architecture automate the process of infrastructure management.
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