AWS iot-wireless documentation change
Summary
Updated VPN terminology from 'AWS VPN' to 'Site-to-Site VPN' in data plane API endpoint access instructions
Security assessment
The change clarifies VPN type but does not address a security vulnerability or add security features. It's a terminology update without explicit security implications.
Diff
diff --git a/iot-wireless/latest/developerguide/vpc-interface-endpoints.md b/iot-wireless/latest/developerguide/vpc-interface-endpoints.md index 39c762efc..af1b07ede 100644 --- a//iot-wireless/latest/developerguide/vpc-interface-endpoints.md +++ b//iot-wireless/latest/developerguide/vpc-interface-endpoints.md @@ -43 +43 @@ You can use control plane API endpoints to interact with the AWS IoT Wireless AP -Data plane API endpoints are LoRaWAN Network Server (LNS) and Configuration and Update Server (CUPS) endpoints that you can use to interact with the AWS IoT Core for LoRaWAN LNS and CUPS endpoints. These endpoints can be accessed from your LoRa gateways on premises by using AWS VPN or AWS Direct Connect. You get these endpoints when onboarding your gateway to AWS IoT Core for LoRaWAN. For more information, see [Add a gateway to AWS IoT Core for LoRaWAN](./lorawan-onboard-gateway-add.html). +Data plane API endpoints are LoRaWAN Network Server (LNS) and Configuration and Update Server (CUPS) endpoints that you can use to interact with the AWS IoT Core for LoRaWAN LNS and CUPS endpoints. These endpoints can be accessed from your LoRa gateways on premises by using Site-to-Site VPN or AWS Direct Connect. You get these endpoints when onboarding your gateway to AWS IoT Core for LoRaWAN. For more information, see [Add a gateway to AWS IoT Core for LoRaWAN](./lorawan-onboard-gateway-add.html).