Use interface VPC endpoints (AWS PrivateLink) to create a private connection between your VPC and your AgentCore resources

You can use AWS PrivateLink to create a private connection between your VPC and Amazon Bedrock AgentCore. You can access AgentCore as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to access AgentCore.

You establish this private connection by creating an interface endpoint, powered by AWS PrivateLink. We create an endpoint network interface in each subnet that you enable for the interface endpoint. These are requester-managed network interfaces that serve as the entry point for traffic destined for AgentCore.

For more information, see Access AWS services through AWS PrivateLink in the AWS PrivateLink Guide.

Considerations for AgentCore

Before you set up an interface endpoint for AgentCore, review Considerations in the AWS PrivateLink Guide.

AgentCore supports invoking gateways through the interface endpoint.

By default, full access to AgentCore is allowed through the interface endpoint. Alternatively, you can associate a security group with the endpoint network interfaces to control traffic to AgentCore through the interface endpoint.

Create an interface endpoint for AgentCore

You can create an interface endpoint for AgentCore using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see Create an interface endpoint in the AWS PrivateLink Guide.

Create an interface endpoint for AgentCore using one of the following service names:

• For AgentCore Gateway :

  com.amazonaws.region.bedrock-agentcore.gateway

If you enable private DNS for the interface endpoint, you can make API requests to AgentCore using its default Regional DNS name. For example, bedrock-agentcore.us-east-1.amazonaws.com.

Create an endpoint policy for your interface endpoint

An endpoint policy is an IAM resource that you can attach to an interface endpoint. The default endpoint policy allows full access to AgentCore through the interface endpoint. To control the access allowed to AgentCore from your VPC, attach a custom endpoint policy to the interface endpoint.

An endpoint policy specifies the following information:

• The principals that can perform actions (AWS accounts, IAM users, and IAM roles).

  • For AgentCore Gateway , if your gateway ingress isn't AWS Signature Version 4 (SigV4)-based (for example, if you use OAuth instead), you must specify the Principal field as the wildcard *. SigV4 -based authentication allows you to define the Principal as a specific AWS identity.

• The actions that can be performed.

• The resources on which the actions can be performed.

For more information, see Control access to services using endpoint policies in the AWS PrivateLink Guide.

Example: VPC endpoint policy for AgentCore Gateway actions

The following is an example of a custom endpoint policy. When you attach this policy to your interface endpoint, it allows all principals to invoke the gateway specified in the Resource field.

{
   "Statement": [
      {
         "Principal": "*",
         "Effect": "Allow",
         "Action": "*",
         "Resource":"arn:aws::bedrock-agentcore:us-east-1::gateway/my-gateway"
      }
   ]
}