AWS iot: Clarify IPv6 support and network access for HTTPS rule action
Summary
Updated the endpoint description to clarify that IPv6 addresses aren't supported in place of a hostname and added guidance to use a hostname with AAAA records for IPv6, plus a link to network access documentation.
Security assessment
The change documents network connectivity behavior (IPv4 vs IPv6) for the HTTPS rule action endpoint. It is network-adjacent guidance but does not address a specific vulnerability, credential, or authorization concern.
Evidence
IPv6 addresses aren't supported in place of a hostname. To receive data over IPv6, use a hostname that publishes AAAA records and no A records.
Diff
diff --git a/iot/latest/developerguide/https-rule-action.md b/iot/latest/developerguide/https-rule-action.md index 319bf5b3e..d382b14b8 100644 --- a//iot/latest/developerguide/https-rule-action.md +++ b//iot/latest/developerguide/https-rule-action.md @@ -29 +29,3 @@ When you create an AWS IoT rule with this action, you must specify the following -The HTTPS endpoint where the message is sent using the HTTP POST method. If you use an IP address in place of a hostname, it must be an IPv4 address. IPv6 addresses are not supported. +The HTTPS endpoint where the message is sent using the HTTP POST method. If you use an IP address in place of a hostname, it must be an IPv4 address. IPv6 addresses aren't supported in place of a hostname. To receive data over IPv6, use a hostname that publishes AAAA records and no A records. + +For information about the IP version that the rules engine uses to connect to your endpoint, see [Network access](./http-action-destination.html#http-action-destination-network-access).