AWS emr documentation change
Summary
Minor wording changes in IAM troubleshooting guide: changed 'must contact' to 'contact', 'view details' to 'access details', and 'you must add' to 'add' in logging instructions. No technical changes.
Security assessment
Changes are grammatical improvements and clarifications of existing security documentation. No new security guidance or vulnerability fixes introduced.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/security_iam_troubleshoot.md b/emr/latest/EMR-Serverless-UserGuide/security_iam_troubleshoot.md index 36e6d7a82..3f618f18f 100644 --- a//emr/latest/EMR-Serverless-UserGuide/security_iam_troubleshoot.md +++ b//emr/latest/EMR-Serverless-UserGuide/security_iam_troubleshoot.md @@ -26 +26 @@ Use the following information to help you diagnose and fix common issues that yo -If the AWS Management Console tells you that you're not authorized to perform an action, then you must contact your administrator for assistance. Your administrator is the person that provided you with your user name and password. +If the AWS Management Console tells you that you're not authorized to perform an action, then contact your administrator for assistance. Your administrator is the person that provided you with your user name and password. @@ -28 +28 @@ If the AWS Management Console tells you that you're not authorized to perform an -The following example error occurs when the `mateojackson` user tries to use the console to view details about a fictional ``my-example-widget`` resource but does not have the fictional `emr-serverless:`GetWidget`` permissions. +The following example error occurs when the `mateojackson` user tries to use the console to access details about a fictional ``my-example-widget`` resource but does not have the fictional `emr-serverless:`GetWidget`` permissions. @@ -71 +71 @@ To learn more, consult the following: -If you use EMR Serverless managed storage for logging and your EMR Serverless application is in a private subnet with VPC endpoints for Amazon S3 and you attach an endpoint policy to control access, you must add the permissions mentioned in [Logging for EMR Serverless with managed storage](logging.html#jobs-log-storage-managed-storage) in your VPC policy to S3 gateway endpoint for EMR Serverless to store and serve application logs. +If you use EMR Serverless managed storage for logging and your EMR Serverless application is in a private subnet with VPC endpoints for Amazon S3 and you attach an endpoint policy to control access, add the permissions mentioned in [Logging for EMR Serverless with managed storage](logging.html#jobs-log-storage-managed-storage) in your VPC policy to S3 gateway endpoint for EMR Serverless to store and serve application logs.