Skip to content
AI Agent Access Control

Run agent compute on private networks with no direct path to the internet

Check 15 of 30: Run agent compute on private networks with no direct path to the internet. Compute with a direct internet path can send data out or pull in instructions from anywhere. A private network makes every outside path an explicit choice.

The whole checklist ยท The map

Why it matters

Compute with a direct internet path can send data out or pull in instructions from anywhere. A private network makes every outside path an explicit choice.

How, in each cloud

AWS
Attach functions to private subnets; AWS says a public subnet does not give a Lambda function internet access.
Google Cloud
Use a Private Service Connect interface so Agent Runtime traffic stays inside Google's network and never crosses the public internet.
Azure
Use the Foundry Standard Setup with private networking, which Microsoft documents as having no public egress.

What the documentation says

  • "To access private resources, connect your function to private subnets." (source)
  • "All traffic between your agent and your VPC travels securely within Google's network, never traversing the public internet." (source)
  • "No public egress : Foundational infrastructure provides the right authentication and security for your agents and tools, without requiring trusted service bypass." (source)

Sources

  1. docs.aws.amazon.com/lambda/latest/dg/configuration-vpc.html, read 10 Nov 2026
  2. docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/private-ser, read 10 Nov 2026
  3. learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/virtual-networks, read 10 Nov 2026

Last reviewed 16 Nov 2026.