AWS amazondynamodb documentation change
Summary
Updated references from 'AWS Direct Connect' to 'Direct Connect' and adjusted documentation links
Security assessment
The changes are minor terminology updates (removing redundant 'AWS' prefix) and link text adjustments. No security implications are introduced or modified in the PrivateLink documentation.
Diff
diff --git a/amazondynamodb/latest/developerguide/privatelink-streams.md b/amazondynamodb/latest/developerguide/privatelink-streams.md index 006590e76..abad35a80 100644 --- a//amazondynamodb/latest/developerguide/privatelink-streams.md +++ b//amazondynamodb/latest/developerguide/privatelink-streams.md @@ -9 +9 @@ Considerations when using AWS PrivateLink for Amazon DynamoDB StreamsCreating an -With AWS PrivateLink for Amazon DynamoDB Streams, you can provision interface Amazon VPC endpoints (interface endpoints) in your virtual private cloud (Amazon VPC). These endpoints are directly accessible from applications that are on premises over VPN and AWS Direct Connect, or in a different AWS Region over Amazon VPC peering. Using AWS PrivateLink and interface endpoints, you can simplify private network connectivity from your applications to DynamoDB Streams. +With AWS PrivateLink for Amazon DynamoDB Streams, you can provision interface Amazon VPC endpoints (interface endpoints) in your virtual private cloud (Amazon VPC). These endpoints are directly accessible from applications that are on premises over VPN and Direct Connect, or in a different AWS Region over Amazon VPC peering. Using AWS PrivateLink and interface endpoints, you can simplify private network connectivity from your applications to DynamoDB Streams. @@ -11 +11 @@ With AWS PrivateLink for Amazon DynamoDB Streams, you can provision interface Am -Applications in your Amazon VPC do not need public IP addresses to communicate with DynamoDB Streams using Amazon VPC interface endpoints for DynamoDB Streams operations. Interface endpoints are represented by one or more elastic network interfaces (ENIs) that are assigned private IP addresses from subnets in your Amazon VPC. Requests to DynamoDB Streams over interface endpoints stay on the Amazon network. You can also access interface endpoints in your Amazon VPC from on-premises applications through AWS Direct Connect or AWS Virtual Private Network (AWS VPN). For more information about how to connect your AWS Virtual Private Network with your on-premises network, see the [_AWS Direct Connect User Guide_](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html) and the [_AWS Site-to-Site VPN User Guide_](https://docs.aws.amazon.com/vpn/latest/s2svpn/VPC_VPN.html). +Applications in your Amazon VPC do not need public IP addresses to communicate with DynamoDB Streams using Amazon VPC interface endpoints for DynamoDB Streams operations. Interface endpoints are represented by one or more elastic network interfaces (ENIs) that are assigned private IP addresses from subnets in your Amazon VPC. Requests to DynamoDB Streams over interface endpoints stay on the Amazon network. You can also access interface endpoints in your Amazon VPC from on-premises applications through Direct Connect or AWS Virtual Private Network (AWS VPN). For more information about how to connect your AWS Virtual Private Network with your on-premises network, see the [_Direct Connect User Guide_](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html) and the [_AWS Site-to-Site VPN User Guide_](https://docs.aws.amazon.com/vpn/latest/s2svpn/VPC_VPN.html).