https://aws-sensei.cloud/tags/aws/AWS - 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-05-08-aws-mcp-server-claude-code/Fri, 08 May 2026 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2026-05-08-aws-mcp-server-claude-code/🔊 Voiced by Amazon Polly AWS recently announced the general availability of the AWS MCP Server. It gives AI coding assistants like Claude Code direct access to over 15,000 AWS API operations, live documentation, and sandboxed script execution — all via the Model Context Protocol. I set it up for my own workflow and ran into a few stumbling blocks. Here’s the short version of what actually works. What is the AWS MCP Server?https://aws-sensei.cloud/posts/2026-04-30-polly-tts/Thu, 30 Apr 2026 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2026-04-30-polly-tts/https://aws-sensei.cloud/posts/2026-04-27-contact-form/Mon, 27 Apr 2026 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2026-04-27-contact-form/🔊 Voiced by Amazon Polly Static blogs have no backend — but sometimes you still need a way for visitors to get in touch. The usual solution is a third-party service like Formspree or Netlify Forms. My solution: build everything on AWS myself. The Architecture Browser → API Gateway → Lambda → SES → Email Three AWS services, all serverless. The visitor fills out the form, Lambda validates the input and calls SES — the email lands in my inbox.https://aws-sensei.cloud/posts/2026-04-20-realtime-chat/Mon, 20 Apr 2026 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2026-04-20-realtime-chat/🔊 Voiced by Amazon Polly Static blogs have a problem: no interaction. Comment systems like Disqus exist, but they load third-party JavaScript, track visitors, and never quite fit the blog’s look. My solution: build a custom real-time comment section directly on AWS. The result is the widget at the bottom of this post — you can try it out right now. The Architecture Browser ←→ WebSocket API Gateway ←→ Lambda ←→ DynamoDB The key difference from a regular REST widget: WebSocket.https://aws-sensei.cloud/posts/2026-04-14-cost-dashboard/Tue, 14 Apr 2026 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2026-04-14-cost-dashboard/🔊 Voiced by Amazon Polly One question I ask myself with every AWS project: what does this actually cost? For this blog I built the answer directly in — at the bottom of this post you can see live what aws-sensei.cloud has cost in the current month, broken down by AWS service. The Idea The goal was not a static screenshot dashboard, but real live data straight from AWS — updated daily, embedded directly in the blog.https://aws-sensei.cloud/posts/2026-04-10-sentiment-widget/Fri, 10 Apr 2026 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2026-04-10-sentiment-widget/🔊 Voiced by Amazon Polly The APIs pipeline from the previous post was ready — waiting for its first feature. The result is the sentiment analysis widget you can try out at the bottom of this post: type a sentence, AWS Comprehend analyzes it in real time and tells you whether it reads as positive, negative, neutral, or mixed. The Architecture Browser → API Gateway → Lambda → AWS Comprehend Three AWS services, all serverless.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.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.