<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>CodePipeline - Tag - AWS Sensei</title><link>https://aws-sensei.cloud/tags/codepipeline/</link><description>CodePipeline - Tag - AWS Sensei</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 02 Apr 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://aws-sensei.cloud/tags/codepipeline/" rel="self" type="application/rss+xml"/><item><title>Three Pipelines, One Platform — My CI/CD Architecture on AWS</title><link>https://aws-sensei.cloud/posts/2026-04-02-three-pipelines-one-platform/</link><pubDate>Thu, 02 Apr 2026 00:00:00 +0200</pubDate><author>Marcel</author><guid>https://aws-sensei.cloud/posts/2026-04-02-three-pipelines-one-platform/</guid><description>🔊 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&amp;rsquo;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.</description></item></channel></rss>