Amazon Lex bot

Managed conversational bot with intents, slots and text or voice runtime APIs.

Provider
aws
Category
Compute
Properties · 5 set by this component
propertytypevaluesrequiredkind defaultthis component
authenumapi-key | oauth | iam | noneno—▸ iam
concurrentTextConversations · component propertyinteger—no50inherited
concurrentVoiceConversations · component propertyinteger—no125inherited
contentFilteringboolean—no—inherited
conversationLogs · component propertyboolean—nofalseinherited
customerManagedKeysboolean—no—▸ false
dataResidency · advancedenumus | eu | asia | globalno—inherited
dataRetentionDaysinteger—no—inherited
keyStoreboolean—nofalseinherited
lambdaFulfilment · component propertyboolean—nofalseinherited
managedboolean—nofalse▸ true
maxConversationMinutes · component propertyinteger—no15inherited
maxInputTextCharacters · component propertyinteger—no1024inherited
modalityenumtext | vision | speech | multimodal | structured | image | video | audio | embedding | rerankno—▸ multimodal
publicEndpointboolean—no—▸ true
quotaUnitsPerMinuteinteger—no—inherited
rateLimitRpm · advancedinteger—no—inherited
rateLimitTpm · advancedinteger—no—inherited
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: "lex", component: "aws-lex" }
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 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-serviceAmazon Translateaws-translateawsai-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 Lex V2 bot: managed conversational interface with intents, slots and Lambda fulfilment, reachable over text and voice runtime APIs.
# "Quotas" (Lex V2) gives the runtime defaults: 1,024 characters of input text, 55 seconds of speech per utterance, 50 concurrent text-mode and 125 concurrent voice-mode conversations per alias, a 15-minute maximum conversation and a 30-second Lambda timeout; "Logging conversations with conversation logs" states logs are configured per alias and are off until enabled.
schemaVersion: "1"
type: "component"
id: "aws-lex"
kind: "ai-service"
provider: "aws"
docs: "https://docs.aws.amazon.com/lexv2/latest/dg/quotas.html"
defaults:
  auth: "iam"
  managed: true
  modality: "multimodal"
  publicEndpoint: true
  customerManagedKeys: false
properties:
  concurrentTextConversations:
    type: "integer"
    default: 50
  concurrentVoiceConversations:
    type: "integer"
    default: 125
  maxInputTextCharacters:
    type: "integer"
    default: 1024
  maxConversationMinutes:
    type: "integer"
    default: 15
  conversationLogs:
    type: "boolean"
    default: false
  lambdaFulfilment:
    type: "boolean"
    default: false

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