AWS emr documentation change
Summary
Updated example code and CLI commands to use EMR release label 7.13.0 instead of 7.12.0 for client-side encryption configuration
Security assessment
This change updates example code to reference the new EMR release 7.13.0. While the topic is security-related (client-side encryption), the change itself is just a version update in examples, not a security fix or new security documentation.
Diff
diff --git a/emr/latest/ReleaseGuide/emr-emrfs-encryption-cse.md b/emr/latest/ReleaseGuide/emr-emrfs-encryption-cse.md index e978437b8..076568777 100644 --- a//emr/latest/ReleaseGuide/emr-emrfs-encryption-cse.md +++ b//emr/latest/ReleaseGuide/emr-emrfs-encryption-cse.md @@ -133 +133 @@ For example, in the AWS SDK for Java using RunJobFlowRequest, your code might lo - .withReleaseLabel("emr-7.12.0") + .withReleaseLabel("emr-7.13.0") @@ -168 +168 @@ Using the `create-cluster` command from the AWS CLI, you can use the `--configur - aws emr create-cluster --release-label emr-7.12.0 --instance-type m5.xlarge --instance-count 2 --configurations file://myConfig.json --emrfs Encryption=ClientSide,CustomProviderLocation=s3://amzn-s3-demo-bucket/myfolder/myprovider.jar,CustomProviderClass=classname + aws emr create-cluster --release-label emr-7.13.0 --instance-type m5.xlarge --instance-count 2 --configurations file://myConfig.json --emrfs Encryption=ClientSide,CustomProviderLocation=s3://amzn-s3-demo-bucket/myfolder/myprovider.jar,CustomProviderClass=classname