Thank you @AWS Tuorials for the video. It is great as always. I have a question and a comment and thought you get your answer and view respectively: Question - With the redact/masking approach, if Glue Transformer uses redaction, does that imply we'll not be able to recover those redacted data unless we have the original data stored in an Archive or somewhere? Comments: Suppose we use "the Enrich data with Detection Result Option", we'll need to create a separate (custom) application/process to try and handle/redact those PII data as the Regulation may require. Therefore, would you say that it makes a lot more sense to leverage Lake formation to perform access control on the PII for both users and applications where some of the PII fields are identified using the Enrich data with Detection Result Option? By the way, Hope you are well and we are all Safe and Health.

Thank you for this awesome video, can we use custom own PII data(like gender coloumn) which is not available in the "PII to detect section" ?

Thanks for the awesome content. Whether it supports nested data?

Very informative video.. But it is using aws glue studio and as per my understanding, it is less popular because of Amazon pricing.

Thank you for providing the tips on errors to watch out for. One question is it possible to partially mask. 123-99-6765 --> XXX-XX-6765?