Study guide

12.5 SageMaker Unified Studio Domains, Projects & Catalog Governance

AWS Certified Data Engineer - Associate DEA-C01

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Streaming Data Ingestion

1.1 Kinesis Data Streams vs. Firehose Architecture & Partitioning 1.2 Amazon MSK (Managed Streaming for Apache Kafka) & Serverless Patterns 1.3 Event-Driven Streaming Ingestion with DynamoDB Streams & Lambda 1.4 Streaming Distribution, Replay & Processing State

2 Chapter 2: Batch Data Ingestion & Migration

2.1 AWS DMS (Database Migration Service) & Change Data Capture (CDC) 2.2 S3 Batch Operations & High-Throughput Bulk Data Ingestion 2.3 Hybrid Data Transfer with Snow Family & AWS DataSync 2.4 Application, API & Managed File Ingestion

3 Chapter 3: ETL Transformation with AWS Glue

3.1 AWS Glue Jobs, DynamicFrames & PySpark Transformations 3.2 Glue Crawlers, Data Catalog & Schema Evolution 3.3 Data Preparation & Quality Rules with AWS Glue DataBrew & Data Quality 3.4 Incremental Processing with AWS Glue Job Bookmarks & Partition Processing 3.5 Technical and Business Catalogs, Connections & Lineage

4 Chapter 4: Big Data Processing & Workflow Orchestration

4.1 Amazon EMR Cluster Architecture, Spark & Hadoop Ecosystem 4.2 EMR Serverless & Instance Selection (On-Demand vs. Spot Optimization) 4.3 Serverless Orchestration with AWS Step Functions 4.4 Airflow Pipeline Orchestration with Amazon MWAA 4.5 Containers, Lambda & Distributed Processing Performance 4.6 Data Engineering Code, IaC & CI/CD

5 Chapter 5: Object Storage & Data Lake Architecture

5.1 Amazon S3 Storage Classes, Lifecycle Policies & Cost Optimization 5.2 S3 Data Lake Partitioning, Bucketing & Layout Strategies 5.3 Efficient Columnar Formats: Parquet, ORC, and Avro Schema Design 5.4 S3 Performance Optimization, Multipart Uploads & Transfer Acceleration 5.5 Apache Iceberg, S3 Tables & Open Table Operations

6 Chapter 6: Data Warehousing with Amazon Redshift

6.1 Amazon Redshift Architecture, RA3 Nodes & Managed Storage 6.2 Redshift Data Modeling: Distribution Styles (KEY, EVEN, ALL) & Sort Keys 6.3 Loading & Unloading Data with COPY/UNLOAD & Redshift Spectrum

7 Chapter 7: NoSQL, Relational & Specialty Data Stores

7.1 Amazon DynamoDB Partition Keys, Global Secondary Indexes & Data Modeling 7.2 Amazon RDS & Aurora Operations, Read Replicas & Multi-AZ 7.3 Graph & Analytical Querying with Amazon Neptune, OpenSearch & Athena 7.4 Vector Stores, Indexes & LLM Data Processing

8 Chapter 8: Pipeline Operations, Monitoring & Observability

8.1 Monitoring Pipeline Health with Amazon CloudWatch Metrics & Logs 8.2 Event-Driven Alerting & Automation with EventBridge & CloudWatch Alarms 8.3 Centralized Audit Logging with AWS CloudTrail

9 Chapter 9: Troubleshooting, Data Quality & Performance Tuning

9.1 Diagnosing & Resolving AWS Glue, EMR & Lambda Execution Failures 9.2 Redshift & Athena Query Performance Tuning & Memory Management 9.3 Implementing Data Quality Frameworks & Automated Validation Checks 9.4 Visualization, Notebooks, SQL Analytics, Sampling & Skew

10 Chapter 10: High Availability, Backup & Cost Optimization

10.1 Disaster Recovery, Cross-Region Replication & Backup Strategies 10.2 Designing High Availability Architectures Across AWS Data Services 10.3 Cost Optimization & Resource Utilization across Analytics Workloads

11 Chapter 11: Data Security, Encryption & Identity Management

11.1 Fine-Grained Access Control with AWS IAM Policies, Roles & Conditions 11.2 Data Encryption at Rest & in Transit with AWS KMS & S3 Bucket Policies 11.3 Secure Credentials & Secrets Management with AWS Secrets Manager & Parameter Store 11.4 Private Network Connectivity & Isolation with AWS PrivateLink & VPC Endpoints

12 Chapter 12: Data Governance, Privacy & Compliance

12.1 Centralized Data Lake Governance & Access Control with AWS Lake Formation 12.2 Automated Sensitive Data Discovery & PII Protection with Amazon Macie 12.3 Configuration Auditing & Compliance Enforcement with AWS Config 12.4 Data Privacy, Sovereignty, Sharing & Retention Guardrails 12.5 SageMaker Unified Studio Domains, Projects & Catalog Governance

