AWS lake-formation documentation change
Summary
Added details about applying Lake Formation permissions using tag-based access control and cross-account sharing capabilities
Security assessment
Documents security features (tag-based access control and cross-account sharing) but does not indicate any vulnerability being patched
Diff
diff --git a/lake-formation/latest/dg/create-s3-tables-catalog.md b/lake-formation/latest/dg/create-s3-tables-catalog.md index 31c51b68a..3169ab609 100644 --- a//lake-formation/latest/dg/create-s3-tables-catalog.md +++ b//lake-formation/latest/dg/create-s3-tables-catalog.md @@ -11 +11,3 @@ How Data Catalog and Lake Formation integration works -You can integrate Amazon S3 table buckets and tables with AWS Glue Data Catalog (Data Catalog), and register the catalog as a Lake Formation data location from the Lake Formation console or using service APIs. +You can integrate Amazon S3 table buckets and tables with AWS Glue Data Catalog (Data Catalog), and register the catalog as a Lake Formation data location from the Lake Formation console or using service APIs. When your organization manages data in the Data Catalog, and register the data location with Lake Formation, you can use Lake Formation to control access to your datasets. + +You can apply Lake Formation permissions using tag-based access control and the named resource method on the federated databases, and share them across multiple AWS accounts, AWS Organizations, and organizational units (OUs). You can also share the federated databases directly with IAM principals from another account.