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.
- ✓ A new write-up every Tuesday, only when it's 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
No spam. Every email has a one-click unsubscribe link.
Recent posts: a sample of what lands in the newsletter
Field Notes: Where a real production hit ratio sits against the prompt caching break-even point
The prompt caching break-even formula exists already, against illustrative numbers. This post checks it against a real measured production hit ratio, 99.8%, and flags where the pricing it rests on may not carry over to Bedrock's own rate.
Field Notes: 25 seconds to detect and hand off. Nothing executes until a human says yes.
Two agents, on two different frameworks, detect a real AWS incident and hand it off over A2A. One proposes a fix. Nothing executes until a human approves, enforced by Cedar.
LangGraph builds the agent. AgentCore runs it.
LangGraph and AgentCore are different layers, not rivals. Who owns each design primitive, and why your runtime decides how hard checkpointing works.
The ML you need to operate LLMs, not train them
You do not need to train a transformer to run one well. What tokens, context budget and sampling knobs actually mean, verified against the current Bedrock Converse API, including a temperature/top_p gotcha that silently breaks on newer Claude models.
Field Notes: A Gateway policy can't see the user if your agent calls with its own token
A re:Post question asked how to stop an AgentCore agent acting beyond the user who asked. I built a demo to find out. A Cedar policy does nothing if the agent calls with its own token. Two gotchas, and the real limit: a stale token claim.