This Guidance helps sellers perform content localization and accurate translations so they can adapt their content for a global audience. Amazon Translate allows ecommerce and marketplace retailers to translate millions of product titles, descriptions, and interactions between customers and sellers. In a global economy with customers around the world, localization can improve customer interactions and increase transactions. By automating content translation at scale, this Guidance minimizes the manual work involved with maintaining localized content.

Architecture Diagram

[Architecture diagram description]

Download the architecture diagram PDF 

Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.

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.

  • 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.

    Read the Operational Excellence whitepaper 
  • 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.

    Read the Security whitepaper 
  • 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.

    Read the Reliability whitepaper 
  • 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.

    Read the Performance Efficiency whitepaper 
  • 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. 

    Read the Cost Optimization whitepaper 
  • 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.

    Read the Sustainability whitepaper 

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.

[Content Type]


This [blog post/e-book/Guidance/sample code] demonstrates how [insert short description].


The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.

References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.

Was this page helpful?