AWS firehose documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in VPC endpoint documentation
Security assessment
Service name update without altering the security posture of VPC endpoint configurations. PrivateLink security benefits remain described equivalently.
Diff
diff --git a/firehose/latest/dev/vpc.md b/firehose/latest/dev/vpc.md index d74ce2564..4a352dd04 100644 --- a//firehose/latest/dev/vpc.md +++ b//firehose/latest/dev/vpc.md @@ -9 +9 @@ Using interface VPC endpoints (AWS PrivateLink) for FirehoseSupported AWS Region -You can use an interface VPC endpoint (AWS PrivateLink) to access Amazon Data Firehose from your VPC without requiring an Internet Gateway or NAT Gateway. Interface VPC endpoints don't require an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Interface VPC endpoints are powered by AWS PrivateLink, an AWS technology that enables private communication between AWS services using an elastic network interface with private IPs in your Amazon VPC. For more information, see [Amazon Virtual Private Cloud](http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Introduction.html). +You can use an interface VPC endpoint (AWS PrivateLink) to access Amazon Data Firehose from your VPC without requiring an Internet Gateway or NAT Gateway. Interface VPC endpoints don't require an internet gateway, NAT device, VPN connection, or Direct Connect connection. Interface VPC endpoints are powered by AWS PrivateLink, an AWS technology that enables private communication between AWS services using an elastic network interface with private IPs in your Amazon VPC. For more information, see [Amazon Virtual Private Cloud](http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Introduction.html).