AWS emr documentation change
Summary
Modified wording from 'must include' to 'include' and 'recommend' to 'suggest' in Iceberg usage guidance
Security assessment
Changes are stylistic improvements without altering security meaning. The VPC endpoint policy reference maintains existing security guidance without introducing new protections.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/emr-serverless-lf-enable-considerations.md b/emr/latest/EMR-Serverless-UserGuide/emr-serverless-lf-enable-considerations.md index feb675c8c..9558d8a93 100644 --- a//emr/latest/EMR-Serverless-UserGuide/emr-serverless-lf-enable-considerations.md +++ b//emr/latest/EMR-Serverless-UserGuide/emr-serverless-lf-enable-considerations.md @@ -53 +53 @@ System profile logs are always persisted in managed storage – this is a mandat -If your EMR Serverless application is in a private subnet with VPC endpoints for Amazon S3 and you attach an endpoint policy to control access, before your jobs can send log data to AWS Managed Amazon S3, you must include the permissions detailed in [Managed storage](logging.html#jobs-log-storage-managed-storage) in your VPC policy to S3 gateway endpoint. For troubleshooting requests, contact AWS support. +If your EMR Serverless application is in a private subnet with VPC endpoints for Amazon S3 and you attach an endpoint policy to control access, before your jobs can send log data to AWS Managed Amazon S3, include the permissions detailed in [Managed storage](logging.html#jobs-log-storage-managed-storage) in your VPC policy to S3 gateway endpoint. For troubleshooting requests, contact AWS support. @@ -72 +72 @@ The following are considerations and limitations when using Apache Iceberg: - * We recommend that you use Iceberg DataFrameWriterV2 instead of V1. + * We suggest that you use Iceberg DataFrameWriterV2 instead of V1.