AWS comprehend-medical documentation change
Summary
Updated documentation to replace 'AWS Direct Connect connection' with 'Direct Connect connection' in VPC endpoint description
Security assessment
The change standardizes terminology but does not address a specific security vulnerability. The content describes security features (VPC endpoints and PrivateLink) but the edit itself is non-substantive.
Diff
diff --git a/comprehend-medical/latest/dev/comprehendmedical-vpcendpoints.md b/comprehend-medical/latest/dev/comprehendmedical-vpcendpoints.md index 0e36b1b87..c9d18a587 100644 --- a//comprehend-medical/latest/dev/comprehendmedical-vpcendpoints.md +++ b//comprehend-medical/latest/dev/comprehendmedical-vpcendpoints.md @@ -9 +9 @@ Considerations for Amazon Comprehend Medical VPC endpointsCreating an interface -You can establish a private connection between your VPC and Amazon Comprehend Medical by creating an _interface VPC endpoint_. Interface VPC endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that you can use to privately access Amazon Comprehend Medical APIs without an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with Amazon Comprehend Medical APIs. Traffic between your VPC and Amazon Comprehend Medical does not leave the Amazon network. +You can establish a private connection between your VPC and Amazon Comprehend Medical by creating an _interface VPC endpoint_. Interface VPC endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that you can use to privately access Amazon Comprehend Medical APIs without an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with Amazon Comprehend Medical APIs. Traffic between your VPC and Amazon Comprehend Medical does not leave the Amazon network.