<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Polly - Tag - AWS Sensei</title><link>https://aws-sensei.cloud/tags/polly/</link><description>Polly - Tag - AWS Sensei</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 30 Apr 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://aws-sensei.cloud/tags/polly/" rel="self" type="application/rss+xml"/><item><title>Voiced by Amazon Polly — Adding TTS to a Static Blog</title><link>https://aws-sensei.cloud/posts/2026-04-30-polly-tts/</link><pubDate>Thu, 30 Apr 2026 00:00:00 +0200</pubDate><author>Marcel</author><guid>https://aws-sensei.cloud/posts/2026-04-30-polly-tts/</guid><description><![CDATA[🔊 Voiced by Amazon Polly
You&rsquo;ve probably noticed the audio player at the top of this post. That&rsquo;s Amazon Polly — AWS&rsquo;s neural Text-to-Speech service. Here&rsquo;s how it works and why I built it the way I did.
The Goal Every blog post should have a &ldquo;listen&rdquo; option. Audio is generated automatically when a post is published or updated — no manual steps, no third-party service.
Architecture Git Push → Frontend Pipeline (Hugo build + S3 sync) → Markdown files synced to S3 (_content/posts/) → S3 Event triggers Lambda → Lambda reads HTML from S3 → Polly synthesizes speech (SSML) → MP3 saved to S3 (audio/{slug}.]]></description></item></channel></rss>