Closed Sevi7 closed 2 years ago
Hi @Sevi7,
Depending on the behavior you're expecting, there's 2 paths here:
If you want to create a cell filter, you probably want to use AWS::LakeFormation::DataCellsFilter instead. This will allow you to create a filter within your account and specify a row filter and/or column filter.
If you want to grant permissions on a cell filter, you would use AWS::LakeFormation::PrincipalPermissions. You'd be granting permissions on a cell filter that already exists, so you would only need some identifying data to specify it in the CFN template. For that reason, we don't allow information beyond what's specified in the DataCellsFilterResource as you mentioned above.
Thank you so much for your detailed explanation @aws-kaushal-partani. I misunderstood the documentation, it really makes sense now
Name of the resource
Other
Resource Name
AWS::LakeFormation::PrincipalPermissions
Issue Description
DataCellsFilterResource struct in CloudFormation has the following properties:
The issue is that there is no property to specify a row filter expression. I think there should be a property that recognizes this format: PartiQL support in row filter expressions.
Also ColumnNames and ColumnWildcard properties from TableWithColumnsResource are missing because cell filtering is when you include or exclude specific columns and also provide a row filter expression. Source: Data filters
Expected Behavior
A row filter property in DataCellsFilterResource struct that supports PartiQL format.
ColumnNames and ColumnWildcard from TableWithColumnsResource are also missing in DataCellsFilterResource.
With these three properties we would be able to establish cell-level security (cell filtering).
Useful documentation about Data filters that states the following:
According to the above we could also be missing a RowFilterResource in CloudFormation.
Observed Behavior
Missing properties in DataCellsFilterResource struct.
Test Cases
Test row filtering and cell filtering.
Other Details
No response