AWS pinpoint documentation change
Summary
Updated references from 'AWS Direct Connect' to 'Direct Connect' and adjusted router description
Security assessment
Terminology update without changing security implications. Maintains existing guidance about private connections but doesn't introduce new security controls or address vulnerabilities.
Diff
diff --git a/pinpoint/latest/archguide/security-data-protection-internetwork-traffic.md b/pinpoint/latest/archguide/security-data-protection-internetwork-traffic.md index 73af629bb..b601616ab 100644 --- a//pinpoint/latest/archguide/security-data-protection-internetwork-traffic.md +++ b//pinpoint/latest/archguide/security-data-protection-internetwork-traffic.md @@ -15 +15 @@ Traffic between Amazon Pinpoint and on-premises clients and applicationsTraffic -To establish a private connection between Amazon Pinpoint and clients and applications on your on-premises network, you can use AWS Direct Connect. With AWS Direct Connect, you can link your network to an AWS Direct Connect location by using a standard, fiber-optic Ethernet cable. One end of the cable is connected to your router, and the other end is connected to an AWS Direct Connect router. For more information, see [What is AWS Direct Connect?](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html) in the _AWS Direct Connect User Guide_. +To establish a private connection between Amazon Pinpoint and clients and applications on your on-premises network, you can use Direct Connect. With Direct Connect, you can link your network to an AWS Direct Connect location by using a standard, fiber-optic Ethernet cable. One end of the cable is connected to your router, and the other end is connected to an Direct Connect router. For more information, see [What is Direct Connect?](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html) in the _Direct Connect User Guide_.