AWS Lake Formation
#166 · Level 3 · Modern architecture · Data and analyticsConcept
Section titled “Concept”With AWS Lake Formation you can build a data lake and control, from one place, who can see which data. It works on top of the AWS Glue Data Catalog, which holds the descriptions of the data tables. Permissions can be given at the level of a database, a table, or even specific columns or rows. Services like Athena, Redshift and EMR follow these permissions when they read data. Data can also be shared with other AWS accounts in a controlled way.
Simple example
Section titled “Simple example”A warehouse manager — decides which goods go on which shelf, and which worker can touch which shelf.
Why it’s needed
Section titled “Why it’s needed”If everyone has permission to see all the data in a data lake, private information can leak.
Where it’s used
Section titled “Where it’s used”Department-based data permissions, hiding specific columns or rows.
Azure equivalent
Section titled “Azure equivalent”Microsoft Purview / Unity Catalog on Azure Databricks
Learn more
Section titled “Learn more”For details and the latest information, see the official documentation: