AWS iot documentation change
Summary
Updated service name reference from 'AWS Direct Connect' to 'Direct Connect' in VPC endpoint documentation
Security assessment
Terminology update with no security impact. PrivateLink security advantages (no public IPs, encrypted traffic) remain unchanged.
Diff
diff --git a/iot/latest/developerguide/device-advisor-vpc-endpoint.md b/iot/latest/developerguide/device-advisor-vpc-endpoint.md index 2c3601352..5db0e8c1a 100644 --- a//iot/latest/developerguide/device-advisor-vpc-endpoint.md +++ b//iot/latest/developerguide/device-advisor-vpc-endpoint.md @@ -11 +11 @@ You can establish a private connection between your VPC and the AWS IoT Core Dev -[AWS PrivateLink](http://aws.amazon.com/privatelink) powers the interface endpoints used with your IoT devices. This service helps you access the AWS IoT Core Device Advisor test endpoint privately without an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC that send TCP and MQTT packets don't need public IP addresses to communicate with AWS IoT Core Device Advisor test endpoints. Traffic between your VPC and AWS IoT Core Device Advisor doesn't leave AWS Cloud. Any TLS and MQTT communication between IoT devices and Device Advisor test cases stay within the resources in your AWS account. +[AWS PrivateLink](http://aws.amazon.com/privatelink) powers the interface endpoints used with your IoT devices. This service helps you access the AWS IoT Core Device Advisor test endpoint privately without an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC that send TCP and MQTT packets don't need public IP addresses to communicate with AWS IoT Core Device Advisor test endpoints. Traffic between your VPC and AWS IoT Core Device Advisor doesn't leave AWS Cloud. Any TLS and MQTT communication between IoT devices and Device Advisor test cases stay within the resources in your AWS account.