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

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

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.

## 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](https://docs.aws.amazon.com/lambda/latest/dg/configuration-vpc.html))
- "All traffic between your agent and your VPC travels securely within Google's network, never traversing the public internet." ([source](https://docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/private-service-connect-interface))
- "No public egress : Foundational infrastructure provides the right authentication and security for your agents and tools, without requiring trusted service bypass." ([source](https://learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/virtual-networks))

- [Previous: Limit data access with tags, attributes or conditions, not only resource lists](/checklist/condition-based-data-access/)
- [Next: Allow outbound traffic only to the destinations the agent needs](/checklist/allowlist-egress/)

## Related pages

- [Allow outbound traffic only to the destinations the agent needs: the check, and how in AWS, Google Cloud and Azure](/checklist/allowlist-egress/)
- [Reach cloud APIs and data stores through private endpoints: the check, and how in AWS, Google Cloud and Azure](/checklist/private-endpoints-for-cloud-apis/)
- [Keep the agent's code from reading node, instance or other workloads' credentials: the check, and how in AWS, Google Cloud and Azure](/checklist/credential-isolation/)

## Sources

- docs.aws.amazon.com/lambda/latest/dg/configuration-vpc.html: https://docs.aws.amazon.com/lambda/latest/dg/configuration-vpc.html (read 10 Nov 2026)
- docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/private-ser: https://docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/private-service-connect-interface (read 10 Nov 2026)
- learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/virtual-networks: https://learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/virtual-networks (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/checklist/private-network-no-direct-internet/
