AWS emr documentation change
Summary
Removed reference to SageMaker Unified Studio for configuring Lake Formation with full table access
Security assessment
This is a documentation clarification without security implications. The change removes a specific implementation detail (SageMaker Unified Studio) but doesn't alter security controls or requirements.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/lake-formation-unfiltered-access.md b/emr/latest/EMR-Serverless-UserGuide/lake-formation-unfiltered-access.md index 0fa55f2d9..eab9fbfbc 100644 --- a//emr/latest/EMR-Serverless-UserGuide/lake-formation-unfiltered-access.md +++ b//emr/latest/EMR-Serverless-UserGuide/lake-formation-unfiltered-access.md @@ -9 +9 @@ Using Lake Formation with full table access -With Amazon EMR releases 7.8.0 and higher, you can leverage AWS Lake Formation with Glue Data Catalog where the job runtime role has full table permissions without the limitations of fine-grained access control. This capability allows you to read and write to tables that are protected by Lake Formation from your EMR Serverless Spark batch and interactive jobs. To configure AWS Lake Formation with full table access for interactive sessions, use Sage Maker Unified Studio. See the following sections to learn more about Lake Formation and how to use it with EMR Serverless. +With Amazon EMR releases 7.8.0 and higher, you can leverage AWS Lake Formation with Glue Data Catalog where the job runtime role has full table permissions without the limitations of fine-grained access control. This capability allows you to read and write to tables that are protected by Lake Formation from your EMR Serverless Spark batch and interactive jobs. See the following sections to learn more about Lake Formation and how to use it with EMR Serverless.