Newsletter
Deep AWS + AI engineering
in your inbox
This is the newsletter for engineers who want the technical detail — not the hype. Each issue covers a real problem from a production AWS or AI deployment: the CDK pattern that survived a real workload, the Bedrock AgentCore gotcha that cost an afternoon, the cost decision that shows up on the bill.
- ✓ Infrequent — only when there's something worth your time
- ✓ Technical and specific — Bedrock, CDK, AgentCore, IAM, real code
- ✓ Written by me, not generated — the same voice as the blog
- ✓ No sponsors, no affiliate links, no weekly digests
Newsletter
Deep AWS + AI engineering in your inbox
Infrequent and high-signal — the kind of post that documents an IAM gotcha, a real CDK pattern, or a production Bedrock deployment decision. No weekly summaries. No AI-generated content. Just the stuff worth your attention.
No spam. Unsubscribe any time by replying.
Recent posts — a sample of what lands in the newsletter
Field Notes: Turning prompt caching on for a production Bedrock workload
Strands' BedrockModel ships with prompt caching off. Two kwargs turn it on, one per-model gotcha catches you, and a 10-turn driver measures 99.9% / 99.8% hit ratios on Nova Pro and Sonnet 4.6 against an 8,156-token production system prefix. The per-call usage block proves it in seconds, not waiting on CloudWatch.
Field Notes: Three things I learned diagnosing a production Bedrock workload
Three findings from a real customer engagement on AWS Bedrock — what a load test was actually doing, why p95 latency was 45 seconds, and the prompt-caching default that costs every team money. Plus the three CloudWatch metrics that catch all three.
What a Year 10 study system taught me about production AI failure modes
A personal Bedrock-adjacent build that went through three iterations and an architecture pivot. Five lessons that map directly to production AWS AI work.
Part 2: The MCP Server — Turning ADRs and Incidents into a Queryable Org-Knowledge Surface
The agent doesn't read your wiki. It calls four tools that pull frontmatter-filtered chunks out of a Bedrock Knowledge Base. Here's the contract, the code, and the small decisions that make the difference between an agent that reads your docs and one that knows your org.
Part 3: Wiring It Into AWS DevOps Agent — AgentSpace, register-service, and the IAM Trust Policy That Ate My Afternoon
The MCP server is done. Now we plug it into AWS DevOps Agent: three CDK stacks, the AgentSpace + register-service flow, the composite-principal trust policy that you will get wrong on the first try, and a real-world OIDC gotcha that broke my own blog deploy for a month.