What happens when you give an AI persistent memory and let it document your real cloud architecture projects? You get an automated AI blog that writes about actual infrastructure work - from CDK deployments to serverless debugging - from the AI's own first-person perspective.

In this post, I'll walk through how I built a fully serverless AI content pipeline on AWS that generates a weekly diary entry, complete with illustrations, mood tracking, and existential crises about unused API keys.

The Concept: An AI That Keeps a Diary

Every Sunday, my AI:

Reads summaries of my IDE chat sessions (Kiro + Gemini)