AI Infrastructureaws

Keeping Amazon Bedrock Traffic Private with VPC Endpoints

P&C

Prompt & Circuit Editorial

October 26, 2026 · 12 Min Read

Keeping Amazon Bedrock Traffic Private with VPC Endpoints

Why this matters

Many security reviews of generative AI workloads start with one question: does the model call cross the public internet? Amazon Bedrock answers it with AWS PrivateLink, which lets instances in a VPC reach the service without an internet gateway, NAT device, VPN connection or Direct Connect connection, and without public IP addresses [2]. The setup is short, but several choices inside it change how your applications, DNS and access controls behave. This guide walks through those choices in the order an architect meets them.

What a Bedrock interface endpoint is

You create the private connection by creating an interface endpoint, which is powered by AWS PrivateLink [2]. For every subnet you enable for the endpoint, AWS creates an endpoint network interface, a requester-managed network interface that is the entry point for traffic destined for Bedrock [2]. In PrivateLink terms, the consumer creates a VPC endpoint to reach an endpoint service hosted by a provider, and the provider can be AWS itself [4]. Traffic between the VPC endpoint and the service stays within the AWS network and does not traverse the public internet [4].

The general PrivateLink documentation describes the technology as highly available and scalable, and says you control the specific API endpoints, sites, services and resources reachable from your VPC [6]. For Bedrock, the user guide states that its endpoints are available in multiple Availability Zones [2], so the subnets you pick for the endpoint determine where its network interfaces live.

Pick the right endpoint for each API

Bedrock is not one endpoint. The documentation lists five categories of API calls that can go through VPC endpoints, each with its own suffix [2]:

API categoryEndpoint suffix
Control plane API actionsbedrock
Runtime API actionsbedrock-runtime
Mantle API actionsbedrock-mantle
Agents build-time API actionsbedrock-agent
Agents runtime API actionsbedrock-agent-runtime

The service names follow the pattern com.amazonaws.region.suffix, and there are two additional FIPS service names, bedrock-fips and bedrock-runtime-fips [2]. Those FIPS endpoint services are available in us-east-1, us-east-2, us-west-2, ca-central-1, us-gov-east-1 and us-gov-west-1 [2]. If your compliance regime requires FIPS 140-3 validated cryptographic modules when accessing AWS through a command line interface or an API, the Bedrock data protection page says to use a FIPS endpoint [5].

The practical consequence is that a private design needs one endpoint per API surface you actually call. An application that only invokes models needs the runtime endpoint. A pipeline that also creates or manages resources needs the control plane endpoint, and an agent-based application needs the agent endpoints. Inventory the API calls before you create endpoints, because each additional endpoint is another set of network interfaces in each enabled subnet [2].

Private DNS decides whether your code changes

After you create the endpoint you can enable a private DNS hostname by selecting Enable Private DNS Name in the VPC console [2]. The two modes behave differently:

  • With private DNS enabled, you can call Bedrock using its default Regional DNS name, such as bedrock-runtime.region.amazonaws.com, and no code changes are needed [2].
  • Without private DNS, you must specify the VPC endpoint URL explicitly in your API calls, for example with the --endpoint-url flag in the AWS CLI or the endpoint_url parameter when creating a boto3 client [2].

Note the Mantle endpoint's default name uses a different domain, bedrock-mantle.region.api.aws, rather than amazonaws.com [2]. If you maintain DNS allow lists or firewall rules by domain, account for it.

For most teams, enabling private DNS is the lower-risk option, because applications keep using standard service names and nothing in application configuration has to know that a private path exists. Explicit endpoint URLs make sense when a single VPC needs to be deliberate about which calls use the private path, but they put routing knowledge into every client. The PrivateLink documentation also notes that Amazon Route 53 can route traffic to a VPC endpoint and can be used for split-horizon DNS, where requests from inside the consumer VPC resolve to the private addresses of the endpoint network interfaces and requests from outside continue to resolve to public endpoints [4].

Endpoint policies: the default is wide open

An endpoint policy is an IAM resource policy that you attach to a VPC endpoint, and it determines which principals can use the endpoint [4]. The Bedrock guide is direct about the starting point: the default endpoint policy allows full access to Bedrock through the interface endpoint [2]. The general PrivateLink documentation shows the default policy as an Allow statement with Principal, Action and Resource all set to a wildcard [3].

A custom policy specifies the principals that can perform actions, the actions themselves and the resources they apply to [2]. The Bedrock examples grant the runtime actions bedrock:InvokeModel and bedrock:InvokeModelWithResponseStream, and for Mantle the action bedrock-mantle:CreateInference [2]. These examples are written for all principals on all resources, so they narrow the actions but not the callers; tightening principals and resources is up to you.

