AWS emr documentation change
Summary
Updated FIPS 140-2 reference to FIPS 140 for cryptographic modules
Security assessment
The change updates compliance documentation regarding encryption standards but does not indicate a security vulnerability. FIPS validation updates relate to security features but are not tied to a specific security issue.
Diff
diff --git a/emr/latest/ManagementGuide/emr-studio-considerations.md b/emr/latest/ManagementGuide/emr-studio-considerations.md index dbaddddb3..317b1d138 100644 --- a/emr/latest/ManagementGuide/emr-studio-considerations.md +++ b/emr/latest/ManagementGuide/emr-studio-considerations.md @@ -113 +113 @@ Consider the following when you work with EMR Studio: - * Amazon EMR Studio Workspaces and Persistent UI endpoints use FIPS 140-2 validated cryptographic modules for encryption-in-transit, which enables easier adoption of the service for regulated workloads. For additional context on Persistent UI endpoints, see [View persistent application user interfaces in Amazon EMR](https://docs.aws.amazon.com/emr/latest/ManagementGuide/app-history-spark-UI.html). For additional context regarding notebooks, see [Amazon EMR Notebooks overview](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-managed-notebooks.html). + * Amazon EMR Studio Workspaces and Persistent UI endpoints use FIPS 140 validated cryptographic modules for encryption-in-transit, which enables easier adoption of the service for regulated workloads. For additional context on Persistent UI endpoints, see [View persistent application user interfaces in Amazon EMR](https://docs.aws.amazon.com/emr/latest/ManagementGuide/app-history-spark-UI.html). For additional context regarding notebooks, see [Amazon EMR Notebooks overview](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-managed-notebooks.html).