AWS iot: Clarify trailing-dot domain matching for iot:DomainName policy variable
Summary
Adds guidance that condition values match exact text, so to fully deny a domain you must list both the domain name and the domain name with a trailing dot; updates the deny-policy example wording accordingly.
Security assessment
The change documents that a deny policy on iot:DomainName must include the trailing-dot variant, otherwise a device could connect to the domain via the dotted form and bypass the intended deny. This is authorization-policy hardening guidance rather than a fix for a named vulnerability.
Evidence
A condition value matches the exact text you specify. To fully deny a domain, include both the domain name and the domain name with a trailing dot.
Diff
diff --git a/iot/latest/developerguide/basic-policy-variables.md b/iot/latest/developerguide/basic-policy-variables.md index a24a974..69baf79 100644 --- a//iot/latest/developerguide/basic-policy-variables.md +++ b//iot/latest/developerguide/basic-policy-variables.md @@ -111,0 +112,2 @@ You can add the `iot:DomainName` policy variable to restrict which domains are a +A condition value matches the exact text you specify. To fully deny a domain, include both the domain name and the domain name with a trailing dot. + @@ -136 +138 @@ The following policy allows devices to connect to the specified domain. -The following policy denies devices to connect to the specified domain. +The following policy denies devices access to the specified domain. The policy lists the domain name both with and without a trailing dot to fully deny the domain.