AWS transcribe documentation change
Summary
Updated VPC endpoint documentation to use 'Direct Connect' instead of 'AWS Direct Connect'
Security assessment
Consistency update for service naming. The security implications of using VPC endpoints remain unchanged.
Diff
diff --git a/transcribe/latest/dg/vulnerability-analysis-and-management.md b/transcribe/latest/dg/vulnerability-analysis-and-management.md index 6d9efaec1..617383127 100644 --- a//transcribe/latest/dg/vulnerability-analysis-and-management.md +++ b//transcribe/latest/dg/vulnerability-analysis-and-management.md @@ -13 +13 @@ Configuration and IT controls are a shared responsibility between AWS and you, o -You can establish a private connection between your VPC and Amazon Transcribe by creating an _interface VPC endpoint_. Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that you can use to privately access Amazon Transcribe 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 APIs. Traffic between your VPC and Amazon Transcribe does not leave the Amazon network. +You can establish a private connection between your VPC and Amazon Transcribe by creating an _interface VPC endpoint_. Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that you can use to privately access Amazon Transcribe 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 APIs. Traffic between your VPC and Amazon Transcribe does not leave the Amazon network.