AWS redshift documentation change
Summary
Added database/schema qualification syntax and federated permissions documentation
Security assessment
The change extends policy attachment syntax to support cross-database operations and documents federated permissions usage, enhancing security documentation without patching vulnerabilities.
Diff
diff --git a/redshift/latest/dg/r_ATTACH_MASKING_POLICY.md b/redshift/latest/dg/r_ATTACH_MASKING_POLICY.md index 16efebdb9..5a8a910c8 100644 --- a//redshift/latest/dg/r_ATTACH_MASKING_POLICY.md +++ b//redshift/latest/dg/r_ATTACH_MASKING_POLICY.md @@ -18,5 +18,10 @@ Superusers and users or roles that have the sys:secadmin role can attach a maski - ATTACH MASKING POLICY _policy_name_ - ON { _relation_name_ } - ( {_output_columns_names_ | _output_path_} ) [ USING ( {_input_column_names_ | _input_path_ )} ] - TO { _user_name_ | ROLE _role_name_ | PUBLIC } - [ PRIORITY _priority_ ]; + ATTACH MASKING POLICY + { + _policy_name_ ON _relation_name_ + | _database_name_._policy_name_ ON _database_name_._schema_name_._relation_name_ + } + ( { output_column_names | output_path } ) + [ USING ( { input_column_names | input_path } ) ] + TO { user_name | ROLE role_name | PUBLIC } + [ PRIORITY priority ]; + @@ -30,0 +36,10 @@ The name of the masking policy to attach. +database_name + + +The name of the database where the policy and the relation are created. The policy and the relation needs to be on the same database. The database can be the connected database or a database that supports Amazon Redshift federated permissions. + +schema_name + + +The name of the schema the relation belongs to. + @@ -85,0 +101,2 @@ You can't apply a policy to a column with the same priority as another policy at +For the usage of ATTACH MASKING 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). +