Hi - I used a simple .xlsx file with some fake first/last name and fake ssn. Created a job and it was able to identify as below
The object contains personal information such as first or last names, addresses, or identification numbers.
Also review some of the requirements mentioned here https://docs.aws.amazon.com/macie/latest/user/data-classification.html
You can also you can monitor and analyze specific events that occur as a job progresses https://docs.aws.amazon.com/macie/latest/user/discovery-jobs-monitor-cw-logs.html
Could you provide the sample file in the form of comma separated values in a comment?
It's worth noting that Macie does have some validation built in to filter out fake numbers. For example, if you entered 123-45-6789 or 000-00-0000 as the SSN, it wouldn't trigger.
Relevant content
- asked a year ago
- asked 9 months ago
- Accepted Answerasked 5 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
Hi Nitin thanks for your response. Could you share with me the excel doc you used and what the data looked like? Thank you for those links I have seen those as I have been investigating this problem. The cloudwatch logs just say that the scan was running and was completed but does not give me any insight into why Macie cant pick up on these sensitive data types.