AWS emr medium security documentation change
Summary
Added known issues: HBase table creation failure with Glue catalog and Tez UI HTTPS misconfiguration when in-transit encryption is enabled
Security assessment
Tez UI misconfiguration undermines in-transit encryption by using HTTP, requiring HTTPS configuration to prevent potential data exposure.
Diff
diff --git a/emr/latest/ReleaseGuide/emr-770-release.md b/emr/latest/ReleaseGuide/emr-770-release.md index 0da050553..a949603f6 100644 --- a//emr/latest/ReleaseGuide/emr-770-release.md +++ b//emr/latest/ReleaseGuide/emr-770-release.md @@ -85 +85,3 @@ The following release notes include information for Amazon EMR release 7.7.0. - * Not applicable for this release. + * **HBase table creation in Hive with Glue catalog** – From EMR-7.3.0 to EMR-7.10.0, there is a bug due to Hive Iceberg integration, which causes HBase table creation in Hive to fail when Glue Data Catalog is used as the metastore. Please reach out to the AWS support team if you encounter this issue. + + * **Tez UI** – From EMR-7.3 to EMR-7.10, there is a bug where accessing Tez UI through YARN Resource Manager Web UI fails when in-transit encryption is enabled. This occurs because YARN proxy attempts to use HTTP protocol while Tez UI requires HTTPS. Please modify the `tez.tez-ui.history-url.base` configuration in `tez-site` from `http` to `https` to resolve this issue.