Apologies for the late response due to my summer break. Please check if glue database is configure to use only lake formation based security. if It is supports backward compatibility for IAM Role based access then TBAC might not work.
@@AWSTutorialsOnline also there is one more use case only a single user group will be able to see the PI columns but the other user group won't be able to see it. thanks
Is there any way to combine the tags with row access? as I would like for example to create a user to access dojodb.custumers only where country is USA
Thank you for your time! That was very helpful.
You're very welcome!
Good one !
Thanks for listening
What could be possible reasons if TBAC is not working correctly?
Apologies for the late response due to my summer break.
Please check if glue database is configure to use only lake formation based security. if It is supports backward compatibility for IAM Role based access then TBAC might not work.
thanks for the demo
Welcome
Is row level access can be applied using tag based?
thanks for the great video, could you please create some video how to manage PI info in aws data lake
Apologies for the late response due to my summer break.
Do you want to identify PI information or want to secure it like encrypt / mask?
@@AWSTutorialsOnline I want to mask the encrypt / mask information so that when user will query it they will be able to see the no - PI columns
@@AWSTutorialsOnline also there is one more use case only a single user group will be able to see the PI columns but the other user group won't be able to see it.
thanks
this is good, but i'm looking for Tag based control for IAM role logged as CD roles to segregate access users using same role
Apologies for the late response due to my summer break.
Can you please elaborate the use case?
Is there any way to combine the tags with row access? as I would like for example to create a user to access dojodb.custumers only where country is USA
Even I am also facing the same challenge. Not sure how to create row based filter when using tag based access control
@@shaktisingh-lu3dm you cannot limit that on LF level.