AWS pinpoint documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in PrivateLink context
Security assessment
Service name abbreviation update in existing security context. No change to VPC endpoint security implementation or vulnerability mitigation.
Diff
diff --git a/pinpoint/latest/developerguide/security-vpc-endpoints.md b/pinpoint/latest/developerguide/security-vpc-endpoints.md index dd5f661b5..25864034d 100644 --- a//pinpoint/latest/developerguide/security-vpc-endpoints.md +++ b//pinpoint/latest/developerguide/security-vpc-endpoints.md @@ -13 +13 @@ You can establish a private connection between your virtual private cloud (VPC) -Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink/), a technology that allows you to privately access Amazon Pinpoint APIs without an internet gateway, NAT device, VPN connection, or AWS Direct Connect. Instances in your VPC don't need public IP addresses to communicate with the Amazon Pinpoint APIs that integrate with AWS PrivateLink. +Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink/), a technology that allows you to privately access Amazon Pinpoint APIs without an internet gateway, NAT device, VPN connection, or Direct Connect. Instances in your VPC don't need public IP addresses to communicate with the Amazon Pinpoint APIs that integrate with AWS PrivateLink.