AWS transcribe documentation change
Summary
Updated documentation to replace 'AWS Direct Connect' with 'Direct Connect' in VPC endpoint description
Security assessment
The change is a minor terminology adjustment (removing 'AWS' from 'Direct Connect'). It does not introduce or modify security controls, nor does it address a specific vulnerability.
Diff
diff --git a/transcribe/latest/dg/med-vpc-interface-endpoints.md b/transcribe/latest/dg/med-vpc-interface-endpoints.md index 0b26892b1..812a8b059 100644 --- a//transcribe/latest/dg/med-vpc-interface-endpoints.md +++ b//transcribe/latest/dg/med-vpc-interface-endpoints.md @@ -9 +9 @@ Considerations for Amazon Transcribe Medical VPC endpointsCreating an interface -You can establish a private connection between your VPC and Amazon Transcribe Medical by creating an _interface VPC endpoint_. Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that enables you to privately access Amazon Transcribe 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 Transcribe Medical APIs. Traffic between your VPC and Amazon Transcribe Medical does not leave the Amazon network. +You can establish a private connection between your VPC and Amazon Transcribe Medical by creating an _interface VPC endpoint_. Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that enables you to privately access Amazon Transcribe 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 Transcribe Medical APIs. Traffic between your VPC and Amazon Transcribe Medical does not leave the Amazon network.