# AgentCore Memory adds fine-grained access control through Cedar policies

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

AWS announced on 28 August 2026 that Amazon Bedrock AgentCore Memory supports fine-grained access control. Placing a Memory resource behind an AgentCore Gateway with OAuth authentication lets Cedar policies limit each caller to their own actor data, namespaces derived from token claims, and specific Memory operations.

Amazon Bedrock AgentCore Memory now supports fine-grained access control, according to an AWS announcement dated 28 August 2026. You front the Memory resource with an AgentCore Gateway configured for OAuth (JWT) authentication and attach Cedar policies that restrict access based on the authenticated caller. AWS says you can make each user reach only their own actor data and limit memory records to namespaces taken from token claims.

The announcement adds that the feature rests on an AgentCore Memory connector, which exposes 12 Memory operations as Cedar actions, so policies can allow or deny specific operations per caller. For anyone asking what an agent can read from stored memory, this moves the check from application code to a policy layer. It depends on routing memory access through the gateway.

## Related pages

- [Amazon Quick custom permissions can deny new AI capabilities by default](/news/quick-custom-permissions-deny-by-default/)
- [AWS Nitro Sandboxes give pods, tasks and agents their own hardware-isolated VM](/news/nitro-sandboxes-eks-ecs-ec2-agents/)
- [Amazon Quick adds smart approvals for actions that agents take](/news/quick-smart-approvals-agentic-actions/)
- [All of them](/news/)

## Sources

- https://aws.amazon.com/about-aws/whats-new/2026/08/agentcorememory-fine-grained-access-control (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/news/agentcore-memory-fine-grained-access-control/
