# Reach cloud APIs and data stores through private endpoints

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

Check 17 of 30: Reach cloud APIs and data stores through private endpoints. Calls to cloud services over public addresses can be made from anywhere that holds valid credentials. Private endpoints keep the path inside your network, so stolen credentials are harder to use from outside.

## Why it matters

Calls to cloud services over public addresses can be made from anywhere that holds valid credentials. Private endpoints keep the path inside your network, so stolen credentials are harder to use from outside.

## How, in each cloud

- **AWS:** Create VPC interface endpoints with AWS PrivateLink.
- **Google Cloud:** Use Private Google Access so VMs with only internal IP addresses can reach Google APIs.
- **Azure:** Use private endpoints, which put a service on a private IP address from your virtual network.

## What the documentation says

- "creating a VPC interface endpoint with AWS PrivateLink to establish a private connection to your data." ([source](https://docs.aws.amazon.com/bedrock/latest/userguide/usingVPC.html))
- "VM instances that only have internal IP addresses (no external IP addresses) can" ([source](https://cloud.google.com/vpc/docs/private-google-access))
- "A private endpoint is a network interface that uses a private IP address from your virtual network." ([source](https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-overview))

- [Previous: Allow outbound traffic only to the destinations the agent needs](/checklist/allowlist-egress/)
- [Next: Keep the agent's code from reading node, instance or other workloads' credentials](/checklist/credential-isolation/)

## Related pages

- [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/)
- [Give each tool function its own least-privilege role instead of the agent's role: the check, and how in AWS, Google Cloud and Azure](/checklist/tool-own-role/)
- [Restrict which principals can invoke each tool endpoint: the check, and how in AWS, Google Cloud and Azure](/checklist/restrict-tool-invokers/)

## Sources

- docs.aws.amazon.com/bedrock/latest/userguide/usingVPC.html: https://docs.aws.amazon.com/bedrock/latest/userguide/usingVPC.html (read 10 Nov 2026)
- cloud.google.com/vpc/docs/private-google-access: https://cloud.google.com/vpc/docs/private-google-access (read 10 Nov 2026)
- learn.microsoft.com/en-us/azure/private-link/private-endpoint-overview: https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-overview (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/checklist/private-endpoints-for-cloud-apis/
