https://aws-sensei.cloud/tags/sam/SAM - Tag - AWS SenseiHugo -- gohugo.ioenMon, 27 Apr 2026 00:00:00 +0200https://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.