AWS keyspaces documentation change
Summary
Revised 'AWS Direct Connect' to 'Direct Connect' in network configuration documentation
Security assessment
Consistency update for service naming. No modification to security controls or privacy features of VPC endpoints.
Diff
diff --git a/keyspaces/latest/devguide/vpc-endpoints.md b/keyspaces/latest/devguide/vpc-endpoints.md index ce514a04d..c2498508b 100644 --- a//keyspaces/latest/devguide/vpc-endpoints.md +++ b//keyspaces/latest/devguide/vpc-endpoints.md @@ -11 +11 @@ Interface VPC endpoints enable private communication between your virtual privat -AWS PrivateLink enables this by using an elastic network interface with private IP addresses in your VPC so that network traffic does not leave the Amazon network. Interface VPC endpoints don't require an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. For more information, see [Amazon Virtual Private Cloud](https://docs.aws.amazon.com/vpc/latest/userguide/) and [Interface VPC endpoints (AWS PrivateLink)](https://docs.aws.amazon.com/vpc/latest/privatelink/vpce-interface.html). +AWS PrivateLink enables this by using an elastic network interface with private IP addresses in your VPC so that network traffic does not leave the Amazon network. Interface VPC endpoints don't require an internet gateway, NAT device, VPN connection, or Direct Connect connection. For more information, see [Amazon Virtual Private Cloud](https://docs.aws.amazon.com/vpc/latest/userguide/) and [Interface VPC endpoints (AWS PrivateLink)](https://docs.aws.amazon.com/vpc/latest/privatelink/vpce-interface.html).