https://aws-sensei.cloud/tags/iac/IaC - Tag - AWS SenseiHugo -- gohugo.ioenThu, 02 Apr 2026 00:00:00 +0200https://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.https://aws-sensei.cloud/posts/2026-03-26-aws-cloud-migration-blog/Thu, 26 Mar 2026 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2026-03-26-aws-cloud-migration-blog/🔊 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.