AgentCore Memory exposes 12 Cedar actions

AWS’s AgentCore Memory now exposes 12 memory operations as Cedar actions, letting teams enforce per-user or per-tenant isolation through an OAuth/JWT-authenticated gateway instead of custom authorization code in the service’s new access-control release. The control moves memory boundaries into the infrastructure layer, while Claude’s shared-memory economics shows why those boundaries matter once context persists across work; teams adding long-lived agent memory should treat namespace policy as a deployment gate, not a prompt convention.