AWS emr: Fix broken link to TLS 1.2 requirement blog
Summary
Corrected a URL with an extra slash in the link to the AWS Security Blog about TLS 1.2 enforcement.
Security assessment
The change fixes a documentation link but does not modify security guidance or address vulnerabilities.
Evidence
+If you use Amazon EMR 3.10 or lower, we recommend that you immediately test and migrate your workloads to the latest Amazon EMR release. For more information, see the [AWS Security Blog](https://aws.amazon.com/blogs/security/tls-1-2-required-for-aws-endpoints/).
Diff
diff --git a/emr/latest/ReleaseGuide/emr-release-3x.md b/emr/latest/ReleaseGuide/emr-release-3x.md index 1a8513843..963d3e46e 100644 --- a//emr/latest/ReleaseGuide/emr-release-3x.md +++ b//emr/latest/ReleaseGuide/emr-release-3x.md @@ -13 +13 @@ AWS is updating the TLS configuration for all AWS API endpoints to a minimum ver -If you use Amazon EMR 3.10 or lower, we recommend that you immediately test and migrate your workloads to the latest Amazon EMR release. For more information, see the [AWS Security Blog](https://aws.amazon.com/blogs//security/tls-1-2-required-for-aws-endpoints/). +If you use Amazon EMR 3.10 or lower, we recommend that you immediately test and migrate your workloads to the latest Amazon EMR release. For more information, see the [AWS Security Blog](https://aws.amazon.com/blogs/security/tls-1-2-required-for-aws-endpoints/).