AWS emr documentation change
Summary
Updated version references and added explicit EMR Serverless execution role requirement in command examples
Security assessment
While not addressing a specific security issue, the addition of explicit execution role requirements promotes least-privilege access practices, which is a security best practice.
Diff
diff --git a/emr/latest/ReleaseGuide/emr-spark-upgrade-agent-using.md b/emr/latest/ReleaseGuide/emr-spark-upgrade-agent-using.md index e530438ea..6e7d39de3 100644 --- a//emr/latest/ReleaseGuide/emr-spark-upgrade-agent-using.md +++ b//emr/latest/ReleaseGuide/emr-spark-upgrade-agent-using.md @@ -33 +33 @@ A demonstration of the EMR on EC2 upgrade experience with SMUS VS code editor. I - Upgrade my Spark application <local-project-path> from 2.4 to 3.5. + Upgrade my Spark application <local-project-path> from EMR version 6.0.0 to 7.12.0. @@ -35 +35 @@ A demonstration of the EMR on EC2 upgrade experience with SMUS VS code editor. I - s3://<s3-staging-path> to store updated application artifacts. + s3://<please fill in your staging bucket path> to store updated application artifacts. @@ -54,3 +54,3 @@ A demonstration of the EMR Serverless upgrade experience with Kiro CLI. You can - Upgrade my Spark application <local-project-path> from 2.4 to 3.5. - Use EMR-Serverless Applicaion <application-id> to run the validation and s3 paths - s3://<s3-staging-path> to store updated application artifacts. + Upgrade my Spark application <local-project-path> from EMR version 6.0.0 to 7.12.0. + Use EMR-Serverless Applicaion <application-id> and execution role <your EMR Serverless job execution role> to run the validation and s3 paths + s3://<please fill in your staging bucket path> to store updated application artifacts.