AWS emr documentation change
Summary
Multiple phrasing changes including timeout configuration clarification and VPC connectivity instructions
Security assessment
While mentioning security services like KMS and VPC connectivity, the changes only simplify sentence structure without adding new security guidance or addressing specific vulnerabilities. The timeout configuration clarification maintains existing functionality.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/considerations.md b/emr/latest/EMR-Serverless-UserGuide/considerations.md index 499ddc7fa..6a22a3f80 100644 --- a//emr/latest/EMR-Serverless-UserGuide/considerations.md +++ b//emr/latest/EMR-Serverless-UserGuide/considerations.md @@ -63 +63 @@ The following list contains other considerations with EMR Serverless. -For a list of endpoints associated with these Regions, see [Service endpoints](./endpoints-quotas.html#endpoints). +For a list of endpoints associated with these Regions, refer to [Service endpoints](./endpoints-quotas.html#endpoints). @@ -65 +65 @@ For a list of endpoints associated with these Regions, see [Service endpoints](. - * The default timeout for a job run is 12 hours. You can change this setting with the `executionTimeoutMinutes` property in the `startJobRun` API or the AWS SDK. You can set `executionTimeoutMinutes` to 0 if you want your job run to never time out. For example, if you have a streaming application, you can set `executionTimeoutMinutes` to 0 to allow the streaming job to run continuously. + * The default timeout for a job run is 12 hours. You can change this setting with the `executionTimeoutMinutes` property in the `startJobRun` API or the AWS SDK. You can set `executionTimeoutMinutes` to 0 if you want your job run to never time out. For example, if you have a streaming application, set `executionTimeoutMinutes` to 0 to allow the streaming job to run continuously. @@ -69 +69 @@ For a list of endpoints associated with these Regions, see [Service endpoints](. - * Without VPC connectivity, a job can access some AWS service endpoints in the same AWS Region. These services include Amazon S3, AWS Glue, AWS Lake Formation, Amazon CloudWatch Logs, AWS KMS, AWS Security Token Service, Amazon DynamoDB, and AWS Secrets Manager. You can enable VPC connectivity to access other AWS services through [AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html), but you aren't required to do this. To access external services, you can create your application with a VPC. + * Without VPC connectivity, a job can access some AWS service endpoints in the same AWS Region. These services include Amazon S3, AWS Glue, AWS Lake Formation, Amazon CloudWatch Logs, AWS KMS, AWS Security Token Service, Amazon DynamoDB, and AWS Secrets Manager. You can enable VPC connectivity to access other AWS services through [AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html), but you aren't required to do this. To access external services, create your application with a VPC.