AWS emr documentation change
Summary
Fixed a minor grammatical error in the sentence about wildcard certificates in encryption artifacts
Security assessment
This change only corrects a grammatical error ('in the for the domain' to 'for the domain') in existing security documentation about SSL/TLS certificate configuration. It does not introduce new security information or address any security vulnerability.
Diff
diff --git a/emr/latest/ManagementGuide/emr-encryption-enable.md b/emr/latest/ManagementGuide/emr-encryption-enable.md index 2c21dafef..844e29a1f 100644 --- a//emr/latest/ManagementGuide/emr-encryption-enable.md +++ b//emr/latest/ManagementGuide/emr-encryption-enable.md @@ -177 +177 @@ You likely want to configure the private key PEM file to be a wildcard certifica -If the provided PEM file in the encryption artifact doesn't have a wildcard character in the for the domain in the common name, you must change the value of `hadoop.ssl.hostname.verifier` to `ALLOW_ALL`. To do so in Amazon EMR releases 7.3.0 and higher, add the `core-site` classification when you submit configurations to a cluster. In releases lower than 7.3.0, add the configuration `"hadoop.ssl.hostname.verifier": "ALLOW_ALL"` directly into the `core-site.xml` file. This change is required because the default hostname verifier requires a hostname without the wildcard because all hosts in the cluster use it. For more information about EMR cluster configuration within an Amazon VPC, see [Configure networking in a VPC for Amazon EMR](./emr-plan-vpc-subnet.html). +If the provided PEM file in the encryption artifact doesn't have a wildcard character for the domain in the common name, you must change the value of `hadoop.ssl.hostname.verifier` to `ALLOW_ALL`. To do so in Amazon EMR releases 7.3.0 and higher, add the `core-site` classification when you submit configurations to a cluster. In releases lower than 7.3.0, add the configuration `"hadoop.ssl.hostname.verifier": "ALLOW_ALL"` directly into the `core-site.xml` file. This change is required because the default hostname verifier requires a hostname without the wildcard because all hosts in the cluster use it. For more information about EMR cluster configuration within an Amazon VPC, see [Configure networking in a VPC for Amazon EMR](./emr-plan-vpc-subnet.html).