AWS emr documentation change
Summary
Minor wording improvements and typo fixes in IAM policy documentation (e.g., 'right permissions' to 'appropriate permissions', removed duplicate 'the', changed 'see' to 'refer to')
Security assessment
Changes are editorial improvements to existing security documentation without introducing new security concepts or addressing vulnerabilities. No evidence of security incident remediation.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/security-iam-user-access-policies.md b/emr/latest/EMR-Serverless-UserGuide/security-iam-user-access-policies.md index abb5e76d6..67fee5b98 100644 --- a//emr/latest/EMR-Serverless-UserGuide/security-iam-user-access-policies.md +++ b//emr/latest/EMR-Serverless-UserGuide/security-iam-user-access-policies.md @@ -9 +9 @@ Power user policyData engineer policyUsing tags for access control -You can set up fine-grained policies for your users depending on the actions you want each user to perform when interacting with EMR Serverless applications. The following policies are examples that might help in setting up the right permissions for your users. This section focuses only on EMR Serverless policies. For samples of EMR Studio user policies, see [Configure EMR Studio user permissions](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-studio-user-permissions.html#emr-studio-advanced-permissions-policy). For information about how to attach policies to IAM users (principals), see [ Managing IAM policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-using.html) in the IAM User Guide. +You can set up fine-grained policies for your users depending on the actions you want each user to perform when interacting with EMR Serverless applications. The following policies are examples that might help in setting up the appropriate permissions for your users. This section focuses only on EMR Serverless policies. For samples of EMR Studio user policies, refer to [Configure EMR Studio user permissions](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-studio-user-permissions.html#emr-studio-advanced-permissions-policy). For information about how to attach policies to IAM users (principals), refer to [ Managing IAM policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-using.html) in the IAM User Guide. @@ -108 +108 @@ If you want to restrict EMR Serverless access to certain subnets, you can tag ea -If you’re an Administrator or power user creating your first application, you must configure your permission policies to allow you to create a EMR Serverless service-linked role. To learn more, see [Using service-linked roles for EMR Serverless](./using-service-linked-roles.html). +If you’re an Administrator or power user creating your first application, you must configure your permission policies to allow you to create a EMR Serverless service-linked role. To learn more, refer to [Using service-linked roles for EMR Serverless](./using-service-linked-roles.html). @@ -122 +122 @@ The following IAM policy permits you to create a EMR Serverless service-linked r -This following is a sample policy that allows users read-only permissions on EMR Serverless applications, as well as the the ability to submit and debug jobs. Keep in mind that because this policy does not explicitly deny actions, a different policy statement may still be used to grant access to specified actions. +This following is a sample policy that allows users read-only permissions on EMR Serverless applications, as well as the ability to submit and debug jobs. Keep in mind that because this policy does not explicitly deny actions, a different policy statement may still be used to grant access to specified actions.