Experience Cloud
Flow
AI Services
Translate your OTT metadata into any language with AWS Translate
Enveu uses AWS Translate to localize content metadata — titles, descriptions, tags, genres — into 75+ languages, both inside Experience Cloud's CMS (Metadata Translator) and as an automated Flow step.
Experience Cloud
AWS Translate for OTT platforms
About AWS Translate in Enveu
AWS Translate is Amazon’s neural machine-translation service. Enveu uses it two ways:
- Metadata Translator (Experience Cloud) — automatically translates content metadata (titles, descriptions, synopses, tags) into multiple languages directly in the Enveu CMS.
- AWS Translate plugin (Flow) — does the same as an automated step in media workflows, on ingest or metadata update.
Only text metadata is sent for translation — your video and audio files are never processed.
How AWS Translate + Enveu works
How Enveu's Metadata Translator uses AWS Translate to localize metadata at scale.
1
Content is created or updated in Enveu CMS
You add or update metadata — title, description, synopsis, tags — for Live or VoD content.
2
Enveu sends metadata to AWS Translate
Only the metadata fields are sent securely — never your video or audio files.
3
AWS Translate processes the translation
Metadata is converted into the selected target languages with accuracy and consistency.
4
Translated metadata is stored back in Enveu CMS
Each language is saved as a separate metadata variant and shown per the viewer's device or app language.
Why AWS Translate customers add Enveu
- Automatic translation of content metadata into multiple languages using AWS Translate — no manual localization.
- Faster global OTT launches by enabling multilingual metadata at scale across large libraries.
- Consistent, accurate metadata across web, mobile, and TV via centralized language management in Enveu.
- Secure, enterprise-grade workflow — only metadata is processed; media files stay untouched.
- Runs asynchronously — no impact on content publishing or playback performance.
Frequently asked questions
What is AWS Translate + Enveu?
Enveu uses AWS Translate to localize content metadata — titles, descriptions, tags, genres — into 75+ languages, both inside Experience Cloud's CMS (Metadata Translator) and as an automated Flow step.
What does the AWS Translate connector do in Enveu?
It automatically translates content metadata — titles, descriptions, tags, and other attributes — into multiple languages, helping you localize your OTT platform efficiently.
What content is translated?
Only metadata (text fields like titles, descriptions, and tags). Video and audio files are never sent or processed.
Which languages are supported?
AWS Translate supports 75+ languages. Source and target languages are configurable within Enveu.
Is AWS Translate required for metadata translation?
Enveu currently uses AWS Translate as the translation service. The connector is designed to support additional providers in the future if required.
How is translated metadata stored in Enveu?
Each translated version is stored as a separate language variant of the metadata in the CMS, so apps display the correct language automatically.
How do Enveu apps decide which language to display?
Based on device language settings, app language selection, and regional or market-specific configuration.
Flow
AWS Translate as a Flow plugin
Best forTranslating titles, descriptions, tags, and genre labels into multiple languages automatically when new content is ingested or metadata is updated.
Translate content metadata into any language using AWS Translate. Supports 75+ languages. Use in Multilingual Metadata Translation and Live to VoD workflows to automatically localise titles, descriptions, tags, and genre labels.
Inputs & outputs
Inputs
Source textMetadata field content to translate — title, description, tags
Source languageLanguage code of the input text e.g. en, hi, ar
Target languagesList of language codes to translate into
Outputs
Translated text per languageMetadata field content in each target language
Language confidence scoreTranslation quality score per output
Triggers & actions
Triggers
Metadata readyFires when upstream step outputs metadata fields ready for translation
Asset ingestedNew asset record created in CMS triggers translation of all metadata fields
Actions
Translate textTranslate a string into a target language
Translate batchTranslate multiple fields in a single API call
Detect languageIdentify the language of an input string
Apply glossaryTranslate using a custom terminology glossary to protect brand terms
Example workflow
Metadata extractedSource asset
→Detect languageAWS Translate
→Translate fieldsAWS Translate
→Update CMSAll languages
→NotifySlack
Used in these workflows
Works well with
Frequently asked questions
Does AWS Translate support all languages?
AWS Translate supports 75+ languages. Flow passes your configured source and target language codes directly to AWS Translate. Full language support details are available in the AWS documentation.
Can Flow protect brand names from being translated incorrectly?
Yes. Flow supports AWS Translate custom terminology glossaries. You define a list of protected terms and AWS Translate will never translate them - preserving brand names, product names, and technical terms across all target languages.
Does Flow detect the source language automatically?
Yes. The AWS Translate plugin includes a language detection action that identifies the language of an input string. You can use this as a workflow step before translation to route content correctly.
Can Flow translate multiple metadata fields in one API call?
Yes. Flow supports batch translation of multiple fields in a single AWS Translate call, reducing latency and API costs compared to making one call per field.
Launch with Enveu + AWS Translate
See how Enveu works with AWS Translate to power and automate OTT at scale.