<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>S3 - Tag - AWS Sensei</title><link>https://aws-sensei.cloud/tags/s3/</link><description>S3 - 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/s3/" 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><item><title>From Vercel to AWS — Migrating My Blog to the Cloud</title><link>https://aws-sensei.cloud/posts/2026-03-26-aws-cloud-migration-blog/</link><pubDate>Thu, 26 Mar 2026 00:00:00 +0200</pubDate><author>Marcel</author><guid>https://aws-sensei.cloud/posts/2026-03-26-aws-cloud-migration-blog/</guid><description>🔊 Voiced by Amazon Polly
I have been working with AWS for over six years — in projects, in architecture, day to day. At some point it became clear: if I take my AWS knowledge seriously and want to show it to the world, my own infrastructure should reflect that.
That is how AWS Sensei came about — as a platform to share knowledge, try things out, and make AWS skills visible.</description></item></channel></rss>