AWS quicksuite documentation change
Summary
Rephrased instructions for creating row-level security rules
Security assessment
The change clarifies documentation syntax but does not alter security functionality or address a specific security issue.
Diff
diff --git a/quicksuite/latest/userguide/restrict-access-to-a-data-set-using-row-level-security.md b/quicksuite/latest/userguide/restrict-access-to-a-data-set-using-row-level-security.md index bf8ee79be..41f32ea9a 100644 --- a//quicksuite/latest/userguide/restrict-access-to-a-data-set-using-row-level-security.md +++ b//quicksuite/latest/userguide/restrict-access-to-a-data-set-using-row-level-security.md @@ -18 +18 @@ When applying SPICE datasets to row-level security, each field in the dataset ca -To do this, you create a query or file that has one column named `UserName`, `GroupName`, or both. Or you can create a query or file that has one column named `UserARN`, `GroupARN`, or both. You can think of this as _adding a rule_ for that user or group. Then you can add one column to the query or file for each field that you want to grant or restrict access to. For each user or group name that you add, you add the values for each field. You can use NULL (no value) to mean all values. To see examples of dataset rules, see Creating dataset rules for row-level security. +To do this, you create a query or file with one column for user or group identification. You can use either `UserName` and `GroupName`, or alternatively `UserARN` and `GroupARN`. You can think of this as _adding a rule_ for that user or group. Then you can add one column to the query or file for each field that you want to grant or restrict access to. For each user or group name that you add, you add the values for each field. You can use NULL (no value) to mean all values. To see examples of dataset rules, see Creating dataset rules for row-level security.