3 ms·

At my last job we had a lot of data in S3 queried using the data tooling like Athena or EMR. This was useful to a lot of teams in the org but the downside was

At my last job we had a lot of data in S3 queried using the data tooling like Athena or EMR. This was useful to a lot of teams in the org but the downside was trying to lockdown certain fields like IP address to people who needed access to that data for support/operational reasons. Amazon did come up with some IAM/grouping policy things but these were a bit clunky from what I recall. I wonder if something like this would have made it a bit more flexible to allow us to redact the IP address on the fly EDIT: although I wonder about the performance implication of this for the "big data" use cases

JshWright 6y ago
> like Athena or EMR Despite being familiar with both of those individually, the combination of the two words side by side switched me into an entirely different context that took several tries to escape from... https://en.wikipedia.org/wiki/Athenahealth https://en.wikipedia.org/wiki/Athenahealth https://en.wikipedia.org/wiki/Electronic_medical_record https://en.wikipedia.org/wiki/Electronic_medical_record
minaguib 6y ago
If I understand things correctly, the modern way to to read-time masking in the AWS ecosystem is to introduce AWS Lake Formation ( https://aws.amazon.com/lake-formation/ https://aws.amazon.com/lake-formation/ ) as the abstraction layer between Athena and S3.