AWS athena documentation change
Summary
Fixed apostrophe encoding in Lake Formation permissions documentation
Security assessment
Typo correction in existing security context about query result access controls
Diff
diff --git a/athena/latest/ug/lf-athena-limitations.md b/athena/latest/ug/lf-athena-limitations.md index 558301f9d..740e483ec 100644 --- a//athena/latest/ug/lf-athena-limitations.md +++ b//athena/latest/ug/lf-athena-limitations.md @@ -56 +56 @@ Users in the same Athena workgroup can see the data that Lake Formation fine-gra -The query results locations in Amazon S3 for Athena cannot be registered with Lake Formation. Lake Formation permissions don&t limit access to these locations. Unless you limit access, Athena users can access query result files and metadata when they don&t have Lake Formation permissions for the data. To avoid this, we recommend that you use workgroups to specify the location for query results and align workgroup membership with Lake Formation permissions. You can then use IAM permissions policies to limit access to query results locations. For more information about query results, see [Work with query results and recent queries](./querying.html). +The query results locations in Amazon S3 for Athena cannot be registered with Lake Formation. Lake Formation permissions don't limit access to these locations. Unless you limit access, Athena users can access query result files and metadata when they don't have Lake Formation permissions for the data. To avoid this, we recommend that you use workgroups to specify the location for query results and align workgroup membership with Lake Formation permissions. You can then use IAM permissions policies to limit access to query results locations. For more information about query results, see [Work with query results and recent queries](./querying.html).