AWS lake-formation documentation change
Summary
Added line continuations (backslashes) to CLI command formatting for readability
Security assessment
The change is purely syntactic, improving command readability without altering security logic or documentation.
Diff
diff --git a/lake-formation/latest/dg/abac-granting-permissions.md b/lake-formation/latest/dg/abac-granting-permissions.md index 00a8d18a2..d251370d3 100644 --- a//lake-formation/latest/dg/abac-granting-permissions.md +++ b//lake-formation/latest/dg/abac-granting-permissions.md @@ -48,5 +48,5 @@ This condition checks if the IAM principal has a `department` tag, and the `depa - --principal '{"DataLakePrincipalIdentifier": "111122223333:IAMPrincipals"}' - --resource '{"Database": {"CatalogId": 111122223333, "Name": "abac-db"}}' - --permissions ALL - --condition '{"Expression": "context.iam.principalTags.hasTag(\"department\") - && context.iam.principalTags.getTag(\"department\") == \"sales\""' + --principal '{"DataLakePrincipalIdentifier": "111122223333:IAMPrincipals"}' \ + --resource '{"Database": {"CatalogId": 111122223333, "Name": "abac-db"}}' \ + --permissions ALL \ + --condition '{"Expression": "context.iam.principalTags.hasTag(\"department\") \ + && context.iam.principalTags.getTag(\"department\") == \"sales\""}'