Skip to content
AI Agent Access Control

What an AI agent can access in AWS, and the controls that bound it

In AWS, an AI agent runs as an IAM role, and can reach whatever that identity's permissions and the network allow. The map covers 3 ways to run one: Amazon Bedrock Agents; Amazon Bedrock AgentCore; Self-hosted agent on AWS Lambda or Amazon EKS.

The map ยท The checklist

In AWS the agent is an IAM role. Amazon Bedrock Agents Classic runs as a service role, Amazon Bedrock AgentCore Runtime as an execution role, and a Lambda or EKS agent as its function or pod role. The checklist's AWS answers put the limits on that role: an SCP or permissions boundary as the ceiling (ab-07), an explicit deny of IAM changes and destructive actions (ab-08), and trust policy conditions that name the agent (ab-04).

Around the role sit the network and the tools. The checklist uses private subnets, security groups and AWS Network Firewall for egress (ab-15, ab-16), VPC interface endpoints for AWS APIs (ab-17), and a separate role and resource-based policy for each tool function (ab-19, ab-20). Logging is an organization trail plus data events, which trails do not log by default (ab-27, ab-28).

Agent platformRuns asNetwork
Amazon Bedrock Agents (now Amazon Bedrock Agents Classic)AWS documents that the agent runs as an IAM service role that Amazon Bedrock assumes.AWS documents interface endpoints (AWS PrivateLink) for the bedrock-agent and bedrock-agent-runtime APIs, with an endpoint policy you can attach.
Amazon Bedrock AgentCore (Runtime, Gateway, Identity)Runtime runs the agent under an IAM execution role that AgentCore assumes.AWS documents VPC connectivity for Runtime and the built-in Code Interpreter and Browser tools: AgentCore creates network interfaces in your VPC through a service-linked role.
Self-hosted agent on AWS Lambda or Amazon EKSA Lambda function runs as its execution role.AWS documents attaching a Lambda function to a VPC: private subnets for private resources, and a public subnet does not give a function internet access.

The checklist, AWS column

Where Act is behind

Act draws the boundary at the access layer (cloud IAM and network controls, and the gateways or MCP servers in front of agents); it does not inspect prompts or model outputs, which needs a different tool. Your team applies the boundaries it proposes, and its customer evidence for AI boundaries is less mature than for its core access control.

Sources

  1. docs.aws.amazon.com/bedrock/latest/userguide/agents.html, read 10 Nov 2026
  2. docs.aws.amazon.com/bedrock/latest/userguide/agents-classic-maintenance-mode.htm, read 10 Nov 2026
  3. docs.aws.amazon.com/bedrock/latest/userguide/agents-permissions.html, read 10 Nov 2026
  4. docs.aws.amazon.com/bedrock/latest/userguide/agents-lambda.html, read 10 Nov 2026
  5. docs.aws.amazon.com/lambda/latest/dg/lambda-intro-execution-role.html, read 10 Nov 2026
  6. docs.aws.amazon.com/bedrock/latest/userguide/agents-how.html, read 10 Nov 2026
  7. docs.aws.amazon.com/bedrock/latest/userguide/vpc-interface-endpoints.html, read 10 Nov 2026
  8. docs.aws.amazon.com/bedrock/latest/userguide/usingVPC.html, read 10 Nov 2026
  9. docs.aws.amazon.com/bedrock/latest/userguide/logging-using-cloudtrail.html, read 10 Nov 2026
  10. docs.aws.amazon.com/bedrock/latest/userguide/model-invocation-logging.html, read 10 Nov 2026

Last reviewed 16 Nov 2026.