Amazon Polly
View on GitHubAmazon Polly
Amazon Polly is a cloud service that converts text into spoken audio using API calls and SDKs. It provides synchronous and asynchronous speech synthesis, supports SSML and customizable pronunciation lexicons, and can produce streaming or file-based audio suitable for applications. Polly typically sits behind application backends or serverless functions to provide programmatic text-to-speech output in an AWS architecture.
🗂 Resource Category
Artificial Intelligence and Machine Learning
🧠 Exam Memory Hook
Think: "Text input + API call + speech output = Amazon Polly"
📖 Ownership
Classification: AWS Managed Service
AWS responsibilities: AWS operates and manages the Amazon Polly service platform, API endpoints, control plane, and the underlying physical infrastructure and managed runtime that perform speech synthesis; AWS is responsible for patching and maintaining the service platform, scaling the service capacity, and securing the service infrastructure. AWS provides service-level logging and metrics endpoints that integrate with AWS observability services. AWS does not operate or manage customer data stored outside the Polly service (for example objects in Amazon S3) unless those services are separately configured.
Customer responsibilities: The customer configures text content, SSML markup, lexicons, and API usage patterns; configures access control using IAM policies and resource policies; secures credentials and application code that call Polly; configures storage, distribution, and lifecycle for generated audio (for example Amazon S3 and Amazon CloudFront); and monitors usage, cost, and application-level quality. The customer is responsible for ensuring input content complies with regulatory and privacy requirements and for implementing any necessary encryption, access logging, and retention policies for generated audio assets.
Patching responsibilities: AWS patches the physical infrastructure and the managed service runtime that executes speech synthesis; AWS maintains and patches the service control plane and underlying service platform. Because Amazon Polly is provided as a managed/serverless API service, guest operating system and hypervisor patching for the service infrastructure are handled by AWS. Customers are responsible for patching their own applications, libraries, packaged dependencies, and any guest operating systems of compute they control (for example EC2 instances or self-managed containers) that call Polly or process audio outputs.
🏗 Typical Architecture
💡 Top 5 Features
- Real-time and asynchronous text-to-speech synthesis via API operations for immediate streaming or background audio generation.
- Support for SSML to control pronunciation, speaking rate, pauses, and emphasis within synthesized speech.
- Neural and standard voice models across multiple languages and selectable voice personas.
- Pronunciation lexicons and speech marks that provide timing and metadata for lip-sync or subtitle alignment.
- SDKs and REST APIs that integrate with serverless functions, application servers, and media pipelines.
✅ Top 5 Use Cases
- Generate dynamic IVR prompts and telephone prompts where text changes per caller and storing pre-recorded audio is impractical.
- Produce narration for e-learning content by converting lesson text to audio and storing files in Amazon S3 for distribution.
- Create accessible audio versions of website content and articles on-demand for visually impaired users via application APIs.
- Generate push notification audio or spoken alerts for operations dashboards where automated content must be voiced programmatically.
- Batch-produce voice assets such as audiobooks or podcast drafts using asynchronous synthesize tasks and store results in object storage.
🏗 Architecture Placement
Amazon Polly is a regional API-based text-to-speech service that is invoked by application servers, serverless functions, or client-side SDKs to produce audio. Typical callers include AWS Lambda, EC2, or containerized application backends that send text or SSML to Polly and receive streamed audio or file-based output. Generated audio is commonly stored in Amazon S3 and distributed via Amazon CloudFront or played directly to users through application streaming. Access control is enforced through IAM and application credentials.
🎯 Commonly Used With
- Amazon S3
- AWS Lambda
- Amazon CloudFront
- Amazon API Gateway
- Amazon CloudWatch
🌍 5 Real-World Examples
- A bank uses Polly to generate dynamic IVR voice prompts that read account balances and transaction details for callers, reducing the need for recorded prompts and enabling rapid content updates.
- An e-learning provider converts lesson text to narrated audio files with Polly and stores outputs in S3 for students to stream on-demand, improving content accessibility.
- A news website produces narrated versions of articles by invoking Polly via backend services and delivers the audio through CloudFront to mobile apps.
- A logistics company generates automated spoken delivery updates for drivers and customer notifications where messages are composed programmatically based on delivery status.
- A healthcare portal offers spoken discharge instructions synthesized by Polly for patients who prefer audio guidance, enabling consistent delivery of standardized content.
🎓 AWS Exam Clues
- Choose Amazon Polly when you need programmatic text-to-speech with SSML or lexicon support for dynamic or on-demand audio.
- Polly is appropriate when applications require both synchronous streaming and asynchronous audio file generation workflows.
- Consider IAM permissions and secure credential handling for services calling Polly, and plan storage/encryption for synthesized audio assets.
- Polly is a managed API service, so operational effort focuses on application integration, content quality, and access controls rather than underlying infrastructure.
- Use Polly when voice variety or neural voices are required; evaluate voice model availability and supported languages for the target audience.
📝 Quick Revision
Amazon Polly provides API-driven text-to-speech with SSML, lexicons, streaming and asynchronous file generation; use it for dynamic voiced content delivered by application backends or serverless functions. Important considerations include access control with IAM, where to store and distribute generated audio (for example Amazon S3 and CloudFront), and monitoring usage and content compliance.
🏷 Keywords
Text-to-Speech • SSML • Neural TTS • Lexicons • Speech Marks • SynthesizeSpeech • StartSpeechSynthesisTask • Streaming audio • Asynchronous synthesis • Audio file generation • API SDKs • Voice personas