AWS emr documentation change
Summary
Updated terminology from 'view job runs' to 'access job runs', simplified phrasing in multiple sections, and changed 'see' to 'refer to' in documentation links
Security assessment
Changes are primarily linguistic improvements and terminology updates without addressing security vulnerabilities or introducing new security features. References to IAM runtime roles and security configurations remain unchanged in content.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/jobs-studio.md b/emr/latest/EMR-Serverless-UserGuide/jobs-studio.md index 78ee52b0e..ca24d3f86 100644 --- a//emr/latest/EMR-Serverless-UserGuide/jobs-studio.md +++ b//emr/latest/EMR-Serverless-UserGuide/jobs-studio.md @@ -5 +5 @@ -Submit a jobView job runs +Submit a jobAccess job runs @@ -9 +9 @@ Submit a jobView job runs -You can submit job runs to EMR Serverless applications and view the jobs from the EMR Studio console. To create or navigate to your EMR Serverless application on the EMR Studio console, follow the instructions in [Getting started from the console](https://docs.aws.amazon.com/emr/latest/EMR-Serverless-UserGuide/getting-started.html#gs-console). +You can submit job runs to EMR Serverless applications and access the jobs from the EMR Studio console. To create or navigate to your EMR Serverless application on the EMR Studio console, follow the instructions in [Getting started from the console](https://docs.aws.amazon.com/emr/latest/EMR-Serverless-UserGuide/getting-started.html#gs-console). @@ -13 +13 @@ You can submit job runs to EMR Serverless applications and view the jobs from th -On the **Submit job** page, you can submit a job to an EMR Serverless application as follows. +On the **Submit job** page, submit a job to an EMR Serverless application as follows. @@ -20 +20 @@ Spark - 2. In the **Runtime role** field, enter the name of the IAM role that your EMR Serverless application can assume for the job run. To learn more about runtime roles, see [Job runtime roles for Amazon EMR Serverless](./security-iam-runtime-role.html). + 2. In the **Runtime role** field, enter the name of the IAM role that your EMR Serverless application can assume for the job run. To learn more about runtime roles, refer to [Job runtime roles for Amazon EMR Serverless](./security-iam-runtime-role.html). @@ -34 +34 @@ Spark -If you specify Spark driver and executor sizes, you must take memory overhead into account. Specify memory overhead values in the properties `spark.driver.memoryOverhead` and `spark.executor.memoryOverhead`. Memory overhead has a default value of 10% of container memory, with a minimum of 384 MB. The executor memory and the memory overhead together can't exceed the worker memory. For example, the maximum `spark.executor.memory` on a 30 GB worker must be 27 GB. +If you specify Spark driver and executor sizes, take memory overhead into account. Specify memory overhead values in the properties `spark.driver.memoryOverhead` and `spark.executor.memoryOverhead`. Memory overhead has a default value of 10% of container memory, with a minimum of 384 MB. The executor memory and the memory overhead together can't exceed the worker memory. For example, the maximum `spark.executor.memory` on a 30 GB worker must be 27 GB. @@ -38 +38 @@ If you specify Spark driver and executor sizes, you must take memory overhead in - * **Additional settings** — Active or deactivate the AWS Glue Data Catalog as a metastore and modify application log settings. To learn more about metastore configurations, see [Metastore configuration for EMR Serverless](./metastore-config.html). To learn more about application logging options, see [Storing logs](./logging.html). + * **Additional settings** — Active or deactivate the AWS Glue Data Catalog as a metastore and modify application log settings. To learn more about metastore configurations, refer to [Metastore configuration for EMR Serverless](./metastore-config.html). To learn more about application logging options, refer to [Storing logs](./logging.html). @@ -78 +78 @@ Hive - * **Additional settings** — Activate or deactivate the AWS Glue Data Catalog as a metastore and modify application log settings. To learn more about metastore configurations, see [Metastore configuration for EMR Serverless](./metastore-config.html). To learn more about application logging options, see [Storing logs](./logging.html). + * **Additional settings** — Activate or deactivate the AWS Glue Data Catalog as a metastore and modify application log settings. To learn more about metastore configurations, refer to [Metastore configuration for EMR Serverless](./metastore-config.html). To learn more about application logging options, refer to [Storing logs](./logging.html). @@ -87 +87 @@ Hive -## View job runs +## Access job runs @@ -89 +89 @@ Hive -From the **Job runs** tab on an application’s **Details** page, you can view job runs and perform the following actions for job runs. +From the **Job runs** tab on an application’s **Details** page, access job runs and perform the following actions for job runs. @@ -91 +91 @@ From the **Job runs** tab on an application’s **Details** page, you can view j -**Cancel job** — To cancel a job run that is in the `RUNNING` state, choose this option. To learn more about job run transitions, see [Job run states](./job-states.html). +**Cancel job** — To cancel a job run that is in the `RUNNING` state, choose this option. To learn more about job run transitions, refer to [Job run states](./job-states.html).