AWS bedrock-agentcore documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' for terminology consistency
Security assessment
Branding terminology update without security implications. Network security controls remain unchanged.
Diff
diff --git a/bedrock-agentcore/latest/devguide/vpc-interface-endpoints.md b/bedrock-agentcore/latest/devguide/vpc-interface-endpoints.md index be8919245..d9fd3f70b 100644 --- a//bedrock-agentcore/latest/devguide/vpc-interface-endpoints.md +++ b//bedrock-agentcore/latest/devguide/vpc-interface-endpoints.md @@ -9 +9 @@ ConsiderationsCreate an interface endpointCreate an endpoint policy -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 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 Direct Connect connection. Instances in your VPC don't need public IP addresses to access AgentCore.