Skip to content
AI Agent Access Control

A Bedrock agent runs as a service role, and the trust policy and the console-created role decide how far that role reaches

Bedrock agents run as IAM roles that the service assumes. This guide covers Agents Classic and AgentCore: the trust policy and its condition keys, the documented permission statements, the role the console creates, the Lambda resource-based policy for tools, and the gaps in AWS documentation.

See the ranking ยท All guides

Agents Classic runs as a service role that Bedrock assumes

AWS documents that Amazon Bedrock Agents Classic runs as an IAM service role. You can let Bedrock create the role automatically or supply a custom one. AWS's status page says you can no longer sign up for Agents Classic, that existing users can continue, and that AgentCore is the service it points to for similar capabilities. Anyone reviewing an existing agent still needs to read the role, because the agent is what that role can do. The role has two parts that matter: the trust policy, which says who may assume it, and the identity-based policy, which says what it may do once assumed. AWS states that Agents Classic will no longer be open to new customers starting July 30, 2026, a date that has passed as of this reading.

The trust policy should name the account and the agent

The documented trust policy allows the bedrock.amazonaws.com service principal to assume the role. AWS shows two optional conditions: aws:SourceAccount set to your account ID and aws:SourceArn matching agents in your Region and account. The sample ends the ARN with a wildcard, and AWS adds a note that, as a best practice, you should replace the * with specific agent IDs after you have created them. Without the conditions, AWS describes the confused deputy problem: an entity without permission to perform an action coerces a more-privileged entity to perform it. Scoping the trust to one agent is the checklist item scope trust to the agent.

The documented policy is short, and the console role is not shown

The documented identity-based policy has three standing statements: bedrock:InvokeModel on the named foundation models, s3:GetObject on the action group schema objects, and bedrock:Retrieve and bedrock:RetrieveAndGenerate on attached knowledge bases. Optional statements cover Provisioned Throughput, agent collaborators, guardrails, KMS decryption and files for code interpretation. The role that Bedrock creates automatically has no policy listed on that page, so its exact contents were none found on 2026-11-10. If your agent uses the automatic role, read the attached policy in IAM and compare it with the documented one before approval (check).

Tools add a second role and a resource-based policy

Each action group is defined by an OpenAPI schema or function details and is usually backed by a Lambda function. AWS documents that you must attach a resource-based policy to the function so Bedrock may invoke it. The function then runs under its own Lambda execution role, so the tool's reach is the function's role, not the agent's. Give each function a narrow role (check) and restrict the resource-based policy to the Bedrock service principal for one agent ARN (check). Also limit who holds iam:PassRole for the agent's role (check), since AWS documents PassRole as the permission needed to hand a role to a service.

Gateway and Identity add credentials beyond the execution role

AgentCore Gateway and AgentCore Identity carry access of their own. For targets that use IAM-based outbound authorization, the gateway service role signs the call with AWS Signature Version 4. AWS documents that the console or CLI can create that role for you with the permissions the target needs, and that each time you add a target the necessary permissions are attached. AgentCore Identity is a separate service for managing credentials so that agents can reach AWS resources and third-party services on behalf of users, and AWS says agent identities are implemented as workload identities. These credentials do not appear in the execution role, so a review that reads only that role will under-count the agent's reach.

A read order for a Bedrock agent review

Use the same order for both generations of the service. First, name the role and read its trust policy. Second, read its attached policies and compare them with the documented minimum. Third, list the tools, the function behind each, and the role each function runs as. Fourth, read the resource-based policy on each function. Fifth, check who holds iam:PassRole and the AgentCore or Bedrock administrative policies. Sixth, check the logging: Bedrock CloudTrail data events for the agent alias, and model invocation logging, which AWS documents as disabled by default. Record each result with the date. The AWS pages above change, and the map shows the read date for each platform entry.

AgentCore uses an execution role, and the console can create it

On AgentCore, Runtime needs an IAM execution role. The documented trust policy names the bedrock-agentcore.amazonaws.com service principal, with SourceAccount and a SourceArn that ends in a wildcard for the account. For the console to create the role, AWS lists iam:CreateRole limited to role names starting AmazonBedrockAgentCoreRuntimeDefaultServiceRole-, plus matching policy permissions. What that automatic role contains was none found on 2026-11-10. Gateway can create a service role and attach permissions each time you add a target, so the role grows with the target list. Review the role after every target is added, and replace the BedrockAgentCoreFullAccess policy on the people and pipelines that use AgentCore with a custom one, as AWS recommends.

Sources

  1. AWS: create a service role for Amazon Bedrock Agents, read 10 Nov 2026
  2. AWS: Lambda functions for Bedrock action groups, read 10 Nov 2026
  3. AWS: Bedrock Agents Classic maintenance mode, read 10 Nov 2026
  4. AWS: IAM permissions for AgentCore Runtime, read 10 Nov 2026
  5. AWS: AgentCore Gateway outbound authorization, read 10 Nov 2026
  6. AWS: the confused deputy problem, read 10 Nov 2026
  7. AWS: granting a user permissions to pass a role, read 10 Nov 2026

Last reviewed 16 Nov 2026.