bedrockagent_create_vpc_configuration: Creates a VPC configuration that lets a knowledge base...

In paws.machine.learning: 'Amazon Web Services' Machine Learning Services

Creates a VPC configuration that lets a knowledge base connect to a resource in your private VPC

Description

Creates a VPC configuration that lets a knowledge base connect to a resource in your private VPC. This operation is asynchronous: it returns a vpcConfigurationId with status CREATING. Poll get_vpc_configuration until the status becomes CREATED or CREATE_FAILED.

See https://www.paws-r-sdk.com/docs/bedrockagent_create_vpc_configuration/ for full documentation.

Usage

bedrockagent_create_vpc_configuration(
  knowledgeBaseId,
  clientToken = NULL,
  vpcId,
  subnetIds,
  resourceTarget,
  port,
  protocol,
  resolutionMode,
  hostHeader = NULL,
  tlsServerName = NULL,
  name = NULL,
  description = NULL
)

Arguments

knowledgeBaseId	[required] The unique identifier of the knowledge base to associate this VPC configuration with.
clientToken	A unique, case-sensitive identifier to ensure that the operation completes no more than one time. If this token matches a previous request, the service ignores the request but does not return an error.
vpcId	[required] The identifier of the VPC that the knowledge base connects through to reach the resource.
subnetIds	[required] The subnets, in the VPC identified by vpcId, that the knowledge base uses to connect to the resource.
resourceTarget	[required] The private IPv4 address or DNS name of the resource you want the knowledge base to reach. The target must be privately reachable from inside your VPC, such as an internal load balancer or a private IP. The following are not supported: Internet-facing endpoints Loopback addresses Link-local addresses Wildcard addresses Multicast addresses IPv6 literals
port	[required] The port on which to reach the resource.
protocol	[required] The protocol used to connect to the resource. Specify HTTP for plaintext or HTTPS for TLS. When you specify HTTPS, you must also provide tlsServerName.
resolutionMode	[required] Controls how a domain-name resourceTarget is resolved. This applies only when the target is a domain name; it has no effect for IP-address targets, which have no name to resolve. In all cases the resolved address must be reachable from inside your VPC. Valid values: IN_VPC (default, recommended) – The target domain name is resolved privately, using the DNS resolvers of the VPC, such as private Route 53 hosted zones or on-premises DNS reachable from the VPC. Use this for targets that are private to your VPC, such as internal load balancers, private hosted-zone names, or on-premises hosts. PUBLIC – The target domain name is resolved against public DNS resolvers. Select this only when the target's domain name must be resolved through public DNS and the resulting address is still reachable from the VPC, an uncommon split-horizon configuration. If you are unsure, use IN_VPC.
hostHeader	An optional HTTP Host header value to send when invoking the resource. Set this only if your resource (or an upstream router or ingress) routes by the Host header and that host differs from the target. This setting is independent of tlsServerName.
tlsServerName	The expected TLS server name. The service matches this value against the Subject Alternative Names on your resource's TLS certificate during invocation. This field is required when protocol is HTTPS. Set it to a hostname on your certificate, such as app.internal.example.com. You can use a single leftmost wildcard, such as ⁠*.example.com⁠. The value must be a hostname without a port.
name	An optional human-readable name for the VPC configuration. If you don't specify a name, the VPC configuration has no name.
description	An optional description of the VPC configuration. If you don't specify a description, the VPC configuration has no description.

paws.machine.learning documentation built on Oct. 8, 2026, 9:06 a.m.