AWS lake-formation documentation change
Summary
Removed redundant JSON policy examples from inline policy sections.
Security assessment
This is a documentation cleanup to reduce redundancy. No security-related content was added or modified.
Diff
diff --git a/lake-formation/latest/dg/permissions-reference.md b/lake-formation/latest/dg/permissions-reference.md index 16ce72ac4..dfc393173 100644 --- a//lake-formation/latest/dg/permissions-reference.md +++ b//lake-formation/latest/dg/permissions-reference.md @@ -372,3 +371,0 @@ Inline policy (for creating the Lake Formation service-linked role) | -JSON - - @@ -398,3 +394,0 @@ JSON -JSON - - @@ -428,3 +421,0 @@ Inline policy (basic) | -JSON - - @@ -499,3 +489,0 @@ Inline policy (basic) | -JSON - - @@ -539,3 +526,0 @@ Inline policy (for operations on governed tables, including operations within tr -JSON - - @@ -570,3 +554,0 @@ Inline policy (for metadata access control using the Lake Formation tag-based ac -JSON - - @@ -599,3 +580,0 @@ Inline policy (passrole policy for the workflow role) | -JSON - - @@ -657,3 +635,0 @@ Inline policy (basic) | -JSON - - @@ -717,3 +692,0 @@ Inline policy (passrole policy for the workflow role) | -JSON - - @@ -743,3 +715,0 @@ Inline policy (for ingesting data outside the data lake, for example, AWS CloudT -JSON - -