AWS bedrock documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' for consistency in terminology
Security assessment
The change only modifies branding terminology without altering security-related content or addressing vulnerabilities. No security implications identified.
Diff
diff --git a/bedrock/latest/userguide/vpc-interface-endpoints.md b/bedrock/latest/userguide/vpc-interface-endpoints.md index dd3c9c3c3..3804c60c2 100644 --- a//bedrock/latest/userguide/vpc-interface-endpoints.md +++ b//bedrock/latest/userguide/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. You can access Amazon Bedrock 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 Amazon Bedrock. +You can use AWS PrivateLink to create a private connection between your VPC and Amazon Bedrock. You can access Amazon Bedrock 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 Amazon Bedrock.