AWS AmazonS3 documentation change
Summary
Modified text to indicate Lake Formation permissions are optional rather than required for AWS Glue ETL jobs
Security assessment
The change clarifies Lake Formation usage as optional but does not remove security functionality. No evidence of a security vulnerability being addressed.
Diff
diff --git a/AmazonS3/latest/userguide/s3-tables-integrating-glue.md b/AmazonS3/latest/userguide/s3-tables-integrating-glue.md index 7b7d1921f..b9d31d1e1 100644 --- a//AmazonS3/latest/userguide/s3-tables-integrating-glue.md +++ b//AmazonS3/latest/userguide/s3-tables-integrating-glue.md @@ -28 +28 @@ Choose your access method based on your specific AWS Glue ETL job requirements: - * **AWS analytics services integration (Recommended)** – Recommended when you need centralized metadata management across multiple AWS analytics services, need to leverage existing AWS Glue Data Catalog permissions and fine-grained access control with Lake Formation, or are building production ETL pipelines that integrate with other AWS services like Athena or Amazon EMR. + * **AWS analytics services integration (Recommended)** – Recommended when you need centralized metadata management across multiple AWS analytics services, need to leverage existing AWS Glue Data Catalog permissions and optionally Lake Formation, or are building production ETL pipelines that integrate with other AWS services like Athena or Amazon EMR.