AWS emr documentation change
Summary
Changed wording from 'you can enable' to 'enable' in mutual-TLS encryption documentation
Security assessment
The change is a grammatical adjustment rather than introducing new security content. The mutual-TLS encryption feature itself is security-related, but this specific edit only modifies instructional phrasing without altering security implications.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/interworker-encryption.md b/emr/latest/EMR-Serverless-UserGuide/interworker-encryption.md index 3b1e8d12b..90467ff7a 100644 --- a//emr/latest/EMR-Serverless-UserGuide/interworker-encryption.md +++ b//emr/latest/EMR-Serverless-UserGuide/interworker-encryption.md @@ -9 +9 @@ Enabling mutual-TLS encryption on EMR Serverless -With Amazon EMR versions 6.15.0 and higher, you can enable mutual-TLS encrypted communication between workers in your Spark job runs. When enabled, EMR Serverless automatically generates and distributes a unique certificate for each worker provisioned under your job runs. When these workers communicate to exchange control messages or transfer shuffle data, they establish a mutual TLS connection and use the configured certificates to verify the identity of each other. If a worker is unable to verify another certificate, the TLS handshake fails, and EMR Serverless aborts the connection between them. +With Amazon EMR versions 6.15.0 and higher, enable mutual-TLS encrypted communication between workers in your Spark job runs. When enabled, EMR Serverless automatically generates and distributes a unique certificate for each worker provisioned under your job runs. When these workers communicate to exchange control messages or transfer shuffle data, they establish a mutual TLS connection and use the configured certificates to verify the identity of each other. If a worker is unable to verify another certificate, the TLS handshake fails, and EMR Serverless aborts the connection between them.