Several constraints apply when you write them:

  • An endpoint policy is a JSON document in the IAM policy language and must contain a Principal element [3].
  • The policy cannot exceed 20,480 characters, including white space [3].
  • You can attach a single endpoint policy to an endpoint and update it at any time, but changes can take a few minutes to take effect [3].
  • Wildcards and numeric condition operators cannot be used with global context keys that reference system-generated identifiers, for example aws:PrincipalAccount or aws:SourceVpc [3].
  • When you use a string condition operator, you need at least six consecutive characters before or after each wildcard character [3].

An endpoint policy does not override or replace identity-based or resource-based policies [3]. Treat it as an additional boundary on top of IAM, not a substitute for it [3].

What a VPC endpoint does not cover

A private path for API calls is one layer of data protection, not all of it. Bedrock's data protection page applies the AWS shared responsibility model and still recommends multi-factor authentication, TLS (it requires TLS 1.2 and recommends TLS 1.3), CloudTrail logging and the use of AWS encryption solutions [5]. It also warns against putting confidential information into tags or free-form text fields such as a Name field, because those may be used for billing or diagnostic logs [5].

Bedrock features that touch other services need their own network design. The VPC overview lists model customization jobs, batch inference and Amazon Bedrock Knowledge Bases accessing Amazon OpenSearch Serverless through an interface endpoint as features where a VPC can protect your data [1]. It also recommends a VPC so that you can monitor all network traffic in and out of the job containers with VPC Flow Logs [1]. For data stored in Amazon S3, the guide recommends keeping the default DNS settings for the endpoint route table so that standard S3 URLs resolve [1]. Note that S3 and DynamoDB use gateway endpoints, which do not use AWS PrivateLink, unlike interface endpoints [4]. A private Bedrock design therefore usually combines more than one endpoint type.

Decision guide

SituationSuggested approach
Workloads in private subnets that only invoke modelsRuntime interface endpoint with private DNS enabled [2]
Agents or resource management from the same VPCAdd the matching agent or control plane endpoints [2]
FIPS 140-3 requirementUse the FIPS endpoint services in a supported Region [2][5]
Several teams share one VPCCustom endpoint policy to limit actions and principals [2][3]
Clients that cannot use the default DNS namesPrivate DNS off, explicit endpoint URLs in clients [2]

Limits and open questions

The sources reviewed for this article describe the endpoint behaviour but do not state pricing, per-endpoint throughput limits or quotas for Bedrock endpoints. The PrivateLink overview only points to a separate pricing page for VPC endpoints [6]. Check that page and your account quotas before you commit to a design with many endpoints across many accounts. The documentation reviewed here also does not describe a Bedrock-specific private path for every model feature, so test each feature you plan to use from a subnet with no internet route before you declare the design private.

Architect's checklist

  • List every Bedrock API surface your workloads call and create one interface endpoint per surface [2].
  • Decide on private DNS per VPC; enable it unless clients must choose the path explicitly [2].
  • Replace the default full-access endpoint policy with one that names the actions you allow [2][3].
  • Keep the policy under 20,480 characters and plan for a few minutes of propagation after changes [3].
  • Use FIPS endpoint services where a FIPS 140-3 requirement applies, and confirm your Region supports them [2][5].
  • Cover adjacent services such as S3 and OpenSearch Serverless with their own private paths [1][4].
  • Turn on VPC Flow Logs and CloudTrail so you can verify that traffic uses the path you intended [1][5].
  • Test from a subnet with no internet route before sign-off.

Sources

Numbers in square brackets refer to these sources, checked on 2026-10-26.

  1. Protect your data using Amazon VPC and AWS PrivateLink - Amazon Bedrock
  2. Use interface VPC endpoints (AWS PrivateLink) to create a private connection between your VPC and Amazon Bedrock - Amazon Bedrock
  3. Control access to VPC endpoints using endpoint policies - Amazon Virtual Private Cloud
  4. AWS PrivateLink concepts - Amazon Virtual Private Cloud
  5. Data protection - Amazon Bedrock
  6. What is AWS PrivateLink? - Amazon Virtual Private Cloud
Tags:awsbedrockprivatelinknetworkingsecurity
Share Article

Responses (0)

Sign in to join the conversation and share your thoughts.

P&C

Prompt & Circuit Editorial

Contributing Editor

Articles on AI infrastructure for cloud architects, written from official vendor sources and checked claim by claim before publishing.