AWS emr documentation change
Summary
Removed mention of using AWS Lake Formation for fine-grained permissions in Trino/AWS Glue Data Catalog documentation
Security assessment
Removal of access control reference appears to be documentation cleanup rather than addressing a security issue
Diff
diff --git a/emr/latest/ReleaseGuide/emr-trino-config.md b/emr/latest/ReleaseGuide/emr-trino-config.md index a71aca19b..a4a039ecc 100644 --- a//emr/latest/ReleaseGuide/emr-trino-config.md +++ b//emr/latest/ReleaseGuide/emr-trino-config.md @@ -22 +22 @@ Configuring connectors for TrinoMonitoring -It's important and useful to understand that you can configure AWS Glue Data Catalog as your Hive metastore when running queries with Trino. When you do this, you can add fine-grained permissions on the data sources using AWS Lake Formation. For additional information, including steps to set up a cluster with a Hive metastore, see [Using the AWS Glue Data Catalog as the metastore for Hive](https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-hive-metastore-glue.html). +It's important and useful to understand that you can configure AWS Glue Data Catalog as your Hive metastore when running queries with Trino. For additional information, including steps to set up a cluster with a Hive metastore, see [Using the AWS Glue Data Catalog as the metastore for Hive](https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-hive-metastore-glue.html).