AWS emr medium security documentation change
Summary
Corrected configuration key for custom AWS credentials provider in Spark job example
Security assessment
The incorrect key 'spark.hadoop.fs.s3.customAWSCredentialsProvider' could lead to misconfiguration, potentially causing jobs to use default credentials instead of the intended AssumeRole provider. This fixes a security-related configuration error.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/jobs-s3-access.md b/emr/latest/EMR-Serverless-UserGuide/jobs-s3-access.md index e03a63b97..5c6e3d5d0 100644 --- a//emr/latest/EMR-Serverless-UserGuide/jobs-s3-access.md +++ b//emr/latest/EMR-Serverless-UserGuide/jobs-s3-access.md @@ -207 +207 @@ The following example shows how to use an assumed role to start an EMR Serverles - "spark.hadoop.fs.s3.customAWSCredentialsProvider": "spark.hadoop.fs.s3.customAWSCredentialsProvider=com.amazonaws.emr.AssumeRoleAWSCredentialsProvider", + "fs.s3.customAWSCredentialsProvider": "spark.hadoop.fs.s3.customAWSCredentialsProvider=com.amazonaws.emr.AssumeRoleAWSCredentialsProvider",