<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>SNS - Tag - AWS Sensei</title><link>https://aws-sensei.cloud/tags/sns/</link><description>SNS - Tag - AWS Sensei</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 22 May 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://aws-sensei.cloud/tags/sns/" rel="self" type="application/rss+xml"/><item><title>Smarter S3 Triggers: Hash Files, SNS Fanout, and No More Redundant Calls</title><link>https://aws-sensei.cloud/posts/2026-05-22-smarter-post-triggers/</link><pubDate>Fri, 22 May 2026 00:00:00 +0200</pubDate><author>Marcel</author><guid>https://aws-sensei.cloud/posts/2026-05-22-smarter-post-triggers/</guid><description>🔊 Voiced by Amazon Polly
The Polly TTS setup worked well, but there was a flaw: every deployment triggered the Polly Lambda for every post, even when nothing had changed. The Lambda&amp;rsquo;s content-hash check caught duplicates after the fact, but the invocations still happened for all posts on every push. At the AWS Summit in Hamburg on May 20th I had some time to think through a cleaner solution.</description></item></channel></rss>