AWS security-lake documentation change
Summary
Added JSON section headers and formatting dividers in policy examples
Security assessment
The changes are purely structural/documentation formatting improvements without modifying actual policy content or security context. No security implications identified.
Diff
diff --git a/security-lake/latest/userguide/security_iam_id-based-policy-examples.md b/security-lake/latest/userguide/security_iam_id-based-policy-examples.md index 9388a1b02..4a4c5ea46 100644 --- a//security-lake/latest/userguide/security_iam_id-based-policy-examples.md +++ b//security-lake/latest/userguide/security_iam_id-based-policy-examples.md @@ -129,0 +130,6 @@ This example shows how you might create a policy that allows a user of an AWS Or +JSON + + +**** + + @@ -148,0 +156,6 @@ In identity-based policies, you can use conditions to control access to Security +JSON + + +**** + +