AWS IAM documentation change
Summary
Added empty JSON blocks and dividers in cross-account access examples
Security assessment
Structural formatting changes without completing cross-account security examples. No evidence of security fixes.
Diff
diff --git a/IAM/latest/UserGuide/access_policies-cross-account-resource-access.md b/IAM/latest/UserGuide/access_policies-cross-account-resource-access.md index 2b3dcaea9..85aed2d09 100644 --- a//IAM/latest/UserGuide/access_policies-cross-account-resource-access.md +++ b//IAM/latest/UserGuide/access_policies-cross-account-resource-access.md @@ -34,0 +35,6 @@ Let’s take a look at the overall process as it applies to APN Partner software +JSON + + +**** + + @@ -49,0 +57,6 @@ Let’s take a look at the overall process as it applies to APN Partner software +JSON + + +**** + + @@ -118,0 +133,6 @@ For example, assume that you manage `AccountA` and `AccountB`. In AccountA, you +JSON + + +**** + + @@ -137,0 +159,6 @@ The AccountB root user has all of the permissions that are granted to the accoun +JSON + + +**** + +