AWS lake-formation documentation change
Summary
Added documentation about enabling LF-Tags for existing federated catalogs and migration requirements
Security assessment
Explains security feature (LF-Tags) implementation process but does not address vulnerabilities
Diff
diff --git a/lake-formation/latest/dg/granting-catalog-perms-TBAC.md b/lake-formation/latest/dg/granting-catalog-perms-TBAC.md index 3d913eb75..9e85b90c3 100644 --- a//lake-formation/latest/dg/granting-catalog-perms-TBAC.md +++ b//lake-formation/latest/dg/granting-catalog-perms-TBAC.md @@ -18,0 +19,21 @@ You can grant permissions on LF-Tags by using the AWS Lake Formation console, th +###### Note + +The following steps are not needed for S3 Tables catalogs. You can use LF-Tags to grant permissions on existing S3 Tables catalogs without deleting and recreating them. + +###### Enabling LF-Tags support for existing federated catalogs that uses Lake Formation permissions + +Follow these steps,iIf you have existing federated catalogs that are using Lake Formation permissions, such as Amazon Redshift or Amazon DynamoDB federated catalogs that were created before LF-Tags support was available for federated catalogs. + +This scenario is not applicable to S3 tables catalog. + + 1. Delete the existing catalog – Call the `deleteCatalog` API operation to remove the existing federated catalog that uses Lake Formation permissions. + +Create a new federated catalog – Create a new catalog and point the new catalog to your existing namespace/datashare. + + 2. Use a new name for the catalog – This process updates your pre-existing federated catalogs to support LF-Tag functionality. + +If you want to use the same catalog name, contact AWS support team for assistance. + + + +