1. Home
  2. |
  3. Blog
  4. |
  5. Insights from Gartner® IAM 2026 in London

FAQ

From your internal systems, such as APIs, databases and LDAP directories. They are retrieved at the moment of each decision, and not from the agent or its token. The token only says who the user is, so a change in those systems applies to the next tool call without a new token.

Before the search runs, the policy engine returns a condition that describes which documents may be read by this user. The condition is applied inside the vector store, so documents that the user may not read are never retrieved.

No. The integration attaches to the AgentCore Gateway, so every tool call is checked on its way through. The agent needs no new library, no prompt change and no redeploy.

So that one policy can govern agents, applications and data wherever they run, not only on AWS. An external engine can also return a filter rather than a yes or no, which can be applied to the results of a search.

Yes. The AgentCore Gateway authenticates every caller. On top of that, Policy in Amazon Bedrock AgentCore evaluates Cedar policies on every tool call. For an organization that runs only on AWS and only needs allow-or-deny decisions, that may be enough.

Related Articles

This website uses cookies

Cookies consist of small text files. They contain data that is stored on your device. To enable us to place certain types of cookies we need to obtain your consent. At Axiomatics AB, corp. ID no. 556708-1012, we use the following kinds of cookies. To read more about which cookies we use and storage times, click here to access our cookies policy.

Manage your cookie-settings

Necessary cookies

Check to consent to the use of Necessary cookies

Nödvändiga cookies

Cookie Syfte Lagringstid
consents

Används för att hantera samtycke

1 år
__hssrc

Närhelst HubSpot ändrar sessionscookien, ställs denna cookie också in för att avgöra om besökaren har startat om sin webbläsare.

Session

Cookies for statistics

Check to consent to the use of Cookies for statistics

Cookies för statistik

Cookie Syfte Lagringstid
__hssc

För att lagra anonymiserad statistik.

30 minuter
_gcl_au

För att lagra och spåra konverteringar.

3 månader

 

Cookies for ad-tracking

Check to consent to the use of Cookies for ad-tracking

Cookies för annonsmätning

Cookie Syfte Lagringstid
__hstc

För att lagra besökstid.

6 månader
hubspotutk

För att lagra och spåra en besökares identitet.

6 månader

 

Ad measurement user cookies

Check to consent to the use of Ad measurement user cookies
In order to show relevant ads we place cookies to tailor ads for you

Personalized ads cookies

Check to consent to the use of Personalized ads cookies
To show relevant and personal ads we place cookies to provide unique offers that are tailored to your user data