Tag: bedrock
All the articles with the tag "bedrock".
-
AgentCore Memory: What an Agent Remembers When the Session Is Gone
A deployed agent's session is a microVM that vanishes when the call ends, so by default it starts every conversation from zero. Amazon Bedrock AgentCore Memory is the managed fix — automatic write, automatic recall, per-user isolation. I wired it into a real agent across two sessions and three tenants to see what it actually does, and where it still fades.
-
AgentCore Runtime: Where an Agent Actually Runs
An agent that thinks, calls a tool, waits, and thinks again is the wrong shape for a Lambda and the wrong thing to leave on a laptop. Amazon Bedrock AgentCore Runtime is the managed answer — a per-session microVM behind an HTTP contract. Here is what that contract actually demands, and what running an agent server-side looks like in the metrics.
-
Harness vs. Runtime: When to Graduate
Harness gives you a working agent in 20 seconds with 25 lines of configuration. Runtime takes 398 lines of code. Both run on the same compute. The graduation trigger that matters is not hooks or custom loops — it's per-user outbound identity.
-
Where AgentCore Sits in the Architecture
Place Amazon Bedrock AgentCore before you judge it: a governed server-side hub, entered through a browser where the human already authenticated, reaching tools through a gateway. I built that hub and ran it — an agent inside Runtime, gated by Cedar, grounded through a connector — and from that vantage two things I first read as gaps turned out to live in a layer AgentCore hands off to.
-
Build a Regression Suite for an Agent
I built a test suite for a support agent and found three classes of bugs that escape human review, output-quality scoring, and code review — and the regressions they taught me how to catch permanently.
-
Who May Call What: Per-User Authorization on AgentCore With Cedar
A valid token proves who is calling. AgentCore Policy is a Cedar engine on the gateway that answers who-may-call-what per user, per tool, per argument — default-deny, before the tool runs. I wired one up and watched it allow, then deny, the same call.
-
How AgentCore Gateway Turns Any API Into an Agent Tool
AgentCore Gateway is a managed front door between agents and tools. It handles inbound auth, outbound auth, and protocol translation once, so any API or Lambda becomes an MCP tool that every connected agent can call. Here is how the wiring actually works.
-
What Actually Gets Stored When You Put a Vector in S3 Vectors
A vector store keeps three things per record — a key, an array of floats, and a bag of metadata. Your document text is stored as metadata, and a 2 KB limit on the filterable part is what quietly breaks ingestion.