<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Brian Feeny</title><description>Notes on AI, machine learning, data, and whatever else I can&apos;t stop thinking about.</description><link>https://brianfeeny.com/</link><item><title>Token Economics on Amazon Bedrock: Prompt Caching and Tool Catalogs</title><link>https://brianfeeny.com/posts/token-economics-on-amazon-bedrock/</link><guid isPermaLink="true">https://brianfeeny.com/posts/token-economics-on-amazon-bedrock/</guid><description>Advice on LLM cost is usually advice on token counts. On Bedrock that is the wrong objective: a request spends in two currencies that disagree, and in an agentic loop what governs cost is whether the prefix is still cacheable. Two AWS recommendations applied together cost 18-20% more than either alone, the crossover tracks catalog tokens rather than tool count, and prompt caching makes output more deterministic, not less.</description><pubDate>Sun, 27 Sep 2026 00:56:49 GMT</pubDate></item><item><title>Tenancy, Rate Limits and PII Masking on AgentCore Gateway</title><link>https://brianfeeny.com/posts/tenancy-rate-limits-and-pii-on-agentcore-gateway/</link><guid isPermaLink="true">https://brianfeeny.com/posts/tenancy-rate-limits-and-pii-on-agentcore-gateway/</guid><description>Three articles of per-tenant controls — budgets, caches, rate limits — all keyed on a header any caller could set. Replacing it with a validated token costs 0.53 ms. Along the way: why a request-rate limit cannot protect a token quota, why a cache hit was silently stealing quota it never spent, and why the PII screen that costs 50x less is the one you must not use.</description><pubDate>Wed, 23 Sep 2026 19:53:59 GMT</pubDate></item><item><title>Semantic Caching for LLMs on AWS</title><link>https://brianfeeny.com/posts/semantic-caching-for-llms-on-aws/</link><guid isPermaLink="true">https://brianfeeny.com/posts/semantic-caching-for-llms-on-aws/</guid><description>An exact LLM cache almost never hits, and the obvious fix — serve the answer to the nearest stored prompt — is worse than no cache: the near-misses that change the answer sit closer in embedding space than the paraphrases that don&apos;t. A verification stage fixes the ranking and leaves a 5% floor of confidently wrong answers that you cannot measure in production. Built on DynamoDB vector search, measured three ways, and mostly an argument for not running it.</description><pubDate>Wed, 23 Sep 2026 15:37:41 GMT</pubDate></item><item><title>Sizing Aurora Connections for Autoscaled Services on AWS</title><link>https://brianfeeny.com/posts/sizing-aurora-connections-for-autoscaled-services/</link><guid isPermaLink="true">https://brianfeeny.com/posts/sizing-aurora-connections-for-autoscaled-services/</guid><description>A service that scales on request rate scales its connection count with it, and Aurora&apos;s ceiling is fixed by instance memory. The arithmetic, the formula behind max_connections, why lowering the pool limit is a trap, and what RDS Proxy does and does not fix.</description><pubDate>Wed, 23 Sep 2026 14:09:29 GMT</pubDate></item><item><title>Customizing inference on AgentCore Gateway: a plugin pipeline for routing, budgets and guardrails</title><link>https://brianfeeny.com/posts/agentcore-gateway-plugin-pipeline/</link><guid isPermaLink="true">https://brianfeeny.com/posts/agentcore-gateway-plugin-pipeline/</guid><description>Every model call through Amazon Bedrock AgentCore Gateway passes one place where you can check a budget, clamp tokens, run a guardrail, pick the model, cache the answer and meter the cost. A reference architecture that makes each of those a swappable plugin, deployed and measured, plus seven things about interceptors the documentation does not tell you.</description><pubDate>Wed, 23 Sep 2026 02:25:00 GMT</pubDate></item><item><title>Scaling LiteLLM on AWS</title><link>https://brianfeeny.com/posts/scaling-litellm-on-aws/</link><guid isPermaLink="true">https://brianfeeny.com/posts/scaling-litellm-on-aws/</guid><description>A reference architecture and operating guide for running LiteLLM as an enterprise LLM gateway on AWS with Amazon Bedrock, plus the FinOps, governance and security work that scales with it, and a managed alternative on AgentCore Gateway.</description><pubDate>Tue, 22 Sep 2026 04:00:00 GMT</pubDate></item><item><title>Replicating RouteLLM on Amazon Bedrock</title><link>https://brianfeeny.com/posts/replicating-routellm-on-amazon-bedrock/</link><guid isPermaLink="true">https://brianfeeny.com/posts/replicating-routellm-on-amazon-bedrock/</guid><description>Prompt-only LLM routers post strong in-distribution scores that are almost entirely recognition of which group a prompt came from. A reproduction of RouteLLM on Amazon Bedrock and AgentCore Gateway, a diagnostic suite that exposes it, and a zero-cost deferral rule that works where prompt-only routing does not.</description><pubDate>Mon, 21 Sep 2026 23:30:00 GMT</pubDate></item><item><title>A telnet daemon for MorphOS, or: how to attach a shell to a socket with no pty</title><link>https://brianfeeny.com/posts/telnetd-for-morphos/</link><guid isPermaLink="true">https://brianfeeny.com/posts/telnetd-for-morphos/</guid><description>MorphOS never shipped a telnet daemon. Building one meant confronting the fact that the Amiga lineage has no pseudo-terminals — and that the answer is stranger and more interesting than a port. A short tour of the design, the war stories, and why it is really groundwork for an sshd.</description><pubDate>Sat, 19 Sep 2026 22:00:00 GMT</pubDate></item></channel></rss>