Skip to content
AI Agent Access Control

By default an agent can reach the internet on most platforms, and private networking is a setting you must choose

What an agent can reach over the network depends on where it runs and what you attach. This guide covers private endpoints, VPC attachment and egress filtering for Bedrock, AgentCore, Agent Runtime, Foundry and self-hosted agents, with the defaults each provider documents and the gaps we found.

See the ranking ยท All guides

Reachability has two directions and the review needs both

Network reach for an agent means two things. The first is which services the agent can call: model endpoints, cloud APIs, data stores, tool endpoints and the open internet. The second is who can call the agent or its tools. Identity decides what a call is allowed to do, but the network decides whether a stolen credential or a hijacked prompt can send data to a server of the attacker's choosing. A private path makes every outside connection a decision someone made, and an open path makes it a default nobody did. The defaults below differ by platform, so a review should read them platform by platform instead of assuming one.

Inbound access to the agent and its tools is the other half

Reachability also covers who may call the agent and its tools. A tool endpoint that accepts calls from any caller can be used without the agent at all. The checklist asks for a restriction on which principals may invoke each tool (check). For a Bedrock action group that is a resource-based policy on the Lambda function allowing only the Bedrock service principal for one agent ARN. For Cloud Run it is granting the Invoker role only to the agent's service account. For Foundry it is assigning roles at agent scope, so access to one agent's endpoints does not extend to every agent in the project. These are identity controls, but they decide who can use a network path that already exists.

AWS offers endpoints for the APIs and VPC attachment for the compute

For Amazon Bedrock Agents Classic, AWS documents interface endpoints (AWS PrivateLink) for the bedrock-agent and bedrock-agent-runtime APIs, with an endpoint policy you can attach. AWS's VPC page lists model customization, batch inference and knowledge bases as the features it describes for VPC protection. Egress controls for the agent's own orchestration were none found on 2026-11-10. The network egress of an action group Lambda function follows that function's own VPC settings.

On AgentCore, 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. A public subnet does not give internet access: AWS says internet access needs private subnets with a route to a NAT Gateway. The same rule applies to Lambda, which AWS documents as needing private subnets to reach private resources. For an agent on Lambda or EKS, network controls for pods in EKS were none found in the pages read.

Google Cloud puts the agent in a managed network until you attach yours

Google documents that an agent on Agent Runtime runs in a Google-managed network without access to your VPC unless you configure a Private Service Connect interface. The interface gives private egress to your VPC and to on-premises resources, and Google says all traffic between the agent and your VPC stays inside Google's network. With VPC Service Controls, the interface is also required for internet access, and the project must be inside the perimeter before the agent is deployed, otherwise Google documents that the agent is not secured by the perimeter and continues to have public internet access.

For Cloud Run or GKE, Cloud Run can send egress traffic to a VPC network with Direct VPC egress (Google's recommendation) or a VPC connector. In GKE, Google documents that by default all Pods in a cluster can communicate with each other until network policy is enforced. Each of these defaults is a setting someone has to change on purpose, and the change belongs in the review record with the date it was made.

Azure documents a private setup for Foundry and open defaults elsewhere

Microsoft documents a Standard Setup for Foundry Agent Service with private networking: no public egress, and a delegated subnet from your virtual network. Private networking is documented for prompt agents, and hosted agents support a bring-your-own virtual network, with each session in a VM-isolated sandbox connected to your VNet. For Container Apps and AKS the defaults are open. Microsoft documents that Container Apps is publicly accessible by default and can talk only to internet-accessible endpoints until you supply your own virtual network, and that in AKS all pods can send and receive traffic without limitations by default.

Filter outbound traffic and keep the cloud APIs private

Four checks cover the network. Run agent compute on a private network (check). Allow outbound traffic only to destinations the agent needs, using security groups and AWS Network Firewall, VPC firewall rules, or network security groups and Azure Firewall (check). Reach cloud APIs through private endpoints (check). Keep the agent's code from reading node or neighbor credentials (check). A perimeter that stops copying of data out is a separate control (check). Record the gaps too: any cell in the checklist that reads none found is a question for the platform team. Each answer belongs in the review record next to the platform it came from.

A perimeter around the data is the last layer, and each cloud has a different form. AWS documents an endpoint policy as a resource-based policy attached to a VPC endpoint, which does not override identity-based or resource-based policies. Google documents VPC Service Controls as protecting against the risk of data exfiltration. Microsoft documents virtual network service endpoint policies as allowing data exfiltration only to specific Azure Storage accounts. Each is built by the network or platform team, not by the agent's builder, so the review should ask who owns it and when it was last tested.

Sources

  1. AWS: interface VPC endpoints for Amazon Bedrock, read 10 Nov 2026
  2. AWS: AgentCore Runtime and tools in a VPC, read 10 Nov 2026
  3. AWS: connect a Lambda function to a VPC, read 10 Nov 2026
  4. Google Cloud: Private Service Connect interface with Agent Runtime, read 10 Nov 2026
  5. Google Cloud: connect Cloud Run to a VPC network, read 10 Nov 2026
  6. Microsoft: private networking for Foundry Agent Service, read 10 Nov 2026
  7. Microsoft: networking in Azure Container Apps, read 10 Nov 2026

Last reviewed 16 Nov 2026.