AWS iot: IoT policy example: add trailing-dot domain to deny condition
Summary
The example deny policy for iot:DomainName was changed from a single string value to an array that also includes the same domain with a trailing dot, so the deny condition matches both FQDN forms.
Security assessment
The example policy denies devices from connecting to a specific domain. Adding the trailing-dot variant of the domain closes a known policy-bypass pattern where a client connects using an FQDN with a trailing dot (e.g. 'host.') that does not string-match the condition value, evading the deny rule. This is an authorization/policy-enforcement hardening in the documented example.
Evidence
+ "d1234567890abcdefghij-ats.iot.us-east-1.amazonaws.com."
Diff
diff --git a/iot/latest/developerguide/basic-policy-variables.md b/iot/latest/developerguide/basic-policy-variables.md index 60a1b27..a24a974 100644 --- a//iot/latest/developerguide/basic-policy-variables.md +++ b//iot/latest/developerguide/basic-policy-variables.md @@ -153 +153,4 @@ The following policy denies devices to connect to the specified domain. - "iot:DomainName": "d1234567890abcdefghij-ats.iot.us-east-1.amazonaws.com" + "iot:DomainName": [ + "d1234567890abcdefghij-ats.iot.us-east-1.amazonaws.com", + "d1234567890abcdefghij-ats.iot.us-east-1.amazonaws.com." + ]