AWS redshift high security documentation change
Summary
Corrected required permission from 'TRUNCATE TABLE' to 'TRUNCATE'
Security assessment
Fixes documentation error about required permissions. Incorrect permission naming could lead to overprivileged access if users followed previous guidance.
Diff
diff --git a/redshift/latest/dg/r_TRUNCATE.md b/redshift/latest/dg/r_TRUNCATE.md index 5336647bd..23f89b379 100644 --- a//redshift/latest/dg/r_TRUNCATE.md +++ b//redshift/latest/dg/r_TRUNCATE.md @@ -9 +9 @@ SyntaxParametersUsage NotesExamples -Deletes all of the rows from a table without doing a table scan: this operation is a faster alternative to an unqualified DELETE operation. To run a TRUNCATE command, you must be have the TRUNCATE TABLE permission, be the owner of the table, or a superuser. To grant permissions to truncate a table, use the [GRANT](./r_GRANT.html) command. +Deletes all of the rows from a table without doing a table scan: this operation is a faster alternative to an unqualified DELETE operation. To run a TRUNCATE command, you must have the TRUNCATE permission for the table, be the owner of the table, or be a superuser. To grant permissions to truncate a table, use the [GRANT](./r_GRANT.html) command.