AWS IAM documentation change
Summary
Added empty JSON blocks and section breaks in permissions boundary examples
Security assessment
Formatting changes without completing permissions boundary examples. No security features or vulnerabilities addressed.
Diff
diff --git a/IAM/latest/UserGuide/access_policies_boundaries.md b/IAM/latest/UserGuide/access_policies_boundaries.md index 0bcc40e62..3c4f44575 100644 --- a//IAM/latest/UserGuide/access_policies_boundaries.md +++ b//IAM/latest/UserGuide/access_policies_boundaries.md @@ -20,0 +21,6 @@ For example, assume that the IAM user named `Shirley` should be allowed to manag +JSON + + +**** + + @@ -38,0 +46,6 @@ When you use a policy to set the permissions boundary for a user, it limits the +JSON + + +**** + + @@ -132,0 +147,6 @@ To enforce these rules, María completes the following tasks, for which details +JSON + + +**** + + @@ -203,0 +225,6 @@ Each statement serves a different purpose: +JSON + + +**** + + @@ -310,0 +339,6 @@ María then assigns the `DelegatedUserBoundary` policy [as the permissions bound +JSON + + +**** + +