12.5 SageMaker Unified Studio Domains, Projects & Catalog Governance

Key Takeaways Explain This Topic AI

A SageMaker Unified Studio domain is the top collaboration and governance boundary; domain units organize business groups and delegate authorization-policy administration.

Projects are collaboration and access boundaries whose project profiles determine provisioned tools and resources; access normally flows through project execution roles rather than each human identity directly.

Catalog inventory is private to a project until its latest asset version is published, and consumers receive access through approved subscriptions or direct grants tied to enforceable data-plane permissions.

Managed services reduce infrastructure operations but do not remove customer responsibility for project membership, execution-role permissions, data classification, approvals, quality, cost, or lineage.

Last updated: August 2026

12.5 SageMaker Unified Studio Domains, Projects & Catalog Governance

Amazon SageMaker Unified Studio brings analytics, data, machine learning, and generative AI tools into a governed project experience. The exam focuses on the hierarchy and access path, not on treating Unified Studio as a replacement for IAM or Lake Formation.

Domain hierarchy

A domain is the top-level collaboration and governance boundary. It has a portal, identity configuration, root domain unit, and execution roles. Administrators make capabilities available to users and establish authorization policies.

Domain units organize assets and projects around business structures such as Finance, Risk, or Retail. A domain-unit owner can receive delegated authority to manage policies for that part of the organization. Domain units are not AWS accounts or VPC subnets; they are governance groupings inside the domain.

A useful hierarchy is:

Domain → domain unit → project → resources and catalog inventory

Place a project in the domain unit that owns its business purpose and policies. Moving a project or changing policy needs impact analysis because its resource and access context can change.

Projects and project profiles

A project is a collaboration boundary for one business use case. Project members share files, tools, data access, and resources. A project profile defines which tools and infrastructure are provisioned or made available when the project is created, potentially including Redshift, SageMaker AI, query, notebook, and other capabilities.

Do not grant every domain user membership in every project. Assign project owners and members from job function, separate development and production duties, and review membership. The project has an execution role used by tools to query and process data. Human permission to open the portal and data-plane permission for that execution role are separate layers.

Managed versus unmanaged responsibility

Unified Studio is managed: AWS operates substantial portal and service infrastructure. Managed does not mean ungoverned. Customers still configure identities, project memberships, authorization policies, VPC access, KMS choices, execution roles, Lake Formation integration, resource limits, and data approvals.

Likewise, a self-managed Spark cluster offers host and framework control but requires patching and capacity operations; a managed or serverless service reduces those duties. Choose from functional and control requirements, then secure the controls that remain yours.

Inventory, publish, and subscribe

A producer first brings an asset into a project's inventory . Inventory is visible to that project's members. The producer enriches it with business names, descriptions, glossary terms, metadata forms, ownership, and quality context.

Publishing the latest inventory asset version makes it discoverable in the SageMaker Catalog to domain users. If the producer later updates the inventory, the newest version must be published again; discovery should not silently expose an unreviewed draft.

A consumer searches the catalog and requests a subscription . After approval, the system grants access to the consumer project's execution role, commonly through Lake Formation for governed tables. The individual who clicks Request is not necessarily the principal that reads the data.

This distinction explains common failures:

Catalog asset is visible, but the execution role lacks Lake Formation or IAM access.

Lake Formation grant exists, but the project tool uses a different execution role.

Subscription is revoked in catalog workflow, but a separate broad S3 permission still bypasses it.

User leaves the team, but stale project membership remains.

Authorization policy design

Use domain-unit authorization policies to delegate only the needed actions, such as creating projects from approved profiles. Project profiles should embed secure defaults: encryption, logging, private connectivity, bounded compute, and approved resource roles.

Separate these roles:

  • Role Responsibility
  • Domain administrator Domain-wide identity and platform configuration
  • Domain-unit owner Delegated policies for a business unit
  • Project owner Membership, resources, and business-use boundary
  • Data owner or steward Asset meaning, publication, subscription approval
  • Project member Uses approved tools and data for the project purpose

Avoid one execution role shared by unrelated projects; it blurs attribution and can make one project's grant available to another.

End-to-end governed query

For a project member to query a catalog table:

The person authenticates and is authorized to enter the project.

The table is inventoried, curated, and published.

A subscription or direct grant authorizes the project.

Lake Formation and IAM grant the project's execution role the required metadata and data access.

The query tool assumes or uses that role.

CloudTrail, query logs, and catalog history provide evidence.

Network reachability and KMS decrypt permission must also succeed. Authorization does not repair a missing VPC route, and connectivity does not grant table access.

Operational governance

Track project owner, member review date, profile version, execution role, active subscriptions, resource cost, and last activity. On project closure, revoke shares, preserve required evidence, expire temporary resources, and delete derived data according to retention policy.

Use lineage and quality results in the catalog so consumers can judge fitness. A technically queryable table without ownership, freshness, or business definition should not be promoted as a trusted asset.