https://aws-sensei.cloud/tags/ci/cd/CI/CD - Tag - AWS SenseiHugo -- gohugo.ioenFri, 22 May 2026 00:00:00 +0200https://aws-sensei.cloud/posts/2026-05-22-smarter-post-triggers/Fri, 22 May 2026 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2026-05-22-smarter-post-triggers/🔊 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’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.https://aws-sensei.cloud/posts/2026-04-02-three-pipelines-one-platform/Thu, 02 Apr 2026 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2026-04-02-three-pipelines-one-platform/🔊 Voiced by Amazon Polly In the first post I described how aws-sensei.cloud is set up — Hugo, S3, CloudFront, a CodeBuild pipeline. That was a good start. But one pipeline for everything doesn’t scale. The problem showed up in practice faster than expected: with a single pipeline, I kept hitting the CodeBuild free tier limit just by writing blog posts — even though I had only changed Markdown. Every commit triggered the full pipeline: Hugo build, infrastructure deploy, everything.