AWS emr documentation change
Summary
Narrowed runtime role support scope to Lake Formation-enabled EMR Serverless
Security assessment
Updates supported environments without security implications. Focuses on feature availability rather than security controls.
Diff
diff --git a/emr/latest/ManagementGuide/emr-glue-views.md b/emr/latest/ManagementGuide/emr-glue-views.md index 085074fee..8298645a0 100644 --- a//emr/latest/ManagementGuide/emr-glue-views.md +++ b//emr/latest/ManagementGuide/emr-glue-views.md @@ -159 +159 @@ During this preview release, we recommend that you access views only from truste -After creating a Data Catalog view, you can now use an IAM role to query the view. The IAM role must have the `SELECT` permission on the Data Catalog view. You don't need to grant access to the underlying tables referred in the view. You must use this IAM role as a runtime role. You can access the view from an EMR cluster using a runtime role from Amazon EMR steps, EMR Studio, and SageMaker AI Studio. For more information about runtime roles, see [Runtime roles for Amazon EMR steps](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-steps-runtime-roles.html). +After creating a Data Catalog view, you can now use an IAM role to query the view. The IAM role must have the `SELECT` permission on the Data Catalog view. You don't need to grant access to the underlying tables referred in the view. You must use this IAM role as a runtime role. You can access the view from Lake Formation enabled EMR Serverless. For more information about runtime roles, see [Runtime roles for Amazon EMR steps](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-steps-runtime-roles.html).