AWS redshift documentation change
Summary
Added database qualification syntax and federated permissions reference
Security assessment
Extends RLS policy drop syntax to support federated environments. Updates security documentation without evidence of vulnerability remediation.
Diff
diff --git a/redshift/latest/dg/r_DROP_RLS_POLICY.md b/redshift/latest/dg/r_DROP_RLS_POLICY.md index 8fbd937df..cc011098f 100644 --- a//redshift/latest/dg/r_DROP_RLS_POLICY.md +++ b//redshift/latest/dg/r_DROP_RLS_POLICY.md @@ -18 +18,3 @@ Superusers and users or roles that have the sys:secadmin role can drop a policy. - DROP RLS POLICY [ IF EXISTS ] _policy_name_ [ CASCADE | RESTRICT ] + DROP RLS POLICY [ IF EXISTS ] + { policy_name | database_name.policy_name } + [ CASCADE | RESTRICT ] @@ -31,0 +34,5 @@ The name of the policy. +database_name + + +The name of the database from where the policy to be dropped. The database can be the connected database or a database that supports Amazon Redshift federated permissions. + @@ -41,0 +49,2 @@ A clause that indicates not to drop the policy when it is attached to some table +For the usage of DROP RLS POLICY on Amazon Redshift Federated Permissions Catalog, see [ Managing access control with Amazon Redshift federated permissions](https://docs.aws.amazon.com/redshift/latest/dg/federated-permissions-managing-access.html). +