Topic
Aws
4 episodes
-
Enterprise RAG Permission Assembly
Daniel Shimoni argues that permissions must be baked into how enterprise context gets assembled for RAG systems, not applied as post-hoc filters. The central claim: assembly is the last moment where refusing to include something prevents the model from ever seeing it. AWS Context and similar platform moves have converged on this architecture, but most enterprise software hasn't caught up—teams still rely on filtering retrieved context after the fact, which leaves temporal gaps (someone leaves the finance team at 9 a.m., the sync runs at 2 a.m., and for seventeen hours they can still access restricted documents) and fails under pressure from security review.
-
Evolution of a Backend for a Streaming Application
Daniele Frasca's talk on evolving Joyn's backend from a fragile single-node Kafka-to-DB setup to a multi-region serverless architecture on AWS, covering hub-and-spoke data consistency, cell-based isolation, and cost optimization for active-active streaming.
-
Cut AI token usage by 96%? Here's how AWS Strands Agents does it.
AWS Strands Agents is a way to cut agent token usage by making models ask for only the context they need, when they need it. Instead of stuffing huge prompts up front, it uses tools, memory, and session state to keep agents lean, which matters for cost, latency, and scaling.
-
No OAuth Required: An MCP Client For AWS IAM
Dennis Traub for AWS Posted on Nov 18 • Edited on Nov 20 No OAuth Required: An MCP Client For AWS IAM # ai # agents # mcp # aws When Anthropic published the Model Context Protocol (MCP) , I immediately started experimenting with deployment options on AWS: First, I tried running MCP servers as AWS Lambda functions. A great solution in terms of simplicity and cost, but it also meant I had to manually manage session state across invocations.