All Services

AI / ML

Amazon Lex

Amazon Lex V2 builds text and voice conversational interfaces from intents, utterances, slots, prompts, contexts, fulfillment, and fallback behavior, using the same broad technology category as Alexa.

Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with Amazon Lex.

Amazon Lex pricing and cost programs

Pricing model: Conversational request usage

On-Demand
Available
Reserved Instances or reserved capacity
Not applicable
Savings Plans
Not applicable
Spot
Not applicable

Billing dimensions: Speech requests · Text requests · Streaming duration · Automated chatbot design

Programs and modes: Request/response interactions · Streaming conversations · Automated Chatbot Designer

Modality and conversational mode determine request or duration charges.

Free Tier: Available — verify current offers

Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.

Official AWS pricing

Official AWS sources reviewed 2026-07-21.

Why implement Amazon Lex?

  • Provides managed natural-language understanding, dialogue state, speech recognition, and speech synthesis integration without operating bot servers.
  • Supports multiple locales, versions, aliases, Lambda fulfillment, session attributes, contexts, and contact-center integration.
  • Can collect conversation logs and metrics to improve utterances, prompts, fallbacks, and task completion over time.

How to implement Amazon Lex

  1. Define user goals, intents, slots, confirmation rules, fallback and escalation paths, privacy boundaries, supported locales, and measurable completion criteria.
  2. Create the bot, locale, utterances, slot types and prompts; connect a least-privilege Lambda fulfillment function with validation, idempotency, timeouts, secret references, and safe error responses.
  3. Build and test normal, ambiguous, adversarial, interruption, and no-match conversations, then publish a version and alias, integrate the channel, and monitor logs, latency, fallbacks, abandonment, and fulfillment outcomes.

Amazon Lex best practices

  • Keep intents distinct, provide varied natural utterances, validate slot values in fulfillment, confirm irreversible actions, and always offer a clear fallback or human handoff.
  • Do not collect secrets or sensitive data unless necessary; redact or disable conversation logs as policy requires, encrypt them, and restrict log and fulfillment access.
  • Use versions and aliases for controlled releases, load-test dependent services, monitor no-match and error patterns, and retrain only after reviewing real conversation evidence.

Amazon Lex use cases and server impact

  • Customer-service self-service bots
  • Voice and chat task automation
  • Contact-center intent capture and routing

Replaces the managed speech, NLU, and dialogue layer, while fulfillment services, business validation, channel integration, escalation, and conversational governance remain customer responsibilities.

Official implementation resources

Commonly paired AWS services