AWS emr documentation change
Summary
Minor grammatical and phrasing updates to improve clarity and conciseness in Apache Livy endpoint documentation. Changes include replacing 'you can create' with 'create', 'you must' with 'meet', and similar imperative verb adjustments. No substantive technical changes to requirements or functionality.
Security assessment
The changes are purely editorial/grammatical (e.g., 'you must submit' → 'submit', 'see' → 'refer to'). No new security controls, vulnerabilities, or mitigations are introduced. Existing security-related content about IAM roles (iam:PassRole), SIGv4 signing, and session isolation remains unchanged in substance.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/interactive-workloads-livy-endpoints.md b/emr/latest/EMR-Serverless-UserGuide/interactive-workloads-livy-endpoints.md index 4f157feb7..902405fce 100644 --- a//emr/latest/EMR-Serverless-UserGuide/interactive-workloads-livy-endpoints.md +++ b//emr/latest/EMR-Serverless-UserGuide/interactive-workloads-livy-endpoints.md @@ -9 +9 @@ PrerequisitesRequired permissionsGetting startedConsiderations -With Amazon EMR releases 6.14.0 and higher, you can create and enable an Apache Livy endpoint while creating an EMR Serverless application and run interactive workloads through your self-hosted notebooks or with a custom client. An Apache Livy endpoint offers the following benefits: +With Amazon EMR releases 6.14.0 and higher, create and enable an Apache Livy endpoint when creating an EMR Serverless application and run interactive workloads through your self-hosted notebooks or with a custom client. An Apache Livy endpoint offers the following benefits: @@ -20 +20 @@ With Amazon EMR releases 6.14.0 and higher, you can create and enable an Apache -To use an Apache Livy endpoint with EMR Serverless, you must meet the following requirements: +To use an Apache Livy endpoint with EMR Serverless, meet the following requirements: @@ -24 +24 @@ To use an Apache Livy endpoint with EMR Serverless, you must meet the following - * To run interactive workloads through Apache Livy endpoints, you need certain permissions and roles. For more information, see [ Required permissions for interactive workloads](https://docs.aws.amazon.com/emr/latest/EMR-Serverless-UserGuide/interactive-workloads.html#interactive-permissions). + * To run interactive workloads through Apache Livy endpoints, you need certain permissions and roles. For more information, refer to [ Required permissions for interactive workloads](https://docs.aws.amazon.com/emr/latest/EMR-Serverless-UserGuide/interactive-workloads.html#interactive-permissions). @@ -31 +31 @@ To use an Apache Livy endpoint with EMR Serverless, you must meet the following -In addition to the required permissions to access EMR Serverless, you must also add the following permissions to your IAM role to access an Apache Livy endpoint and run applications: +In addition to the required permissions to access EMR Serverless, also add the following permissions to your IAM role to access an Apache Livy endpoint and run applications: @@ -35 +35 @@ In addition to the required permissions to access EMR Serverless, you must also - * `iam:PassRole` – grants permission to access the IAM execution role while creating the Apache Livy session. EMR Serverless will use this role to execute your workloads. + * `iam:PassRole` – grants permission to access the IAM execution role when creating the Apache Livy session. EMR Serverless will use this role to execute your workloads. @@ -108 +108 @@ To create an Apache Livy-enabled application and run it, follow these steps. -Use the following command to check whether the status of your application. Once the status becomes `STARTED`, you can access the Apache Livy endpoint. +Use the following command to check whether the status of your application. Once the status becomes `STARTED`, access the Apache Livy endpoint. @@ -120 +120 @@ Use the following command to check whether the status of your application. Once -Once the endpoint is ready, you can submit workloads based on your use case. You must sign every request to the endpoint with [the SIGv4 protocol](https://docs.aws.amazon.com/IAM/latest/UserGuide/create-signed-request.html) and pass in an authorization header. You can use the following methods to run workloads: +Once the endpoint is ready, submit workloads based on your use case. You must sign every request to the endpoint with [the SIGv4 protocol](https://docs.aws.amazon.com/IAM/latest/UserGuide/create-signed-request.html) and pass in an authorization header. You can use the following methods to run workloads: @@ -122 +122 @@ Once the endpoint is ready, you can submit workloads based on your use case. You - * HTTP client – you must submit your Apache Livy endpoint API operations with a custom HTTP client. + * HTTP client – submit your Apache Livy endpoint API operations with a custom HTTP client. @@ -124 +124 @@ Once the endpoint is ready, you can submit workloads based on your use case. You - * Sparkmagic kernel – you must locally run the sparkmagic kernel and submit interactive queries with Jupyter notebooks. + * Sparkmagic kernel – run the sparkmagic kernel locally and submit interactive queries with Jupyter notebooks. @@ -131 +131 @@ Once the endpoint is ready, you can submit workloads based on your use case. You -To create an Apache Livy session, you must submit `emr-serverless.session.executionRoleArn` in the `conf` parameter of your request body. The following example is a sample `POST /sessions` request. +To create an Apache Livy session, submit `emr-serverless.session.executionRoleArn` in the `conf` parameter of your request body. The following example is a sample `POST /sessions` request. @@ -160 +160 @@ You can also send requests directly to the Apache Livy endpoint from an HTTP cli -Before you can start sending requests to the endpoint, make sure that you've installed the following libraries: +Before you start sending requests to the endpoint, make sure that you've installed the following libraries: @@ -289 +289 @@ Before you install sparkmagic, make sure that you have configured AWS credential - 1. Install sparkmagic by following the [installation steps](https://github.com/jupyter-incubator/sparkmagic?tab=readme-ov-file#installation). Note that you only need to perform the first four steps. + 1. Install sparkmagic by following the [installation steps](https://github.com/jupyter-incubator/sparkmagic?tab=readme-ov-file#installation). Note that you only perform the first four steps. @@ -351 +351 @@ Consider the following considerations when running interactive workloads through - * EMR Serverless maintains session-level isolation using the caller principal. The caller principal that creates the session is the only one that can access that session. For more granular isolation, you can configure a source identity when you assume credentials. In this case, EMR Serverless enforces session-level isolation based on both the caller principal and the source identity. For more information about source identity, see [ Monitor and control actions taken with assumed roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_monitor.html#id_credentials_temp_control-access_monitor-specify-sourceid). + * EMR Serverless maintains session-level isolation using the caller principal. The caller principal that creates the session is the only one that can access that session. For more granular isolation, configure a source identity when you assume credentials. In this case, EMR Serverless enforces session-level isolation based on the caller principal and the source identity. For more information about source identity, refer to [ Monitor and control actions taken with assumed roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_monitor.html#id_credentials_temp_control-access_monitor-specify-sourceid). @@ -363 +363 @@ Consider the following considerations when running interactive workloads through - * For the best startup experience, we recommend that you configure pre-initialized capacity for drivers and executors. + * For the best startup experience, we suggest that you configure pre-initialized capacity for drivers and executors. @@ -367 +367 @@ Consider the following considerations when running interactive workloads through - * You must have sufficient vCPU service quota in your AWS account to run interactive workloads with the Apache Livy endpoint. We recommend at least 24 vCPU. + * You must have sufficient vCPU service quota in your AWS account to run interactive workloads with the Apache Livy endpoint. We suggest at least 24 vCPU. @@ -384 +384 @@ This configuration cannot be changed prior to emr-7.8.0. The following is a samp - * Starting with Amazon EMR release emr-7.8.0 for Applications with fine-grained access control via LakeFormation enabled, the setting can be disabled per session. For more information on enabling fine grained access control for an EMR Serverless application, see [Methods for fine-grained access control](emr-serverless-lf-enable.html#emr-serverless-lf-enable-config). + * Starting with Amazon EMR release emr-7.8.0 for Applications with fine-grained access control via LakeFormation enabled, the setting can be disabled per session. For more information on enabling fine grained access control for an EMR Serverless application, refer to [Methods for fine-grained access control](emr-serverless-lf-enable.html#emr-serverless-lf-enable-config).