AWS push-notifications documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in private connection documentation
Security assessment
Branding terminology change. Security guidance about using private connections for traffic privacy remains equivalent.
Diff
diff --git a/push-notifications/latest/userguide/data-protection.md b/push-notifications/latest/userguide/data-protection.md index 76fc06961..5fbccfcc4 100644 --- a//push-notifications/latest/userguide/data-protection.md +++ b//push-notifications/latest/userguide/data-protection.md @@ -52 +52 @@ _Internetwork traffic privacy_ refers to securing connections and traffic betwee -To establish a private connection between AWS End User Messaging Push and clients and applications on your on-premises network, you can use AWS Direct Connect. This enables you to 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. 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 AWS End User Messaging Push and clients and applications on your on-premises network, you can use Direct Connect. This enables you to 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. 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_.