Amazon Translate

awsAI serviceaws-translate

Managed neural machine translation for real-time text and batch document jobs.

Provider
aws
Category
Compute
Properties · 6 set by this component
propertytypevaluesrequiredkind defaultthis component
activeCustomTranslation · component propertyboolean—nofalseinherited
authenumapi-key | oauth | iam | noneno—▸ iam
concurrentBatchJobs · component propertyinteger—no10inherited
contentFilteringboolean—no—▸ false
customTerminology · component propertyboolean—nofalseinherited
customerManagedKeysboolean—no—▸ false
dataResidency · advancedenumus | eu | asia | globalno—inherited
dataRetentionDaysinteger—no—inherited
keyStoreboolean—nofalseinherited
managedboolean—nofalse▸ true
maxInputBytesPerRequest · component propertyinteger—no10000inherited
modalityenumtext | vision | speech | multimodal | structured | image | video | audio | embedding | rerankno—▸ text
publicEndpointboolean—no—▸ true
quotaUnitsPerMinuteinteger—no—inherited
rateLimitRpm · advancedinteger—no—inherited
rateLimitTpm · advancedinteger—no—inherited
translationMode · component propertyenumsynchronous | batchnosynchronousinherited
viaGatewayboolean—nofalseinherited
Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

ai-api-key-unmanaged

This AI vendor is reached with an API key, and nothing in the design holds or rotates that key. It ends up in environment files or code, every caller shares it, and a single leak runs up the vendor bill until someone notices. Put the key in a key-management component, or say it is held there with keyStore.

  • — all of these hold:
  • — the node's `auth` is "api-key"
  • — the node's `keyStore` is false
  • — the node has at least one incoming edge from an app-server, worker or client
  • — this does not hold:
  • — the design contains a node of kind key-management
stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

  • — all of these hold:
  • — the node's `stateless` is false
  • — the node sits inside exactly 1 availability-zone group
  • — this does not hold:
  • — the node sits inside at least one cell group
Use it in a design
nodes:
  - { id: "translate", component: "aws-translate" }
Other AI service products · 125
Content Moderationalibaba-content-moderationalibabacloudai-serviceFraud Detectionalibaba-fraud-detectionalibabacloudai-serviceID Verificationalibaba-id-verificationalibabacloudai-serviceIntelligent Robotalibaba-intelligent-robotalibabacloudai-serviceModel Studioalibaba-model-studioalibabacloudai-serviceSmart Conversation Analysisalibaba-smart-conversation-analysisalibabacloudai-serviceAmazon Bedrockaws-bedrockawsai-serviceAmazon Bedrock AgentCoreaws-bedrock-agentcoreawsai-serviceAmazon Bedrock Data Automationaws-bedrock-data-automationawsai-serviceAmazon Bedrock Guardrailsaws-bedrock-guardrailsawsai-serviceAmazon Comprehendaws-comprehendawsai-serviceAmazon Comprehend Medicalaws-comprehend-medicalawsai-serviceAWS Elemental Inferenceaws-elemental-inferenceawsai-serviceAmazon Forecastaws-forecastawsai-serviceAmazon Fraud Detectoraws-fraud-detectorawsai-serviceAWS HealthScribeaws-healthscribeawsai-serviceAmazon Lex botaws-lexawsai-serviceAmazon Lookout for Equipmentaws-lookout-for-equipmentawsai-serviceAmazon Lookout for Metricsaws-lookout-for-metricsawsai-serviceAmazon Lookout for Visionaws-lookout-for-visionawsai-serviceAmazon Personalizeaws-personalizeawsai-serviceAmazon Pollyaws-pollyawsai-serviceAmazon Q Businessaws-q-businessawsai-serviceAmazon Rekognitionaws-rekognitionawsai-serviceAmazon Textractaws-textractawsai-serviceAmazon Transcribeaws-transcribeawsai-serviceContent Safetyazure-ai-content-safetyazureai-serviceAzure AI Custom Visionazure-ai-custom-visionazureai-serviceAzure AI Faceazure-ai-faceazureai-serviceAzure Languageazure-ai-languageazureai-serviceAzure Speechazure-ai-speechazureai-serviceAzure Translatorazure-ai-translatorazureai-serviceAzure Visionazure-ai-visionazureai-serviceAzure Content Understandingazure-content-understandingazureai-serviceMicrosoft Discoveryazure-discoveryazureai-serviceAzure Document Intelligenceazure-document-intelligenceazureai-serviceFoundry Agent Serviceazure-foundry-agent-serviceazureai-serviceFoundry Modelsazure-foundry-modelsazureai-serviceAzure AI Immersive Readerazure-immersive-readerazureai-serviceAzure OpenAI in Foundry Modelsazure-openaiazureai-service
and 85 more → AI service page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Amazon Translate: managed neural machine translation, synchronously per request or as an asynchronous batch job over documents in Amazon S3.
# "Guidelines and quotas" gives the defaults: 10,000 bytes of input text per synchronous TranslateText call, 100,000 bytes per document, 10 concurrent batch translation jobs with 1,000 queued, 100 custom terminology files per account, and a statement that Amazon Translate may store customer data to improve its models unless deletion is requested; profanity masking and formality are opt-in request settings.
schemaVersion: "1"
type: "component"
id: "aws-translate"
kind: "ai-service"
provider: "aws"
docs: "https://docs.aws.amazon.com/translate/latest/dg/what-is-limits.html"
defaults:
  auth: "iam"
  managed: true
  modality: "text"
  publicEndpoint: true
  customerManagedKeys: false
  contentFiltering: false
properties:
  translationMode:
    type: "enum"
    values: ["synchronous", "batch"]
    default: "synchronous"
  maxInputBytesPerRequest:
    type: "integer"
    default: 10000
  concurrentBatchJobs:
    type: "integer"
    default: 10
  customTerminology:
    type: "boolean"
    default: false
  activeCustomTranslation:
    type: "boolean"
    default: false

The same page as markdown, for an agent: /catalogue/components/aws-translate.md