AWS emr documentation change
Summary
Corrected EMRFS configuration syntax for AssumeRoleAWSCredentialsProvider by removing redundant key prefix
Security assessment
The change fixes a documentation error in credential provider configuration but does not address a specific security vulnerability. It improves clarity for secure role assumption setup.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/jobs-s3-access.md b/emr/latest/EMR-Serverless-UserGuide/jobs-s3-access.md index 83d74b845..e075fa328 100644 --- a//emr/latest/EMR-Serverless-UserGuide/jobs-s3-access.md +++ b//emr/latest/EMR-Serverless-UserGuide/jobs-s3-access.md @@ -211 +211 @@ If you want to use a single assumed role to access all S3 resources in account B - 1. Specify EMRFS configuration `fs.s3.customAWSCredentialsProvider` to `spark.hadoop.fs.s3.customAWSCredentialsProvider=com.amazonaws.emr.AssumeRoleAWSCredentialsProvider`. + 1. Specify EMRFS configuration `fs.s3.customAWSCredentialsProvider` to `com.amazonaws.emr.AssumeRoleAWSCredentialsProvider`. @@ -242 +242 @@ 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", + "spark.hadoop.fs.s3.customAWSCredentialsProvider": "com.amazonaws.emr.AssumeRoleAWSCredentialsProvider",