AWS emr documentation change
Summary
Renamed section and updated terminology from 'full table access' to 'unfiltered access', removed specific implementation details about Glue Data Catalog views
Security assessment
Changes are primarily terminological (e.g., 'unfiltered access' vs 'full table access') and structural (section renaming). No specific security vulnerabilities or new security features are introduced in these changes.
Diff
diff --git a/emr/latest/ManagementGuide/lake-formation-unfiltered-access-ec2-container.md b/emr/latest/ManagementGuide/lake-formation-unfiltered-access-ec2-container.md index 8f56f26ec..99e4f6fd8 100644 --- a//emr/latest/ManagementGuide/lake-formation-unfiltered-access-ec2-container.md +++ b//emr/latest/ManagementGuide/lake-formation-unfiltered-access-ec2-container.md @@ -5 +5 @@ -# Using a Lake Formation job runtime role with full table access +# Full table access with Lake Formation @@ -7 +7 @@ -The topics in this section cover how you can access Lake Formation protected Glue Data catalog tables from EMR Spark jobs or interactive sessions with full table access. +The topic in this section cover how you can access Lake Formation protected Glue Data catalog tables from EMR Spark jobs or interactive sessions with unfiltered access. @@ -15 +15 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Working with Glue Data Catalog views in Amazon EMR +Considerations @@ -17 +17 @@ Working with Glue Data Catalog views in Amazon EMR -Lake Formation unfiltered access for EMR on EC2 +Lake Formation unfiltered access