AWS lake-formation documentation change
Summary
Added AWS Glue ETL to integrated services list and clarified credential vending limitations with Spark SQL
Security assessment
While clarifying integration boundaries, there's no evidence of addressing security vulnerabilities. The Spark SQL clarification prevents misconfiguration but doesn't document security features or fixes.
Diff
diff --git a/lake-formation/latest/dg/Integrating-with-LakeFormation.md b/lake-formation/latest/dg/Integrating-with-LakeFormation.md index 3e4d8d903..1055ed080 100644 --- a//lake-formation/latest/dg/Integrating-with-LakeFormation.md +++ b//lake-formation/latest/dg/Integrating-with-LakeFormation.md @@ -7 +7 @@ -Integrating with AWS Lake Formation enables third-party services to securely access data in their Amazon S3 based data lakes. You can use Lake Formation as your authorization engine to manage or enforce permissions to your data lake with integrated AWS services such as Amazon Athena, Amazon EMR, and Redshift Spectrum. Lake Formation provides two options for integrating services: +Integrating with AWS Lake Formation enables third-party services to securely access data in their Amazon S3 based data lakes. You can use Lake Formation as your authorization engine to manage or enforce permissions to your data lake with integrated AWS services such as AWS Glue ETL, Amazon Athena, Amazon EMR, and Redshift Spectrum. Lake Formation provides two options for integrating services: @@ -15,0 +16,2 @@ Integrating with AWS Lake Formation enables third-party services to securely acc +Lake Formation credential vending doesn't integrate with spark sql queries. Credential vending only works with queries that run through the AWS Glue ETL library. +