Unity Catalog - Governance from day one

The governance layer sitting on top of every table from Section 5: the metastore/catalog/schema hierarchy, connecting that hierarchy to real S3 storage via storage credentials and external locations, identity (users, groups, service principals), and the full GRANT permissions model – built hands-on into a realistic dev/uat/prod structure with row- and column-level controls at the end. “Governance from day one” is the point: bolting this on after pipelines already exist is far harder than designing it first, which is why this section comes before any actual pipeline- building sections.

flowchart TD
    MS[Metastore] --> C[Catalog<br/>dev / uat / prod]
    C --> S[Schema]
    S --> T[Table / Volume]
    SC[Storage Credential] --> EL[External Location]
    EL --> C
    ID[Users / Groups /<br/>Service Principals] -->|GRANT| C
    ID -->|GRANT| S
    ID -->|GRANT| T

Lectures

#	Lecture	Est. Read
1	Why Unity Catalog - Architecture	13 min read
2	Implementing Unity Catalog Architecture	9 min read
3	Catalogs, External Locations and Storage Credentials	15 min read
4	Identity in Unity Catalog - Users, Groups, and Service Principals	12 min read
5	Implementing Users, Groups, and Access Control	13 min read
6	Unity Catalog Permissions Model - GRANT	15 min read
7	Implementing Unity Catalog Permission for Catalog and Schema	12 min read
8	Unity Catalog Permissions for Tables and Volumns	11 min read
9	Check Your Knowledge	Quiz

| ← Previous: Check Your Knowledge | Next: Why Unity Catalog - Architecture → | |:—|—:|

Unity Catalog - Governance from day one

Lectures

Table of contents